 |  |  |  |  |  |  |  |
Static TCP/IP Setting not saving...
 |
Hi Folks...
I am having a little problem with an IBM Thinkpad with Windows XP & SP2 installed.
I have updated all drivers by the way..
I "AM" able to network successfully when the IP Settings are set for "Obtain an IP address automatically" & "obtain DNS server address automatically".. BUT once I enter a static address with subnet mask, default gateway Etc.. it accepts the details, but then I close the dialog and when I come back in to make sure all is set OK, all static details have disappeared and I am left with the automatic setting once again./??
This is the only machine on the network that this is happening to...
The Network card is: Broadcom NetXtreme Fast Ethernet
Has anybody seen this and if so, what can I do to rememdy the situation.???
Regards
Julius
I am having a little problem with an IBM Thinkpad with Windows XP & SP2 installed.
I have updated all drivers by the way..
I "AM" able to network successfully when the IP Settings are set for "Obtain an IP address automatically" & "obtain DNS server address automatically".. BUT once I enter a static address with subnet mask, default gateway Etc.. it accepts the details, but then I close the dialog and when I come back in to make sure all is set OK, all static details have disappeared and I am left with the automatic setting once again./??
This is the only machine on the network that this is happening to...
The Network card is: Broadcom NetXtreme Fast Ethernet
Has anybody seen this and if so, what can I do to rememdy the situation.???
Regards
Julius
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?
"May the Wombat of Happiness snuffle through your underbrush."
- Ancient Aborigine blessing
Please do not contact me by email or PM for help. We're all volunteers here, and only have so much free time to dedicate to our efforts.
However, if I've been working on a thread with you already, and seem to have "forgotten" your thread, please do send me a message. I try not to let things slip through the cracks, but it does happen sometimes.
- Ancient Aborigine blessing
Please do not contact me by email or PM for help. We're all volunteers here, and only have so much free time to dedicate to our efforts.
However, if I've been working on a thread with you already, and seem to have "forgotten" your thread, please do send me a message. I try not to let things slip through the cracks, but it does happen sometimes.
•
•
•
•
Originally Posted by DMR
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?
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.??
•
•
Join Date: Feb 2005
Posts: 1,181
Reputation: 
Solved Threads: 67
First thing to try is to right click the LAN connection in Network Connections and choose "Repair"
•
•
•
•
Originally Posted by hollystyles
First thing to try is to right click the LAN connection in Network Connections and choose "Repair"
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.
•
•
Join Date: Feb 2005
Posts: 1,181
Reputation:
Solved Threads: 67
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
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
Last edited by hollystyles; Jun 8th, 2006 at 5:40 am.
•
•
•
•
Originally Posted by hollystyles
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
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..!!
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 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...
"May the Wombat of Happiness snuffle through your underbrush."
- Ancient Aborigine blessing
Please do not contact me by email or PM for help. We're all volunteers here, and only have so much free time to dedicate to our efforts.
However, if I've been working on a thread with you already, and seem to have "forgotten" your thread, please do send me a message. I try not to let things slip through the cracks, but it does happen sometimes.
- Ancient Aborigine blessing
Please do not contact me by email or PM for help. We're all volunteers here, and only have so much free time to dedicate to our efforts.
However, if I've been working on a thread with you already, and seem to have "forgotten" your thread, please do send me a message. I try not to let things slip through the cracks, but it does happen sometimes.
•
•
•
•
Originally Posted by DMR
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...
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
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:
Last edited by DMR; Jun 9th, 2006 at 3:04 am.
"May the Wombat of Happiness snuffle through your underbrush."
- Ancient Aborigine blessing
Please do not contact me by email or PM for help. We're all volunteers here, and only have so much free time to dedicate to our efforts.
However, if I've been working on a thread with you already, and seem to have "forgotten" your thread, please do send me a message. I try not to let things slip through the cracks, but it does happen sometimes.
- Ancient Aborigine blessing
Please do not contact me by email or PM for help. We're all volunteers here, and only have so much free time to dedicate to our efforts.
However, if I've been working on a thread with you already, and seem to have "forgotten" your thread, please do send me a message. I try not to let things slip through the cracks, but it does happen sometimes.
|
Other Threads in the Networking Hardware Configuration Forum
- Previous Thread: networking
- Next Thread: New modem/router, no ping, no network: HELP
| Thread Tools | Search this Thread |
You need to join our community in order to build your list of favorite forums. You can visit the forum index for a listing of all forums.
Related Forum Features
Latest Networking Hardware Configuration Posts
802.11 802.11n bluetooth british broadband browserproblems bt connectionproblem connectivity cpu data desktop dual gigabyte hardware infrastructure internet memory network networking news program rdimm reliability riched20.dll routers server storage survey technology telecoms troubleshoot uk upgrade videoconferencing view virgin wireless wirelessnetworking
