mr yeti
@rr.com
| [wireless] linksys wrt54g static routing
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 connection
now 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.
sorry about the lengthy post. i just figured the more info, the better. |
|
flw
Security Is Like An Onion, It Has Layers
Premium
join:2004-01-04
 ·Verizon Online DSL
| Gee where to start....
Ok, first with fixed ips there should be no need (unless you share your connection with visitors) for DHCP so keep it off.
Next keep Internet connection offline (unlugged) while testing your local network for file sharing.
Then verify your ip settings. Box 1 is 192.169.1.200, box 2 is 192.168.1.205, box 3 is 192.168.1.210 all with subnet of 255.255.255.0 and gateway of your wireless router which is 192.168.1.1
Even with print and file sharing turned on, only TCP/IP is requred to share files. Verfiy you don't have any other protocals running other than TCP/IP.
Verify firewalls are all off by disabling them and keep them off until your back up. Then manually turn back on so one boxes firewall won't go up after a reboot while testing your local network.
Verify your all on the same SSID, channel, and just for testing leave WEP off. Once sharing is working, go back and enable WEP or WAP.
Review permissions for each share, you may have accidently changed a child or inherited file access permission(s).
You should be able to ping or tracert the other machines by ip rather than name. Same for VNC. I also vnc wirelessly to my hardwired PC via my wireless router-wrt54g just fine. You will want to verify your version of VNC is current for the OS's.
That's my best guess based on your description as I understand it.
--
"Keep your friends close and your enemies even closer" »www.byronil.org |
|
Ogiewon
join:2003-03-21
Wilmington, NC
| reply to mr yeti
If you went into each machine and statically assigned IP address on each computer manually, then you need not do anything at the router (so long as the addresses you picked are not in the range of the router's DHCP server.)
Go back to the router, put it back the way it was prior to your changes, and then try communicating between your systems. I have been statically assigning my ip addresses at each PC for years. The router could care less as long as the address I pick are in the same subnet as the router's LAN port, and do not conflict with the router's DHCP server's range of addresses. |
|
flw
Security Is Like An Onion, It Has Layers
Premium
join:2004-01-04
·Verizon Online DSL
| True but I would guess there's something on we don't know about like mac filter black or white listings or same for ip filter on router or then are all the firewalls really all off.
--
"Keep your friends close and your enemies even closer" »www.byronil.org |
|
A8codr
join:2004-05-30
Lakewood, OH
| reply to mr yeti
said by mr yeti:
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). That's fine for setting up your Static IP's on the machines in question.
said by mr yeti:
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.
This is not needed and whatr is causing your routing problems. When you set up static IP's on the units you only need to set it on each one not the router as well. You will need to make sure that you specify the routers IP address for the Gateway address of each PC. You'll also need to enter the DNS server addresses on each PC. You also want to make sure that DHCP is not running in the range of IP's you have statically assigned. After you've done that everyhing should be working as you wanted.
If all of your PC's are using static IP's you might want to disable DHCP. Just a thought. |
|
