Static TCP/IP Setting not saving...

Newbie Poster

24 posts since Jun 2006

Reputation Points: 10

Solved Threads: 0

The first thought that comes to mind is that you are using a Broadcom-supplied configuration utility which is conflicting with Windows built-in configuration functions. Is that possibly the case?

DMR

Wombat At Large

Team Colleague

7,229 posts since Dec 2003

Reputation Points: 221

Solved Threads: 370

The first thought that comes to mind is that you are using a Broadcom-supplied configuration utility which is conflicting with Windows built-in configuration functions. Is that possibly the case?

Hi DMR...

No thats not the case... The only thing that I have taken from Broadcom is the driver.

I am still just going into Network COnnections and Right-Mouse-Button on the LAN connection and going to Properties for the Internet Protocol (TCP/IP) setting and trying to make and save the changes there.??

Newbie Poster

24 posts since Jun 2006

Reputation Points: 10

Solved Threads: 0

First thing to try is to right click the LAN connection in Network Connections and choose "Repair"

Veteran Poster

1,182 posts since Feb 2005

Reputation Points: 262

Solved Threads: 68

First thing to try is to right click the LAN connection in Network Connections and choose "Repair"

Done... But no luck.!!

After doing the "Repair" then going into settings and making the necessary changes, saving these changes and exiting, then coming back in to setting, I see the "Obtain an IP address automatically" being set again. :sad:

Newbie Poster

24 posts since Jun 2006

Reputation Points: 10

Solved Threads: 0

Hmm, ok first try in a command window ipconfig/release (to release the DHCP lease) then open Local Area connection properties and set the static address.

I'm grasping at straws a bit here while I try and think of something better, but it's worth a try.

Next follow these steps and post the output:

