Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
hello. this is probably a really stupid question, but i just
cannot get this to work for me.first, i'll detail the hardware involved:
motorola s5100 surfboard modem
linksys wrt54g router
G4 desktop running tiger (mine shipped early!) --
connected wirelessly
a P4 laptop running XP home -- also connected wirelessly
xbox with a wired connectionnow the problem, and i admit that i changed probably too
many variables at one time. my router had been dropping
connection intermittently and this was becoming a major
annoyance. my theory was that dhcp was assigning weird
and/or conflicting addresses to my machines, so i decided
to assign static ip addresses.what i did was this:
on each machine, i changed the network settings to use a
specific ip (192.168.1.200, 205, and 210). i then told the
router in the advanced routing tab to give out those
addresses on the default subnet 255.255.255.0 with a
gateway of 192.168.1.1. individually, the computers work
just fine. i can connect to the internet and the router from
both.now, the problem:
i use vnc to control my desktop remotely from my laptop
(just within the lan). my understanding is that vnc is
broken under tiger. ok, fine. but i should still be able to
communicate between the machines in other ways.
however, i cannot ping either machine from the other, nor
can i access shared folders on either machine from the
other. i tried shutting down all three firewalls (built-in
osx, zonealarm pro, and the router's) and still no dice. so i
decided to investigate further. while my computers see
their addresses as i assigned them, the router tells me
their addresses are the same as if it had assigned them via
dhcp (i.e. 192.168.1.100, etc.). so i tried turning the dhcp
feature off entirely. still the router said that the addresses
were the same, even after a reboot.so that's the long version of my problem(s). i need help
figuring out how to properly assign static ip addresses
through my router. or maybe i'm misunderstanding this
all and someone can point out a really simple thing i've
overlooked.any help or thoughts anyone here can offer would be
greatly appreciated.
Hi, mryeti. A couple things:
-If you are manually assigning static IP addresses, you don't need to use DHCP. You especially don't need to configure the DHCP server to give out the addresses that you have statically assigned. I suspect that doing this would cause strange things to happen. I would suggest removing any settings you made in the router regarding the comptuers and/or statically assigned addresses.
-When manually assigning IP addresses, you also need to assign subnet masks, default gateways, DNS servers, etc. Failing to do any or all of these will affect your computers' ability to communicate, depending on what you failed to assign. It sounds like you already know this, but just to make sure - check that the subnet mask and default gateway is the same on each computer you configured with a static IP address.
There are other things to check, some regarding VNC itself, but at this point I'm hoping that the problem is a simple IP addressing issue. Good luck, and post back with the results of my suggestions above if you need further help.
0 
I would suggest your conclusion of dhcp serving out wrong ip addresses is incorrect. Since it is the basis for all your changes - undo your changes.
set the router to provide ip addresses from .101 to .103 [3 ip address 3 pcs]
set the clients back to being dhcp enabledReboot everyone starting with the router.
Go to each pc and type at a cmd prompt "ipconfig". What are their ip addresses? If 101,102,103 then move on. DHCP is working.Can you ping the gateway? Can you ping the isp's listed dns server? if so you are on the internet and that is fine.
Can you ping between workstations? If so you know the firewalls are turned off properly. Now you are at basic networking
Use the same acct and password on all three machines. Same workgroup. Share something on each pc. See if you can browse to each share from the other.Post back where you encounter a break.
0
hey, thanks for the suggestions.
i've returned the ip settings on all of the machines to
allow the router to assign them via dhcp.jimminy -- i had the subnet and gateway settings correct,
but i double-checked per your suggestion.i can now ping from the mac to the windows machine, but
not the other way around. i can ping the router and dns
servers from both machines, and internet connectivity is
fine, as those results would suggest.i terminated zonealarm on the pc, disabled the router's
firewall (though i wouldn't think that one would affect
communication between the two machines on the
network), and disabled the firewall in osx.i've got my vnc server app running on the mac (osxvnc
v1.5) but cannot connect from the windows machine.
i suppose it's possible that, as i suggested in my earlier
post, vnc is broken under tiger. a friend of mine is also
having trouble with apple remote desktop, which is vnc-
based.additionally, i cannot access an ftp server on the mac from
the pc, which kind of pokes a hole in the theory of this
being a vnc-specific (as, i suppose, my inability to ping
from pc-->mac would also indicate) problem.one question about static addressing -- i had tried it a
couple of different ways before. the first of these was just
telling the individual machines what their ip would be and
then just allowing them to connect that way. the
implication in both posts replying to my initial question
seems to be that i don't need to do anything special with
the router to enable static addresses. is this a correct
assumption?
0
Yes, that is a correct assumption.
As wanderer suggested, running ipconfig /all (or its OSX equivalent. ifconfig, maybe?) could be helpful. Do that on each machine and post the output here.
0
ok, here's the ipconfig results from the pc:
C:\DOCUME~1\MRYETI>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : scottvaio
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : wi.rr.comEthernet adapter Wireless Network Connection 2:
Connection-specific DNS Suffix . : wi.rr.com
Description . . . . . . . . . . . : Wireless-G Notebook
Adapter #2
Physical Address. . . . . . . . . : 00-0C-41-A9-FE-BD
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.101
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 24.160.227.33
24.94.163.227
Lease Obtained. . . . . . . . . . : Tuesday, April 26,
2005 5:41:19 PM
Lease Expires . . . . . . . . . . : Wednesday, April 27,
2005and from the mac:
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST>
mtu 16384
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en0:
flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,M
ULTICAST> mtu 1500
ether 00:0a:95:69:b9:a2
media: autoselect (none) status: inactive
supported media: none autoselect 10baseT/UTP
<half-duplex> 10baseT/UTP <full-duplex> 10baseT/UTP
<full-duplex,hw-loopback> 100baseTX <half-duplex>
100baseTX <full-duplex> 100baseTX <full-duplex,hw-
loopback> 1000baseT <full-duplex> 1000baseT <full-
duplex,hw-loopback> 1000baseT <full-duplex,flow-
control> 1000baseT <full-duplex,flow-control,hw-
loopback>
en1:
flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,M
ULTICAST> mtu 1500
inet6 fe80::20d:93ff:fe81:ebbe%en1 prefixlen 64
scopeid 0x5
inet 192.168.1.100 netmask 0xffffff00 broadcast
192.168.1.255
ether 00:0d:93:81:eb:be
media: autoselect status: active
supported media: autoselect
fw0:
flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,M
ULTICAST> mtu 4078
lladdr 00:0a:95:ff:fe:69:b9:a2
media: autoselect <full-duplex> status: inactive
supported media: autoselect <full-duplex>
0
one reason why you may not be able to ping the mac from the PC is because of your DNS, might want to let your gateway IP handle your DNS (192.168.1.1), did you remove it (DNS) when you removed your static IP, subnet and gateway?
man the MAC is screwy :D i can see it's IP, and it looks like it is showing some IPV6, but i dont know what gateway or dns it is using from that post, never seen the new MACOSX
0
Josh, what was posted for the Mac is the standard formatting of *BSD's ifconfig command, which is what OSX runs under the hood. IPv6 support is compiled in the kernel by default, but is pretty much vestigial unless you're actively using it.
The relevant information for the Mac is
ip address: 192.168.1.100
netmask: 0xffffff00 (or 255.255.255.0, in integers)I can't see why DNS would have any bearing here. If mryeti is pinging by IP address, DNS isn't even involved. And if he is pinging by hostname - well, the router wouldn't know the hostnames of computers on its network anyway.
mryeti, the fact that you can ping your Windows box from the Mac tells us that there is TCP/IP connectivity and communication between the two computers. Ping is a two-way event. The machine being pinged has to receive and respond to packets from the machine pinging it. Since this is happening, it suggests that your network configuration - at least the IP addressing part of it - is correct.
That leaves software and/or operating system configurations on each computer to investigate. Unfortunately, your difficulty getting VNC/FTP/etc. to work could be due to various things - daemon configuration, client configuration, etc. I would suggest getting a port scanner and and do some probing of the mac from your Windows box. NMAP would be a good tool for this. See if it can detect the listening ports for the VNC and FTP server daemons. If not, that probably tells you that you need to look at how you have the Mac configured. If you can detect the Mac's listening ports from Windows, then the problem is possibly with your Windows configuration - the VNC client you are using, for example.
All that being said, I am still concerned that the changes you made to network settings early on may not have been completely undone and that something you changed is still causing problems. I don't know what that would be, unfortunately, becuase you seem to have already done everything I would suggest in that area. Maybe someone else will have some insight regarding that.
0
report from the port scan:
i did two ranges: 1-1024 and 5800-5900 (vnc ports).
between 1-1024, ports 25 and 100 are open. within the
5800-5900 range, no ports are open.
so, if i am interpreting these results correctly, you think
this is a problem with the mac. i guess i should be
unsurprised, as tiger has been exhibiting some issues
which indicate it was not quite ready for release.i am --almost-- certain that i've changed all of the
settings back to where they were before this problem
began, with the exception of going back to 10.3.x (the
prior version of os x). my hope is that apple will maintain
their tradition of releasing software patches for a new os
within a few days of official release. apparently a number
of third-party vendors and even apple themselves shipped
some copies of tiger early. i was excited to be amongst
those, but now it appears to be a mixed blessing.don't get me wrong -- these aren't windows-sized
problems ;D, but still annoying.ok, back to the real topic. to test my vnc client on the
windows machine, i connected to a friend's mac (not on
the LAN) last night. worked fine. i should note that he is NOT running the same version of the os i am.so, to review: ports 25 and 110 seem to be the only open
ports. i can send email to myself!i'm pretty sure all of my settings are back to the way they
were before.it doesn't seem to be a firewall issue, as it persists with no
firewalls in place.the vnc client on the pc works across the internet but not
within my own LAN.the vnc server app on the mac seems a bit flaky, but i
should at least see a response from the ports it uses when
i scan, right? even if it's not running, i mean. i have my
firewalls back up, but have opened the appropriate ports
on the mac.i'm going to try a firewall-free port scan and see if that
does anything. i'll post those results here when it's
finished.even if the problem is not getting solved, i appreciate
everyone's input here. at the very least i am learning a
thing or two. thanks!
0
Interesting. If you can see at least some listening ports on the Mac from the Windows box, I would say your network addressing issues are solved. That's good news :)
At this point, I would recommend looking into the VNC server configuration on the Mac. You might look at things such as - is it configured to accept connections on an interface other than en1? Is it running on a non-default port? Is the firewall or some other system policy blocking it?
One thing you might do is kill the VNC server and start a Telnet server listening on the same port. If you can telnet to the Mac on this port from Windows, then you know that it is possible to connect to the Mac on the port VNC uses. That would pretty much confirm that the issue is with the VNC setup.
0  |
 |
 |
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |
