Trouble getting IP address from router

I have a PC's connecting via a wireless network which was working fine up
until a little while ago. When TCP/IP is set to Obtain IP automatically it
comes up with the IP address 169.254.92.143 rather than the Intranet IP it
should be getting from the Router.

I suspect one of my children has loaded some spyware or something else that
is causing this, but I have used McAfee to check and remove everything it
can find but I still have the problem with the IP being set to this value. I
have checked the router and card in other PC's so the problem is within the
one PC.

If I set a fixed IP for the TCP/IP settings then the Network works but the
PC cannot access the internet.

Has anyone else experienced this? Any ideas?

with thanks
Dennis Barker

Type ipconfig release and renew and see if you get this.



6613 » 'An operation was attempted on something that is not a socket'?



NOTE: The text in the following Microsoft Knowledge Base article is provided
so that the site search can find this page. Please click the Knowledge Base
link to insure that you are reading the most current information.

Microsoft Knowledge Base article Q817571 contains:

SYMPTOMS

When you try to connect to your network on a computer that obtains an IP
address from a Dynamic Host Configuration Protocol (DHCP) server, you may
receive the following error message:

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


If you assign a static IP address to your computer, you do not receive this
message.

CAUSE

This issue may occur if you have a third-party product installed that uses
Windows sockets and also uses the ipconfig, release, and renew commands. The
Windows sockets registry entries may be corrupted.

RESOLUTION

To resolve this problem, use either of the following methods.

Method 1

If you have only one computer or do not have access to a computer with the
same operating system version and a similar hardware configuration,
Microsoft recommends Method 1.

WARNING: If you use Registry Editor incorrectly, you may cause serious
problems that may require you to reinstall your operating system. Microsoft
cannot guarantee that you can solve problems that result from using Registry
Editor incorrectly. Use Registry Editor at your own risk.
Use Registry Editor to delete the Winsock and Winsock2 registry entries, and
then remove and reinstall TCP/IP.

Delete the Corrupted Registry Entries

1. Click Start, and then click Run.

2. In the Open box, type regedit, and then click OK.

3. In Registry Editor, expand
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es, right-click Winsock,
and then click Delete. When you are prompted to confirm the deletion, click
Yes.

4. Right-click Winsock2, click Delete, and then click Yes.

Remove TCP/IP on a Windows 2000-based Computer

1. Log on to Windows as Administrator.

2. In Control Panel, double-click Network Connections, right-click Local
Area Connection, and then click Properties.

3. Under This component uses the following items, click Internet Protocol
(TCP/IP), and then click Uninstall.

4. Follow the instructions on the screen to remove TCP/IP.

5. Restart the computer when prompted, but click No if you are prompted to
allow Windows to enable a protocol.



Install TCP/IP on a Windows 2000-based Computer

1. Log on to Windows as Administrator.

2. In Control Panel, double-click Network Connections, right-click Local
Area Connection, and then click Properties.

3. Click Install.

4. In the Select Network Component Type dialog box, click Protocol, and then
click Add.

5. Under Network Protocol, click Internet Protocol (TCP/IP), and then click
OK.

6. When the protocol is installed, click Close.

7. Restart the computer.

Reset TCP/IP on a Windows XP Computer

In Windows XP, the TCP/IP stack is a core component of the operating system;
therefore, you cannot remove TCP/IP in Windows XP. In Windows XP, a reset
command is available in the IP context of the NetShell utility. When this
command is run, it rewrites pertinent registry keys that are used by the
TCP/IP stack. This generates the same result as the removal and the
reinstallation of the protocol. To reset TCP/IP, follow these steps:

1. Open a command prompt.

2. Type netsh int ip reset resetlog.txt , and then press ENTER.

For additional information about the NetShell utility (netsh), click the
following article number to view the article in the Microsoft Knowledge
Base:

299357 How to Reset Internet Protocol (TCP/IP) in Windows XP



Method 2

If you are correcting this problem on several computers and you have access
to a working computer with the same operating system version and a similar
hardware configuration, Microsoft recommends Method 2.WARNING: If you use
Registry Editor incorrectly, you may cause serious problems that may require
you to reinstall your operating system. Microsoft cannot guarantee that you
can solve problems that result from using Registry Editor incorrectly. Use
Registry Editor at your own risk.
To resolve this issue, delete the corrupted registry entries, and then
replace them with the registry key information exported from a computer that
has a working installation of TCP/IP. To do this, follow these steps.

Delete the Corrupted Registry Entries

1. Click Start, and then click Run.

2. In the Open box, type regedit, and then click OK.

3. In Registry Editor, expand
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es.

4. Right-click Winsock, and then click Delete. When you are prompted to
confirm the deletion, click Yes.

5. Right-click Winsock2, and then click Delete. When you are prompted to
confirm the deletion, click Yes.

Export the Registry Entries to a Floppy Disk

