I recently installed Windows XP Professional (Build 2600.xps1.020822-1800: Service Pack 1, v.1105) on a AMD 1400 Box running on a motherboard with a Via Southbridge Integrated Chipset for Video/USB/LAN with appropriate XP device drivers. This box connects to a Redhat Linux 8.0 Server that is used for DHCP leasing, file serving, SCP, etc..

The newly created XP Pro AMD workstations DHCP client software connected ok to the Linux DHCP daemon just fine for approximately 24 hours and then just quit working and now will not see and communicate with it at all...furthermore if you run ipconfig or winipcfg to try and release/renew the client ip/sub/gateway stuff the ipconfig or winipcfg fails seeing the DHCP Server daemon. In fact the XP Pro shitware assigns an automatic private IP address indicating that it isn't seeing the DHCP server at all. I am convinced the hardware is working fine and the proper device driver is loaded and suspect this is some kind of new method of MS trying to screw with Linux but really not sure on this one. I am hoping someone else out there has already met with similiar results and already figured out the uncludge to make it work.

HELP ?????????

Nobody encountered this problems as well ?

Um, This has to do with Linux how??? No really, have you stoppped and restarted the dhcpd service of your RH box. I would restart dhcpd, check all your wiring and try again. I hate to say it, but Windoze XP does a pretty damn good job of finding drivers and getting hardware that is pretty much mainstream working well, untill you want to access a software dll, its pretty much downhill from there.

Chris

Yes, I stopped and started the DHCP daemon on the Linux Server and even reviewed the DHCP config file and audited the the lease file and didn't see anything that looked messed up.

I also checked the wiring by attaching my viao linux 9 and it worked fine. I am stumped on this one.

Any other idea's ?

I reinstalled XP Pro and guess what it worked perfect for about 12 hours this time and several reboots and then all network disabled again ...except this time I can release and renew the DHCP info and it gets the correct DHCP lease...however thats as far as it goes....no network connectivity via pinging and browser resolving.

Took a spare hard drive I had laying around and load RH9 and and no problems.... therefore nothing wrong with the hardware. It appears that this is a new MS thing with screwing with RH Linux in conjuction with XP Pro.

Does anyone on this forum have a clue ?