Win2k and RoadRunner DHCP Problem..

[DrFatal]

Once in a while my system would assign it self a specific ip address that start with 169.something. Now that's not a Road Runner ip address. I tried everything I could thing off, such as renew, release. My DHCP is enabled and set on automatic. Wen running ip config I get error message that the DHCP server could not be found.
If I boot up with win98, Me!, Linux or Beos they all work fine on the same system.

Any help would be appreciated..

Thnx!

 

[Captain_Rob]

Sounds like a Win2k driver problem. The 169.x.x.x address is the address that Windows assigns when it is not told what to be. If your NIC is a 10/100 model, it could be having trouble automatically syncing up. One thing you can try that might help is to lock the NIC into 10BaseT mode - Control Panel, Network, Local area connection, Properties, Configure, Advanced, Connection Type, 10baseT.

 

[CapNjacK]

Do you use the same machine name for each one of those OS installs on that machine?

 

[Akash]

what is happoning is that ether ur nic card isnt releaseing the ip addr's or they are not getting an ip.. reset ur cable modem and than bootup win2k

 

[DrFatal]

I fixed it!

I had bytes merge on the motherboard bios enable. Once disabled it works fine.

Thnx you guys!

 

[Captain_Rob]

<< I had bytes merge on the motherboard bios enable >>


I had to look that bios feature up just out of curiosity:

Byte Merging
This exists where multiple writes to non-contiguous memory addresses are merged into one PCI-to-memory operation by the host controller, letting devices sort out the ones they want, which increases bus throughput and hence performance for devices that support it-not all PCI video cards do, so enable unless you get bad graphics (this setting is intended to improve video performance). When enabled, the controller checks the CPU Byte Enable signals (8 of them) to see if data from the PCI bus can be merged. See also Byte Merge Support (next) and CPU-PCI Byte Merge.

I'm glad you found the problem, but I'm curious how you figured to even try an obscure bios option like that one?