IP Address Problem

I have two computers that network, and connect to the internet, thought
a Speedtouch 716 DSL router.

One computer appears to be having hard disk problems and has just had a
major crash. I have got it running again, having run chkdsk, but that
computer can no longer access the network.

I suspect that it is an IP issue as, if I try the "repair" option, I get
a box saying "Windows could not finish repairing the problem because the
following action cannot be completed: Renewing your IP address".

When I check the status, it shows packets sent but none received.

When I check the devices from the other computer (the admin computer),
the one I am having problems with is shown as inactive.

The computer is hard wired and I have checked the physical connections.

Can someone please help me with advise as to correcting this problem?

--
Howard Neil


Howard Neil

In article <45d48f41$0$8725$(E-Mail Removed)>, Howard
Neil
(E-Mail Removed) says...
> I have two computers that network, and connect to the internet, thought
> a Speedtouch 716 DSL router.
>
> One computer appears to be having hard disk problems and has just had a
> major crash. I have got it running again, having run chkdsk, but that
> computer can no longer access the network.
>
> I suspect that it is an IP issue as, if I try the "repair" option, I get
> a box saying "Windows could not finish repairing the problem because the
> following action cannot be completed: Renewing your IP address".
>
> When I check the status, it shows packets sent but none received.
>
> When I check the devices from the other computer (the admin computer),
> the one I am having problems with is shown as inactive.
>
> The computer is hard wired and I have checked the physical connections.
>
> Can someone please help me with advise as to correcting this problem?
>
>
Try uninstalling and reinstalling the network drivers (from fresh media
rather than using anything already on the disk).
But msybe you should get a new hard drive first.

Rob Morley wrote:

> Try uninstalling and reinstalling the network drivers (from fresh media
> rather than using anything already on the disk).
> But msybe you should get a new hard drive first.
>

Thanks for the suggestion. I have now tried uninstalling and
reinstalling the network drivers but it has not corrected the problem.

Since I first posted, I have tried a couple of things and have made a
little progress.

I went to the Internet Protocol (TCP/IP) Properties window and
configured the IP address and subnet mask to that shown in the
Speedtouch control panel. I was then able to access the rest of the
network but still could not access the internet from that computer.

If I reset the IP address and subnet mask, in the Internet Protocol
(TCP/IP) Properties window, to "obtain an IP address automatically", the
network connect is lost.

So, I now have connection to my own network (which is through the
router) but still nothing to the internet.

The new hard disk will soon be on order (it's my wife's computer and she
takes a little convincing) but I am concerned that this problem will
still exist after the change of disk.

Any other suggestions, please?


--
Howard Neil

In article <45d6d07b$0$8726$(E-Mail Removed)>, Howard
Neil
(E-Mail Removed) says...
> Rob Morley wrote:
>
> > Try uninstalling and reinstalling the network drivers (from fresh media
> > rather than using anything already on the disk).
> > But msybe you should get a new hard drive first.
> >
>
> Thanks for the suggestion. I have now tried uninstalling and
> reinstalling the network drivers but it has not corrected the problem.
>
> Since I first posted, I have tried a couple of things and have made a
> little progress.
>
> I went to the Internet Protocol (TCP/IP) Properties window and
> configured the IP address and subnet mask to that shown in the
> Speedtouch control panel. I was then able to access the rest of the
> network but still could not access the internet from that computer.
>
Have you set the gateway to the router address, and DNS to whatever DNS
servers your ISP provides (or the router if it has a DNS proxy)?

Rob Morley wrote:
> In article <45d6d07b$0$8726$(E-Mail Removed)>, Howard
> Neil

>> Since I first posted, I have tried a couple of things and have made a
>> little progress.
>>
>> I went to the Internet Protocol (TCP/IP) Properties window and
>> configured the IP address and subnet mask to that shown in the
>> Speedtouch control panel. I was then able to access the rest of the
>> network but still could not access the internet from that computer.
>>
> Have you set the gateway to the router address, and DNS to whatever DNS
> servers your ISP provides (or the router if it has a DNS proxy)?

Well, I *think* I have the gateway set to the correct router address. I
have used the one that calls up the router control panel in browser of
my working computer. The DNS is set to the correct servers (the same as
in the computer that is working correctly).

--
Howard Neil

Howard Neil wrote:
> Rob Morley wrote:
>> In article <45d6d07b$0$8726$(E-Mail Removed)>,
>> Howard Neil
>
>>> Since I first posted, I have tried a couple of things and have made a
>>> little progress.
>>>
>>> I went to the Internet Protocol (TCP/IP) Properties window and
>>> configured the IP address and subnet mask to that shown in the
>>> Speedtouch control panel. I was then able to access the rest of the
>>> network but still could not access the internet from that computer.
>>>
>> Have you set the gateway to the router address, and DNS to whatever
>> DNS servers your ISP provides (or the router if it has a DNS proxy)?
>
> Well, I *think* I have the gateway set to the correct router address. I
> have used the one that calls up the router control panel in browser of
> my working computer. The DNS is set to the correct servers (the same as
> in the computer that is working correctly).
>
Have you tried resetting your TCP/IP stack?
http://support.microsoft.com/default...;en-us;q299357

Kev wrote:

> Have you tried resetting your TCP/IP stack?
> http://support.microsoft.com/default...;en-us;q299357
>

Yes, I have done that. It made no difference unfortunately.

--
Howard Neil

On Sat, 17 Feb 2007 12:09:34 +0000, Howard Neil
<(E-Mail Removed)> wrote:

>Kev wrote:
>
>> Have you tried resetting your TCP/IP stack?
>> http://support.microsoft.com/default...;en-us;q299357
>>
>
>Yes, I have done that. It made no difference unfortunately.


Being heavily involved with our local wireless broadband system I can
thoroughly recommend "Network Magic" from
http://www1.networkmagic.com/ for network diagnostics etc

HTH

In article <45d6f07e$0$8725$(E-Mail Removed)>, Howard
Neil
(E-Mail Removed) says...
> Kev wrote:
>
> > Have you tried resetting your TCP/IP stack?
> > http://support.microsoft.com/default...;en-us;q299357
> >
>
> Yes, I have done that. It made no difference unfortunately.
>
>
What addresses are the various devices on your network using?

Robert Winstanley wrote:
> On Sat, 17 Feb 2007 12:09:34 +0000, Howard Neil
> <(E-Mail Removed)> wrote:
>
>> Kev wrote:
>>
>>> Have you tried resetting your TCP/IP stack?
>>> http://support.microsoft.com/default...;en-us;q299357
>>>
>> Yes, I have done that. It made no difference unfortunately.
>
>
> Being heavily involved with our local wireless broadband system I can
> thoroughly recommend "Network Magic" from
> http://www1.networkmagic.com/ for network diagnostics etc

Thank you, that program looks really useful. I have downloaded it and
will keep it for future use. However, I have managed to solve the
problem just a couple of minutes before I read your post. I will outline
the solution here, in case anyone else gets the same problem.

A program that auto updates via the internet tried to run. Of course it
failed and it left the error message "cannot allocate socket". I had not
seen that error message before so Googled for it.

I found the information that this can happen if the Winsock is damaged
by corruption to programs that modify the Winsock. I downloaded the
program WinSock XP Fix 1.2 available here:-

http://www.majorgeeks.com/download.php?det=4372

It worked. All I have to do now is correct the programs that caused the
problem in the first place and install a new hard disk.

Thank you to everyone who helped. Even if the suggestions didn't
succeed, they did help me understand the problem better.



--
Howard Neil