Hi there, I want to know if this is a W2K problem...if so, is there a way to get around it....Basically, when I input a static IP in W2K and then disconnects the cable, the ipconfig does not show me the static IP...It works fine in NT...One of our software requires the ipconfig to see the static IP in order for it to work...Can someone be kind enough and enlighten me on this subject...thanks...

Assigning Static IP Address While Network Adapter Is Disconnected Results in IP Address of 0.0.0.0 When You Reconnect Adapter (Q254116) SYMPTOMS When you change the way your computer receives an Internet Protocol (IP) address, from use of Dynamic Host Configuration Protocol (DHCP) to use of a static IP address, and you make this change while your network adapter is disconnected, the IP address after you reconnect the network adapter is 0.0.0.0. RESOLUTION To work around this behavior, disable and then re-enable the network adapter in the Network And Dial-up Connections folder. I hope this helps! I know that Microsoft.com knowledge base is great when trying to troubleshoot a problem.

In other words, as soon as W2K recognized that the cable is disconnected...ipconfig simply shows that the cable has been disconnected and does not showcase any ip numbers...Is there a way to get around this such as the registry...We have to do a demo on our software, and sadly, getting a physical network connection is not possible....any suggestions is greatly appreciated...thanks..

What you are seeing is the link state feature of W2k. It detects if the cable is disconnected. If you don't want that try this... To prevent your network adapter from detecting the link state: 1. Use Registry Editor (Regedt32.exe) to view the following key in the registry: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters Add the following registry value: Value Name: DisableDHCPMediaSense Data Type: REG_DWORD -Boolean Value Data Range: 0, 1 (False, True) Default: 0 (False) Description: This parameter controls DHCP Media Sense behavior. If you set this value data to 1, DHCP, and even non-DHCP, clients ignore Media Sense events from the interface. By default, Media Sense events trigger the DHCP client to take an action, such as attempting to obtain a lease (when a connect event occurs), or invalidating the interface and routes (when a disconnect event occurs). 2. Restart your computer. NOTE: There are some side effects of disabling the "Media Sensing" feature. For example, if you have a machine with two network adapters, and you have the "Media Sensing" feature enabled, if one network adapter does not work, it is unbound, and associated routes are removed so that all traffic goes through the other network adapter (assuming a default gateway is there). Also, if you are a roaming (portable) user, the "Media Sensing" feature is what provides the ability to connect to any network and have everything work, without restarting, release and renewing, and so on. After disabling Media Sense and restarting, Windows still shows the "Network Disconnected" icon on the TaskBar and the 'ipconfig' command still shows a "Media State .....: Cable Disconnected" message when the cable is disconnected. However, the Network Interface is bound to TCP/IP and you can verify this by looking at the route table --you can use the "route print" command-- which shows the interface IP address (you are also able to ping the IP address assigned to the NIC).

Glen, Brilliant...Your sharing of knowledge is greatly appreciated...You are a life saver...