A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Microsoft Windows XP » Networking and the Internet with Windows XP
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

LAN conn status shows Automatic Private Address



 
 
Thread Tools Display Modes
  #1  
Old March 24th 04, 04:12 AM
Ray
external usenet poster
 
Posts: n/a
Default LAN conn status shows Automatic Private Address

Instead of Asigned by DHCP

I have a 2 hard drive system with XP Pro on both. I boot one for myself, my
wife boots the other for herself. Hers works fine, mine is the one I
described.

All of the properties are set correctly, I've checked a million times and
compared them to hers. I have restarted many times, and I have reset the
router and the modem many times. I have even installed XP again, with no
luck. I suspect a corupted svhost.exe due to malware, but that's just a
guess...

If you have something for me to try, please share...

TIA,
Ray



Ads
  #2  
Old March 24th 04, 04:27 AM
XPUSER
external usenet poster
 
Posts: n/a
Default LAN conn status shows Automatic Private Address

"Ray" none wrote in message ...
Instead of Asigned by DHCP

I have a 2 hard drive system with XP Pro on both. I boot one for myself, my
wife boots the other for herself. Hers works fine, mine is the one I
described.

All of the properties are set correctly, I've checked a million times and
compared them to hers. I have restarted many times, and I have reset the
router and the modem many times. I have even installed XP again, with no
luck. I suspect a corupted svhost.exe due to malware, but that's just a
guess...

If you have something for me to try, please share...

TIA,
Ray

================================================== =

Please read this whole reply before proceeding with any suggestions.

Issue:

On this XP Home/Pro computer,
when trying to browse the Internet,
you are getting "Page Cannot Be Displayed" and
when you go to the command prompt window
(Start Run cmd)
and run ipconfig /all, you get an APIPA
(Automatic Private Internet Protocol Address)
in the form of 169.254.x.x.
Then immediately run ipconfig /renew, you get this error message:

"An operation was attempted on something that is not a socket"

or

"Unable to contact DHCP server"

If so, you probably have a damaged winsock2 key in the registry.

You should check System Information (winmsd)
START RUN - type in winmsd and click OK
Note the value for the Windows Directory (Usually C:\Windows but not always)
Then expand Components / Network / click on Protocol -
if the section headings item of "Name" have a value
starting with anything other than MSAFD or RSVP
then that is probably what is causing the problem.

Examples:

MSAFD Tcpip [TCP/IP]
MSAFD Tcpip [UDP/IP]
RSVP UDP Service Provider
RSVP TCP Service Provider
MSAFD NetBIOS [\Device\NetBT_Tcpip...
and so on

It may be a third-party firewall or a Spyware or a Virus.
("New.Net" is a common spyware for example)
Make sure that MSCONFIG (System Configuration Utility) is in Normal Startup
and then see if uninstalling the third party firewall
(best done from its own uninstall program if available)
or the Spyware from Add Remove Programs will
resolve the issue. If it's a virus, then only an Anti Virus Program
will be able to deal with that.

You may want to try downloading either Ad-Aware 6 or Spybot
to another computer and then installing one of them on the infected XP Home/Pro
computer and try to wipe out Spyware and see if that resolves the issue.

Ad-aware 6.0 build 181
http://www.pcworld.com/downloads/fil...id,7423,00.asp

Spybot - Search & Destroy 1.2
http://www.1usa.com/downloads/spybotsd/index.html


If none of that works or is possible, you could try this method
for replacing the winsock and winsock2 registry keys:

Uninstall any third-party proxy software or firewall programs before proceeding.

Step 1: Delete registry keys

A)Open Regedit from the Run line (Start Run - regedit)

B)Go to both of the following keys, EXPORT each of them, and then delete them:
(To export a key, you right click on it and choose "export" - you can choose where to export them to -
DESKTOP is handy -
and you need to type in a file name such as "exported Winsock key" / "exported WinSock2 key"
and then click on SAVE)

HKLM\SYSTEM\CurrentControlSet\Services\Winsock
HKLM\SYSTEM\CurrentControlSet\Services\WinSock2

C)Restart the computer

NOTE: It is important to restart the computer after deleting the Winsock keys.
Doing so causes the XP operating system to recreate shell entries for those two
keys. If this is not done, the next step does not work correctly.

Step 2: Install TCP/IP on top of itself

Go to Control Panel | Network Connections