Click Start, click Run, type Msinfo32, and then click OK.
2. Expand Components, expand Network, and then click Protocol
You will have ten sections under Protocol. The section headings will include the following names if the Winsock2 key is undamaged:
• MSAFD Tcpip [TCP/IP]
• MSAFD Tcpip [UDP/IP]
• RSVP UDP Service Provider
• RSVP TCP Service Provider
• MSAFD NetBIOS [\Device\NetBT_Tcpip...
• MSAFD NetBIOS [\Device\NetBT_Tcpip...
• MSAFD NetBIOS [\Device\NetBT_Tcpip...
• MSAFD NetBIOS [\Device\NetBT_Tcpip...
• MSAFD NetBIOS [\Device\NetBT_Tcpip...
• MSAFD NetBIOS [\Device\NetBT_Tcpip...

We are looking to see that the Winsock2 is not corrupted by any LSP that the Broadcom software or any other app may have added to winsock and stuffed it.

The next thing after that is to install support tools from the XP cd root/Support/Tools run the setup.exe (choose a complete install).

This installs (amongst other things) netdiag (command line network tool)
in a command window type this command:

netdiag /test:winsock /v

Veteran Poster

1,182 posts since Feb 2005

Reputation Points: 262

Solved Threads: 68

Hmm, ok first try in a command window ipconfig/release (to release the DHCP lease) then open Local Area connection properties and set the static address.

I'm grasping at straws a bit here while I try and think of something better, but it's worth a try.

Next follow these steps and post the output:

Click Start, click Run, type Msinfo32, and then click OK. 2. Expand Components, expand Network, and then click Protocol You will have ten sections under Protocol. The section headings will include the following names if the Winsock2 key is undamaged: • MSAFD Tcpip [TCP/IP] • MSAFD Tcpip [UDP/IP] • RSVP UDP Service Provider • RSVP TCP Service Provider • MSAFD NetBIOS [\Device\NetBT_Tcpip... • MSAFD NetBIOS [\Device\NetBT_Tcpip... • MSAFD NetBIOS [\Device\NetBT_Tcpip... • MSAFD NetBIOS [\Device\NetBT_Tcpip... • MSAFD NetBIOS [\Device\NetBT_Tcpip... • MSAFD NetBIOS [\Device\NetBT_Tcpip...

We are looking to see that the Winsock2 is not corrupted by any LSP that the Broadcom software or any other app may have added to winsock and stuffed it.

The next thing after that is to install support tools from the XP cd root/Support/Tools run the setup.exe (choose a complete install).

This installs (amongst other things) netdiag (command line network tool) in a command window type this command:

netdiag /test:winsock /v

:lol: You won't believe it :lol:

This morning when I was going thru your suggestions and getting errors, I realised among other things that whenever I had to enter any commands from DOS Prompt I had to actually be in the direfctory that the command existed.!!

Soooo I went and edited START ==> CONTROL PANEL ==> SYSTEM ==> ENVIRONMENT VARIABLES ==> SYSTEM VARIABLES ==> Path Statement and realised that there was no definition for %SystemRoot% or %SystemRoot%\System32

Once I added these two item and rebooted, I was then able to go back into the IP Settings and define STATIC definitions, reboot and reenter the definitions and they remained, so now the problem appears to be fixed...

Thanks to all for your assistance

:cheesy: :cheesy: :cheesy:

P.S. If someone could shed some light onto why the IP settings required that system variables be there, would be most helpful..!!

Newbie Poster

24 posts since Jun 2006

Reputation Points: 10

Solved Threads: 0

Whoa- how very trippy! Good friggin' find!

I have no idea what the variables have to do with IP settings specifically, but the fact that the %systemroot% varialbe is used all over the Registry might be relevant. Actually, given that, I'm surprised you weren't having a slew of other problems as well...

DMR

Wombat At Large

Team Colleague

7,229 posts since Dec 2003

Reputation Points: 221

Solved Threads: 370

Whoa- how very trippy! Good friggin' find!

I have no idea what the variables have to do with IP settings specifically, but the fact that the %systemroot% varialbe is used all over the Registry might be relevant. Actually, given that, I'm surprised you weren't having a slew of other problems as well...

I am TOTALLY amazed myself.!! :eek:

BUT.. The end result wa sthat the problem is now resolved.... Well this one anyway.

Now I can go home for the long weekend and enjoy myself.!!

tahnsk again for the assistance.

regards

Newbie Poster

24 posts since Jun 2006

Reputation Points: 10

Solved Threads: 0

Enjoy the weekend! I know I will... it's my birthday on Saturday, and I can tell you that one thing I won't be doing is sitting front of this computer! :mrgreen:

DMR

Wombat At Large

Team Colleague

7,229 posts since Dec 2003

Reputation Points: 221

Solved Threads: 370

P.S. If someone could shed some light onto why the IP settings required that system variables be there, would be most helpful..!!

I wouldn't be surprised if the TCP/IP properties dialogs are just a GUI on top of the netsh command tool.

Veteran Poster

1,182 posts since Feb 2005

Reputation Points: 262

Solved Threads: 68

I wouldn't be surprised if the TCP/IP properties dialogs are just a GUI on top of the netsh command tool.

Bingo- they are.
The Big Questions still remain, though: In what location(s) do the settings made with the TCP/IP properties GUI and/or the Network Shell actually get stored, and how do environment variables tie in to all of that?

DMR

Wombat At Large

Team Colleague

7,229 posts since Dec 2003

Reputation Points: 221

Solved Threads: 370

Er.. cos the GUI wants to execute %sytemroot%\system32\netsh interface set ip "Local area connection" 10.10.10.101 255.255.255.0 10.10.10.1

but %sytemroot% = "" so no can do.

What's more worrying is that it died too quietly.

Veteran Poster

1,182 posts since Feb 2005

Reputation Points: 262

Solved Threads: 68

Er.. cos the GUI wants to execute %sytemroot%\system32\netsh... ...What's more worrying is that it died too quietly.

Exactly. It isn't as though the netsh command has exclusive rights to the use of the %systemroot% variable, after all; I'd think that alot of programs/commands would be affected.

DMR

Wombat At Large

Team Colleague

7,229 posts since Dec 2003

Reputation Points: 221

Solved Threads: 370

Exactly. It isn't as though the netsh command has exclusive rights to the use of the %systemroot% variable, after all; I'd think that a lot of programs/commands would be affected.

I was very surprised that there were not too many others things effected by this variable not being set.!! But now we know where to look FIRST, if this happens again..!!!

BTW.. DMR ... Did you have a good weekend for your birthday.??

I had a few drinks for you... Boy you sure can drink.!@!

Regards
:cheesy: