• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Win98SE Win2k dual boot IP problem

Lehmann

Member
I've got my machine set up to dual boot between Windows 98SE and Windows 2k professional, but the networking will only work on one side at a time. For example, if it is working in 2k and I reboot into 98 the networking will not work there. If I reboot back to 2k it will work fine again. So if I'm in 98 then and remove the TCP/IP drivers and reboot back into 98, install TCP/IP again, and reboot again, it will finally work in 98. But then if I reboot into 2k then, it won't work there and I have to repeat the process for 2k. Tiring huh? I have a 3com 3c905 pci nic and I'm on a DHCP network. I've tried running Winipcfg in Windows 98, but it doesn't show any IP address at all, just gives me 0.0.0.0. That seems odd to me because even if it's not hitting the DHCP server it should at least assign itself a 168.*.*.* address shouldn't it? If you've got any ideas I would really appreciate it. Thanks!

John
 
Hmm.. a bit strange... sounds like there is a problem with renewing the lease... DHCP leases on Win2k machines last for 8 days by default, but that can be changed. If no DHCP server is found it will auto configure itself with APIPA address 169.254.*.* I suggest using static Ip if possible. I'll try to find a better answer though in the meantime, try just releasing and renewing the IP in win98 with the winipcfg util... see if that works in stead of trying to reinstall everything...
 
Unfortunately I tried that too. Releasing and renewing results in an error that I think says error accessing device. That would make it sound like a driver issue, but I wouldn't think 3Com cards would have problems like that.

The DHCP server on my network should automatically assign the same IP address to both sides of my machine, recognizing my MAC address shouldn't it?

Thanks,
John
 
Back
Top