• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 221
  • Last Modified:

TCP/IP Properties Hangs - IP Address Must Be Changed

I'm running NT Server 4 on a machine that is connected to a cable modem. The IP address of the machine was hard coded into TCP/IP properties when the system was setup. Apparently the IP Address the server was using is no longer available through the cable modem provider (they've reallocated that Class C to another part of the country) and I need to get into TCP/IP properties to change the IP Address again. I've done this before when I had to move the server ... it's easy to do and I've never had any problems.

Now, I'm trying to do this from 1200 miles away, by talking someone through it over the phone. When I ask the person to click on TCP/IP (on the Protocols tab of the Network properties window) and then click Properties, the hourglass appears and the window hangs. No other dialog box appears. No TCP/IP properties window appears. This doesn't freeze the entire server, just the Network Properties window.

This is bizarre to me! If I were sitting in front of the machine, I might be able to find a work around, but I'm 1200 miles away and am stumped! Any ideas on how I can get in there to change the IP Address? Am I just overlooking something?

Any help would be greatly appreciated!!
0
shmans
Asked:
shmans
  • 3
  • 2
1 Solution
 
stevenlewisCommented:
tell them to reboot the server and try
0
 
shmansAuthor Commented:
The server has been rebooted several times with no luck. We've also attempted this with the network cable plugged in and the network cable unplugged. (With reboots in between!)

Turning it off and turning it back on just isn't the solution to this one! :-)

Any other ideas?
0
 
stevenlewisCommented:
well, then you are going to have to walk them thru a reg edit
Use the Registry Editor (REGEDT32.EXE) to add your IP addresses and subnet masks, as follows:

WARNING: Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to reinstall Windows NT to correct them. Microsoft cannot guarantee that problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk.

Start REGEDT32.EXE and locate the following Registry subkey:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet \Services\<Adapter Name>\Parameters\Tcp
Find the IPAddress value and double-click it.
The Multi-String Editor dialog box should appear with the IP address selected. Type each additional IP address on a new line within the dialog box, then click OK. For example:

100.100.100.1
100.100.100.2
100.100.100.3
Find the SubnetMask value and double-click on it.
The Multi-String Editor dialog box should appear with the Subnet Mask selected. Enter each additional subnet mask on a new line within the dialog box, then click OK. For example:

255.255.255.0
255.255.255.0
255.255.255.0

IMPORTANT: The order of the IP addresses and subnet masks must correspond.
Exit REGEDT32.
Exit Windows NT and restart your computer.
0
 
shmansAuthor Commented:
I knew there had to be another way!! Thanks!

It was easy after I figured out the "name" of the Network Adapter. The abbreviations seem to have no logic: an Intel Pro/100 Plus NIC shows up as E100B1 in the Registry!

Thanks again for your help!
0
 
stevenlewisCommented:
shmans Glad to help
Steve
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now