Note The computer that you are importing the registry entries from must use
the same version of Windows and be either similar to or a duplicate of the
computer that is experiencing the issues described in the "Symptoms" section
of this article.

1. Insert a floppy disk in the floppy disk drive of the computer whose
registry entries you are exporting.

2. Click Start, and then click Run.

3. In the Open box, type regedit, and then click OK.

4. In Registry Editor, expand
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es, and then click
Winsock.

5. Click File, and then click Export.

6. In the Save in box, click 3½ Floppy(A, type a name for the file in the
File name box, and then click Save.

7. Click Winsock2, click File, and then click Export.

8. In the Save in box, click 3½ Floppy(A, type a name for the file in the
File name box, and then click Save.

Note Each .reg file that you save must have a different name.

9. Quit Registry Editor.

Import the Registry Entries from the Floppy Disk

1. Insert the floppy disk that contains the .reg files in the floppy disk
drive of the computer that is experiencing the issue described in the
"Symptoms" section of this article.

2. Start Windows Explorer, click My Computer, and then double-click 3½
Floppy(A.

3. Double-click each .reg file that you created and saved to the floppy disk
in the "Export the Registry Keys to a Floppy Disk" section of this article.
..

4. Click Yes when you are prompted to add information to the registry.

5. Click OK when you receive the message that the information is
successfully entered in the registry.

6. Quit Registry Editor.

"Dennis Barker" <dennis_barker@hotmail.com> wrote in message
news:Yc7yc.1673$sj4.608@news-server.bigpond.net.au...
> I have a PC's connecting via a wireless network which was working fine up
> until a little while ago. When TCP/IP is set to Obtain IP automatically it
> comes up with the IP address 169.254.92.143 rather than the Intranet IP it
> should be getting from the Router.
>
> I suspect one of my children has loaded some spyware or something else
that
> is causing this, but I have used McAfee to check and remove everything it
> can find but I still have the problem with the IP being set to this value.
I
> have checked the router and card in other PC's so the problem is within
the
> one PC.
>
> If I set a fixed IP for the TCP/IP settings then the Network works but the
> PC cannot access the internet.
>
> Has anyone else experienced this? Any ideas?
>
> with tha> De> Dennis Barker
>
>
>

Ty,

Many thanks for your response. I used method 2 since I have one working
Win2K PC and this has fixed the problem.

Your help is greatly appreciated.

Dennis Barker.


"Ty" <ty@microsoftcorp.com> wrote in message
news:%23PEho2wUEHA.1888@TK2MSFTNGP11.phx.gbl...
> Type ipconfig release and renew and see if you get this.
>
>
>
> 6613 » 'An operation was attempted on something that is not a socket'?
>
>
>
> NOTE: The text in the following Microsoft Knowledge Base article is
provided
> so that the site search can find this page. Please click the Knowledge
Base
> link to insure that you are reading the most current information.
>
> Microsoft Knowledge Base article Q817571 contains:
>
> SYMPTOMS
>
> When you try to connect to your network on a computer that obtains an IP
> address from a Dynamic Host Configuration Protocol (DHCP) server, you may
> receive the following error message:
>
> An operation was attempted on something that is not a socket .
>
>
> If you assign a static IP address to your computer, you do not receive
this
> message.
>
> CAUSE
>
> This issue may occur if you have a third-party product installed that uses
> Windows sockets and also uses the ipconfig, release, and renew commands.
The
> Windows sockets registry entries may be corrupted.
>
> RESOLUTION
>
> To resolve this problem, use either of the following methods.
>
> Method 1
>
> If you have only one computer or do not have access to a computer with the
> same operating system version and a similar hardware configuration,
> Microsoft recommends Method 1.
>
> WARNING: If you use Registry Editor incorrectly, you may cause serious
> problems that may require you to reinstall your operating system.
Microsoft
> cannot guarantee that you can solve problems that result from using
Registry
> Editor incorrectly. Use Registry Editor at your own risk.
> Use Registry Editor to delete the Winsock and Winsock2 registry entries,
and
> then remove and reinstall TCP/IP.
>
> Delete the Corrupted Registry Entries
>
> 1. Click Start, and then click Run.
>
> 2. In the Open box, type regedit, and then click OK.
>
> 3. In Registry Editor, expand
> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es, right-click Winsock,
> and then click Delete. When you are prompted to confirm the deletion,
click
> Yes.
>
> 4. Right-click Winsock2, click Delete, and then click Yes.
>
> Remove TCP/IP on a Windows 2000-based Computer
>
> 1. Log on to Windows as Administrator.
>
> 2. In Control Panel, double-click Network Connections, right-click Local
> Area Connection, and then click Properties.
>
> 3. Under This component uses the following items, click Internet Protocol
> (TCP/IP), and then click Uninstall.
>
> 4. Follow the instructions on the screen to remove TCP/IP.
>
> 5. Restart the computer when prompted, but click No if you are prompted to
> allow Windows to enable a protocol.
>
>
>
> Install TCP/IP on a Windows 2000-based Computer
>
> 1. Log on to Windows as Administrator.
>
> 2. In Control Panel, double-click Network Connections, right-click Local
> Area Connection, and then click Properties.
>
> 3. Click Install.
>
> 4. In the Select Network Component Type dialog box, click Protocol, and
then
> click Add.
>
> 5. Under Network Protocol, click Internet Protocol (TCP/IP), and then
click
> OK.
>
> 6. When the protocol is installed, click Close.
>
> 7. Restart the computer.
>
> Reset TCP/IP on a Windows XP Computer
>
> In Windows XP, the TCP/IP stack is a core component of the operating
system;
> therefore, you cannot remove TCP/IP in Windows XP. In Windows XP, a reset
> command is available in the IP context of the NetShell utility. When this
> command is run, it rewrites pertinent registry keys that are used by the
> TCP/IP stack. This generates the same result as the removal and the
> reinstallation of the protocol. To reset TCP/IP, follow these steps:
>
> 1. Open a command prompt.
>
> 2. Type netsh int ip reset resetlog.txt , and then press ENTER.
>
> For additional information about the NetShell utility (netsh), click the
> following article number to view the article in the Microsoft Knowledge
> Base:
>
> 299357 How to Reset Internet Protocol (TCP/IP) in Windows XP
>
>
>
> Method 2
>
> If you are correcting this problem on several computers and you have
access
> to a working computer with the same operating system version and a similar
> hardware configuration, Microsoft recommends Method 2.WARNING: If you use
> Registry Editor incorrectly, you may cause serious problems that may
require
> you to reinstall your operating system. Microsoft cannot guarantee that
you
> can solve problems that result from using Registry Editor incorrectly. Use
> Registry Editor at your own risk.
> To resolve this issue, delete the corrupted registry entries, and then
> replace them with the registry key information exported from a computer
that
> has a working installation of TCP/IP. To do this, follow these steps.
>
> Delete the Corrupted Registry Entries
>
> 1. Click Start, and then click Run.
>
> 2. In the Open box, type regedit, and then click OK.
>
> 3. In Registry Editor, expand
> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es.
>
> 4. Right-click Winsock, and then click Delete. When you are prompted to
> confirm the deletion, click Yes.
>
> 5. Right-click Winsock2, and then click Delete. When you are prompted to
> confirm the deletion, click Yes.
>
> Export the Registry Entries to a Floppy Disk
>
> Note The computer that you are importing the registry entries from must
use
> the same version of Windows and be either similar to or a duplicate of the
> computer that is experiencing the issues described in the "Symptoms"
section
> of this article.
>
> 1. Insert a floppy disk in the floppy disk drive of the computer whose
> registry entries you are exporting.
>
> 2. Click Start, and then click Run.
>
> 3. In the Open box, type regedit, and then click OK.
>
> 4. In Registry Editor, expand
> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es, and then click
> Winsock.
>
> 5. Click File, and then click Export.
>
> 6. In the Save in box, click 3½ Floppy(A, type a name for the file in
the
> File name box, and then click Save.
>
> 7. Click Winsock2, click File, and then click Export.
>
> 8. In the Save in box, click 3½ Floppy(A, type a name for the file in
the
> File name box, and then click Save.
>
> Note Each .reg file that you save must have a different name.
>
> 9. Quit Registry Editor.
>
> Import the Registry Entries from the Floppy Disk
>
> 1. Insert the floppy disk that contains the .reg files in the floppy disk
> drive of the computer that is experiencing the issue described in the
> "Symptoms" section of this article.
>
> 2. Start Windows Explorer, click My Computer, and then double-click 3½
> Floppy(A.
>
> 3. Double-click each .reg file that you created and saved to the floppy
disk
> in the "Export the Registry Keys to a Floppy Disk" section of this
article.
> .
>
> 4. Click Yes when you are prompted to add information to the registry.
>
> 5. Click OK when you receive the message that the information is
> successfully entered in the registry.
>
> 6. Quit Registry Editor.
>
> "Dennis Barker" <dennis_barker@hotmail.com> wrote in message
> news:Yc7yc.1673$sj4.608@news-server.bigpond.net.au...
> > I have a PC's connecting via a wireless network which was working fine
up
> > until a little while ago. When TCP/IP is set to Obtain IP automatically
it
> > comes up with the IP address 169.254.92.143 rather than the Intranet IP
it
> > should be getting from the Router.
> >
> > I suspect one of my children has loaded some spyware or something else
> that
> > is causing this, but I have used McAfee to check and remove everything
it
> > can find but I still have the problem with the IP being set to this
value.
> I
> > have checked the router and card in other PC's so the problem is within
> the
> > one PC.
> >
> > If I set a fixed IP for the TCP/IP settings then the Network works but
the
> > PC cannot access the internet.
> >
> > Has anyone else experienced this? Any ideas?
> >
> > with thanks
> > Dennis Barker
> >
> >
> >
>
>