A)Open the properties window of the network connection (Local Area Connection)
B)Click Install
C)Click Protocol, then Add
D)Click Have Disk
E)Type the path to the \%systemroot%\inf folder (usually C:\Windows\inf) and click OK
(if you try to click Browse, then browse to the \inf folder,
it may not show up in the list)
F)You should now see "Internet Protocol (TCP/IP)" in the list of available
protocols. Select it and click OK.
G)Restart the computer

When the computer reboots you will have functional Winsock keys.
If so, then be sure to delete the exported winsock and winsock2 reg files.
(You don't want to accidentally put them back in the registry)

Side effects and possible problems:

This method will restore basic functionality to the Winsock keys, but is not a
complete rebuild. On a default install of Windows XP the registry key:
HKLM\SYSTEM\CurrentControlSet\Services\Winsock2\
Parameters\Protocol_Catalog9\Catalog_Entries will have 11 sub-keys.
When applying this method, the Catalog_Entries will only have 3 sub-keys.
However, it works and there does not appear to be any side effects.
The missing entries relate back to the:
HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Param eters\Interfaces key.
Also, third-party proxy software or firewalls may need to be reinstalled.


================================================== ========


  #3  
Old March 25th 04, 02:22 PM
Ray C
external usenet poster
 
Posts: n/a
Default LAN conn status shows Automatic Private Address


"XPUSER" wrote in message
...
"Ray" none wrote in message ...
Instead of Asigned by DHCP

I have a 2 hard drive system with XP Pro on both. I boot one for myself,

my
wife boots the other for herself. Hers works fine, mine is the one I
described.

All of the properties are set correctly, I've checked a million times and
compared them to hers. I have restarted many times, and I have reset the
router and the modem many times. I have even installed XP again, with no
luck. I suspect a corupted svhost.exe due to malware, but that's just a
guess...

If you have something for me to try, please share...

TIA,
Ray

================================================== =

Please read this whole reply before proceeding with any suggestions.

Issue:

On this XP Home/Pro computer,
when trying to browse the Internet,
you are getting "Page Cannot Be Displayed" and
when you go to the command prompt window
(Start Run cmd)
and run ipconfig /all, you get an APIPA
(Automatic Private Internet Protocol Address)
in the form of 169.254.x.x.
Then immediately run ipconfig /renew, you get this error message:

"An operation was attempted on something that is not a socket"

or

"Unable to contact DHCP server"

If so, you probably have a damaged winsock2 key in the registry.

You should check System Information (winmsd)
START RUN - type in winmsd and click OK
Note the value for the Windows Directory (Usually C:\Windows but not always)
Then expand Components / Network / click on Protocol -
if the section headings item of "Name" have a value
starting with anything other than MSAFD or RSVP
then that is probably what is causing the problem.

Examples:

MSAFD Tcpip [TCP/IP]
MSAFD Tcpip [UDP/IP]
RSVP UDP Service Provider
RSVP TCP Service Provider
MSAFD NetBIOS [\Device\NetBT_Tcpip...
and so on

It may be a third-party firewall or a Spyware or a Virus.
("New.Net" is a common spyware for example)
Make sure that MSCONFIG (System Configuration Utility) is in Normal Startup
and then see if uninstalling the third party firewall
(best done from its own uninstall program if available)
or the Spyware from Add Remove Programs will
resolve the issue. If it's a virus, then only an Anti Virus Program
will be able to deal with that.

You may want to try downloading either Ad-Aware 6 or Spybot
to another computer and then installing one of them on the infected XP
Home/Pro
computer and try to wipe out Spyware and see if that resolves the issue.

Ad-aware 6.0 build 181
http://www.pcworld.com/downloads/fil...id,7423,00.asp

Spybot - Search & Destroy 1.2
http://www.1usa.com/downloads/spybotsd/index.html


If none of that works or is possible, you could try this method
for replacing the winsock and winsock2 registry keys:

Uninstall any third-party proxy software or firewall programs before
proceeding.

Step 1: Delete registry keys

A)Open Regedit from the Run line (Start Run - regedit)

B)Go to both of the following keys, EXPORT each of them, and then delete
them:
(To export a key, you right click on it and choose "export" - you can choose
where to export them to -
DESKTOP is handy -
and you need to type in a file name such as "exported Winsock key" /
"exported WinSock2 key"
and then click on SAVE)

HKLM\SYSTEM\CurrentControlSet\Services\Winsock
HKLM\SYSTEM\CurrentControlSet\Services\WinSock2

C)Restart the computer

NOTE: It is important to restart the computer after deleting the Winsock
keys.
Doing so causes the XP operating system to recreate shell entries for those
two
keys. If this is not done, the next step does not work correctly.

Step 2: Install TCP/IP on top of itself

Go to Control Panel | Network Connections

A)Open the properties window of the network connection (Local Area
Connection)
B)Click Install
C)Click Protocol, then Add
D)Click Have Disk
E)Type the path to the \%systemroot%\inf folder (usually C:\Windows\inf) and
click OK
(if you try to click Browse, then browse to the \inf folder,
it may not show up in the list)
F)You should now see "Internet Protocol (TCP/IP)" in the list of available
protocols. Select it and click OK.
G)Restart the computer

When the computer reboots you will have functional Winsock keys.
If so, then be sure to delete the exported winsock and winsock2 reg files.
(You don't want to accidentally put them back in the registry)

Side effects and possible problems:

This method will restore basic functionality to the Winsock keys, but is not
a
complete rebuild. On a default install of Windows XP the registry key:
HKLM\SYSTEM\CurrentControlSet\Services\Winsock2\
Parameters\Protocol_Catalog9\Catalog_Entries will have 11 sub-keys.
When applying this method, the Catalog_Entries will only have 3 sub-keys.
However, it works and there does not appear to be any side effects.
The missing entries relate back to the:
HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Param eters\Interfaces key.
Also, third-party proxy software or firewalls may need to be reinstalled.


================================================== ========

XPUSER,

Thanks for the response,

I followed all of the above twice, and had no success, I plan to try it
again tonight.

I didn't mention this before because I didn't want to give the impression
that AdAware was at fault, but all this happened after I had just updated,
and scanned with Spybot S & D, SpywareBlaster, CWShredder, and AdAware, in
that order. I was actually in the middle of an AdAware scan when it locked
up solid. I couldn't even access task manager to end the process. I
finally turned off the power, and have had this problem since. I'm
relatively certain it's not a virus, I have an updated Nod32 as virus
protection, and my experience with it suggests to me it is excellent!

There is also another PC which accesses the internet through the same router
and modem without any problems.

If there are any other suggestions, I'll sure listen...

TIA

Ray


  #4  
Old March 25th 04, 02:47 PM
Ray C
external usenet poster
 
Posts: n/a
Default LAN conn status shows Automatic Private Address


wrote in message
...

-----Original Message-----
Instead of Asigned by DHCP

I have a 2 hard drive system with XP Pro on both. I boot

one for myself, my
wife boots the other for herself. Hers works fine, mine

is the one I
described.

All of the properties are set correctly, I've checked a

million times and
compared them to hers. I have restarted many times, and

I have reset the
router and the modem many times. I have even installed

XP again, with no
luck. I suspect a corupted svhost.exe due to malware,

but that's just a
guess...

If you have something for me to try, please share...

TIA,
Ray



.



ray try to switch the hard drives make your hard drive the
slave...see if that will work


Can you enlighten me as to why? I ask this before I do it because it is
not a simple task. My hard drive is attached with double sided servo tape
(which is a PITA to remove), and it must be removed to access the other
drive, which must also be removed before I can change the switches. I also
don't think either is set up as a slave, if my memory serves me correctly, I
believe it is cable select on both HD's (if that matters)

Ray


  #5  
Old March 25th 04, 10:29 PM
MikeM
external usenet poster
 
Posts: n/a
Default LAN conn status shows Automatic Private Address

Xref: kermit microsoft.public.windowsxp.network_web:194152

Had exactly the same problem described (wireless lan failed to connect to router), and followed XPUSER's instructions. Fixed in less than 15 mins. Many thanks.
  #6  
Old March 26th 04, 03:47 AM
Ray Carr
external usenet poster
 
Posts: n/a
Default LAN conn status shows Automatic Private Address


"XPUSER" wrote in message ...
"Ray" none wrote in message ...
Instead of Asigned by DHCP

I have a 2 hard drive system with XP Pro on both. I boot one for myself, my
wife boots the other for herself. Hers works fine, mine is the one I
described.

All of the properties are set correctly, I've checked a million times and
compared them to hers. I have restarted many times, and I have reset the
router and the modem many times. I have even installed XP again, with no
luck. I suspect a corupted svhost.exe due to malware, but that's just a
guess...

If you have something for me to try, please share...

TIA,
Ray

================================================== =

Please read this whole reply before proceeding with any suggestions.

Issue:

On this XP Home/Pro computer,
when trying to browse the Internet,
you are getting "Page Cannot Be Displayed" and
when you go to the command prompt window
(Start Run cmd)
and run ipconfig /all, you get an APIPA
(Automatic Private Internet Protocol Address)
in the form of 169.254.x.x.
Then immediately run ipconfig /renew, you get this error message:

"An operation was attempted on something that is not a socket"

or

"Unable to contact DHCP server"

If so, you probably have a damaged winsock2 key in the registry.

You should check System Information (winmsd)
START RUN - type in winmsd and click OK
Note the value for the Windows Directory (Usually C:\Windows but not always)
Then expand Components / Network / click on Protocol -
if the section headings item of "Name" have a value
starting with anything other than MSAFD or RSVP
then that is probably what is causing the problem.

Examples:

MSAFD Tcpip [TCP/IP]
MSAFD Tcpip [UDP/IP]
RSVP UDP Service Provider
RSVP TCP Service Provider
MSAFD NetBIOS [\Device\NetBT_Tcpip...
and so on

It may be a third-party firewall or a Spyware or a Virus.
("New.Net" is a common spyware for example)
Make sure that MSCONFIG (System Configuration Utility) is in Normal Startup
and then see if uninstalling the third party firewall
(best done from its own uninstall program if available)
or the Spyware from Add Remove Programs will
resolve the issue. If it's a virus, then only an Anti Virus Program
will be able to deal with that.

You may want to try downloading either Ad-Aware 6 or Spybot
to another computer and then installing one of them on the infected XP Home/Pro
computer and try to wipe out Spyware and see if that resolves the issue.

Ad-aware 6.0 build 181
http://www.pcworld.com/downloads/fil...id,7423,00.asp

Spybot - Search & Destroy 1.2
http://www.1usa.com/downloads/spybotsd/index.html


If none of that works or is possible, you could try this method
for replacing the winsock and winsock2 registry keys:

Uninstall any third-party proxy software or firewall programs before proceeding.

Step 1: Delete registry keys

A)Open Regedit from the Run line (Start Run - regedit)

B)Go to both of the following keys, EXPORT each of them, and then delete them:
(To export a key, you right click on it and choose "export" - you can choose where to export them to -
DESKTOP is handy -
and you need to type in a file name such as "exported Winsock key" / "exported WinSock2 key"
and then click on SAVE)

HKLM\SYSTEM\CurrentControlSet\Services\Winsock
HKLM\SYSTEM\CurrentControlSet\Services\WinSock2

C)Restart the computer

NOTE: It is important to restart the computer after deleting the Winsock keys.
Doing so causes the XP operating system to recreate shell entries for those two
keys. If this is not done, the next step does not work correctly.

Step 2: Install TCP/IP on top of itself

Go to Control Panel | Network Connections

A)Open the properties window of the network connection (Local Area Connection)
B)Click Install
C)Click Protocol, then Add
D)Click Have Disk
E)Type the path to the \%systemroot%\inf folder (usually C:\Windows\inf) and click OK
(if you try to click Browse, then browse to the \inf folder,
it may not show up in the list)
F)You should now see "Internet Protocol (TCP/IP)" in the list of available
protocols. Select it and click OK.
G)Restart the computer

When the computer reboots you will have functional Winsock keys.
If so, then be sure to delete the exported winsock and winsock2 reg files.
(You don't want to accidentally put them back in the registry)

Side effects and possible problems:

This method will restore basic functionality to the Winsock keys, but is not a
complete rebuild. On a default install of Windows XP the registry key:
HKLM\SYSTEM\CurrentControlSet\Services\Winsock2\
Parameters\Protocol_Catalog9\Catalog_Entries will have 11 sub-keys.
When applying this method, the Catalog_Entries will only have 3 sub-keys.
However, it works and there does not appear to be any side effects.
The missing entries relate back to the:
HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Param eters\Interfaces key.
Also, third-party proxy software or firewalls may need to be reinstalled.


================================================== ========
XPUSER,

Well I tried again tonight 3 times, it took killing all processes that weren't esential to finally get it fixed. Now I wonder if I'm infected with something, I did notice a few processes I don't remember seeing before, and I keep a pretty close eye on these things.

Anyway I'm fixed and I thank you, this has saved me many, many hours of re-instalations, tweaks, and settings changes...

Thanks,
Ray

 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off






All times are GMT +1. The time now is 10:01 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 PCbanter.
The comments are property of their posters.