Windows 98 Networking issues

[friedrice]

Howdy all,

Let me lay down a little background first. I've built networks before and am even on my way to getting a CCNA cert. There are weird issues with a network I built for a non-forprofit ministry. All their computers use Windows 98. I set up a Samsung Laser printer and have that going to a little Print Server box. Printer hooks up though USB, which of course the print server hooks up though CAT5 to a switch. This switch has all the other computers plugged into it.

Now the problem is, seems like once every two weeks I get a call about not being able to print. Usually going to winipcfg and renewing the IP does the trick. Rebooting works sometimes, but not always. But, they all have IP addresses in the first place. The IP's are provided by the Router which has a built in DHCP server in it. Just a cheap Link-something or other.

I blame it on the Old 98 machines. Also I didn't build the complete network, so I'm wondering if there may be issues with the router considering the fix for the problem. Or, does Win98 just plain suck for networks? Prolly both but any insight would be great. Thanks

 

[ktwebb]

if they are all having the problem at the same time it's not the OS. I'd assign a static IP to one or two users and see if when the next time this happens, they do not have the issue. Then just assign static IP's to everyone, assuming that's reasonable, like not a couple of hundred nodes or something.

 

[ryokum]

Is the lease on the IP address from the DHCP server running out?

 

[Agamar]

Sounds more like the little router is rebooting or some such. The chances of all the PCs having trouble printing at the same time would mean that none of the machines renewed their lease at the DHCP half-time (The computers should start trying to renew their leases around 4 hrs, on a 8 hr lease). I would do like KTWEBB said and assign one or 2 static addresses and try that. Check the logs for the printe server and router too.

 

[OmegaXero]

Is the print server set to a static IP or is it also DHCP assigned? If its DHCP that could be an issue. =) If its a static IP (which it most likely is) make sure its not an IP address that is in the lease range of the DHCP server.

 

[friedrice]

Thanks for the tips. I'm going to check out the network on monday, so i'll report back with my findings

 

[friedrice]

Just an update, it was an issue with the lease. It had a one week lease. I'm not sure why, but I guess the Windows 98 machines are too stupid or something to get a new IP. I would think the router would send them a new one, or the PC would just request a new one. Any ideas on why this is?

 

[yoda291]

Originally posted by: friedrice
Just an update, it was an issue with the lease. It had a one week lease. I'm not sure why, but I guess the Windows 98 machines are too stupid or something to get a new IP. I would think the router would send them a new one, or the PC would just request a new one. Any ideas on why this is?

Wiithout actually having a sniffer on the wire, I have a few experiences with this, all of them retarded.

First off, for some unexplained reason, win98 seems to include itself on collision detection when it renews a dhcp lease. So, it does an ARP for its new IP address then when it ends up responding its own arp, it thinks someone else already has that IP.

Another stupid thing I've seen is that the dsl/cable router might not be issuing out a renewal or may be issuing a new IP altogether. Most clients will request a renewal when the lease is half up. At that point, if the router has no record of the client being in its dhcp table, it will attempt to assign it the first address in its scope which might not match what the client already has. At the point, win98 kind of ignores it as a bogus response and keeps chugging along with the old lease.

One thing I find works is to shorten the lease time to something very short and see if win98 renews its lease at the halfway mark. If it does, set it to something like 6 hours or so.