Windows Network Neighborhood Trouble

[hardgiant]

Just thought I'd mention that a router reserves the first IP for itself.

192.168.1.1 = router

192.168.1.2 = computer 1

192.168.1.3 = computer 2

etc

also DHCP can be a real pain in the butt, for such a small network I would just assign static IP's and then you turn off the the DHCP service.

[rikytik]

My router is 192.168.1.1 and the LAN starts at 100. I'm wondering if I should go ahead and assign IP's. Usually they never change, but I do hook up with different wireless hardware from time to time and that makes a certain machine show up under a different IP.

And....after this a.m. when everything was working so well, I hooked up with a wireless machine and couldn't access the printer on the LAN. Talk about frustrating. So I put IPX/SPX back in the wireless and the machine with the printer--bam, works. Sheesh. Keeps a guy young, I guess. <chuckle>

[rikytik]

I feel kinda stupid. Most of my trouble seems to have been not setting up correctly the "trusted" ip range in the firewall software resident on each pc on the LAN. So, now, no more IPX/SPX, using DHCP through the 4 port LinkSys router, the wireless pc is working fine, printer prints. All systems seem Go.


What threw me completely off track was that if IPX/SPX was installed then the LAN functioned perfectly between the WinXP boxes--but the Linux boxes wouldn't connect to the XP boxes.