Help! Network stopped working from WinXP Tablet PC

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello,

I would appreciate help in solving the following problem.

The network has stopped working from my Windows XP Tablet PC ed.
It is an Averatec C3500 and the router/gateway is D-Link DL-614+.
It used to work like a charm, but now, a ping to the gateway fails.

First, I noticed it in the wireless then I saw the same problem with
ethernet cable. I tried both assigning fixed IP address as well as DHCP.

When set to DHCP, MAC addresses of both interfaces show up on the DL-614+
DHCP Client Table.

Running "ipconfig /all" shows IP addresses properly, but a ping to the IP
address of the gateway always times out.

The gateway is set to 192.168.0.1 and the DHCP range is set to 192.168.0.100
to 192.168.0.199, and the interfaces are assigned proper IP addresses in that
range.

What could be wrong?
What could I be doing wrong?
How to correct this so that it can be back on the 'net?

I called Averatec and they told me to re-image the hard disk.
That means I'll have to backup all user data, not to mention
re-installing everything.

If I have no option but to re-install from scratch, what is
the easiest way to back everything up on a series of CD's?

Thanks.
 
Hello,

I would appreciate help in solving the following problem.

The network has stopped working from my Windows XP Tablet PC ed.
It is an Averatec C3500 and the router/gateway is D-Link DL-614+.
It used to work like a charm, but now, a ping to the gateway fails.

First, I noticed it in the wireless then I saw the same problem with
ethernet cable. I tried both assigning fixed IP address as well as DHCP.

When set to DHCP, MAC addresses of both interfaces show up on the DL-614+
DHCP Client Table.

Running "ipconfig /all" shows IP addresses properly, but a ping to the IP
address of the gateway always times out.

The gateway is set to 192.168.0.1 and the DHCP range is set to 192.168.0.100
to 192.168.0.199, and the interfaces are assigned proper IP addresses in that
range.

What could be wrong?
What could I be doing wrong?
How to correct this so that it can be back on the 'net?

I called Averatec and they told me to re-image the hard disk.
That means I'll have to backup all user data, not to mention
re-installing everything.

If I have no option but to re-install from scratch, what is
the easiest way to back everything up on a series of CD's?

Thanks.
Click to expand...

Sounds like an LSP / Winsock / TCP/IP problem.
<http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html
 
Thanks for the message Chuck !
And thanks a bunch for your web page too !!

Yes, it looks very much like a tcp/ip problem but I just can't figure this
out.

btw, it is running Win XP Service Pack 2
Build 2600.xpsp_sp2_gdr.050301-1519 : Service Pack 2

Following your web page, I tried 6 different techniques

1. LSP-Fix. :: tried, didn't work

2. WinsockFix. :: tried, didn't work

3. Winsock2 Fix. :: didn't try this one,
as description doesn;t match my situation

4. WinSock XP Fix. :: tried, didnt work

5. Remove registry entries and re-install tcp/ip
:: tried, didn;t work

6. run "netsh winsock reset catalog"
:: tried, didn't work

7. run "netsh int ip reset"
as described in http://support.microsoft.com/?id=299357
:: tried, didn;t work

I also followed "How to troubleshoot TCP/IP .."
http://support.microsoft.com/kb/314067/

I can
(1) ping 127.0.0.1 :: ok
(2) ping ip_of_local_host :: ok
(3) ping ip_of_gateway :: fails w time out
and ping from other machines also fail w time out

From above web page of MicroSoft, it says it is
"an issue with the network adapter, the router or
gateway device, the cabling, or other connectivity hardware"

However, exactly the same problem occurs whether I
use WiFi or ethernet.
Another pc can connect successfully to the same gateway
using the same piece of ethernet cable or WiFi with
same settings.

So, could this be a hardware problem?
or could it be software problem?

Thanks again.
 
Thanks for the message Chuck !
And thanks a bunch for your web page too !!

Yes, it looks very much like a tcp/ip problem but I just can't figure this
out.

btw, it is running Win XP Service Pack 2
Build 2600.xpsp_sp2_gdr.050301-1519 : Service Pack 2

Following your web page, I tried 6 different techniques

1. LSP-Fix. :: tried, didn't work

2. WinsockFix. :: tried, didn't work

3. Winsock2 Fix. :: didn't try this one,
as description doesn;t match my situation

4. WinSock XP Fix. :: tried, didnt work

5. Remove registry entries and re-install tcp/ip
:: tried, didn;t work

6. run "netsh winsock reset catalog"
:: tried, didn't work

7. run "netsh int ip reset"
as described in http://support.microsoft.com/?id=299357
:: tried, didn;t work

I also followed "How to troubleshoot TCP/IP .."
http://support.microsoft.com/kb/314067/

I can
(1) ping 127.0.0.1 :: ok
(2) ping ip_of_local_host :: ok
(3) ping ip_of_gateway :: fails w time out
and ping from other machines also fail w time out

From above web page of MicroSoft, it says it is
"an issue with the network adapter, the router or
gateway device, the cabling, or other connectivity hardware"

However, exactly the same problem occurs whether I
use WiFi or ethernet.
Another pc can connect successfully to the same gateway
using the same piece of ethernet cable or WiFi with
same settings.
Click to expand...

What is this second computer? Can we use it to test consistently?

Right now, this sounds like a setting in the DL-614. Besides not being able to
ping it, what symptoms do you have?
 
Thanks again Chuck!

The second computer is a Dell Latitude D600.

I also have a home built desktop running WinXP SP2 connected
by ethernet to the same D-Link DL-614+.

The desktop of course doesn't have WiFi, but the network works
just fine with an ethernet cable.

I can connect the Dell using either WiFi or ethernet,
using either DHCP or fixed IP address :: everything is fine.

On the Averatec I tried WiFi as well as ethernet cable,
static IP or DHCP.
In all of these 4 cases, ipconfig reports valid and correct IP address,
I can ping 127.0.0.1 and the IP address from ipconfig.

However, in each of these 4 cases, ping to the gateway or any other
address fails , as well as ping to its IP address from either
of the other machines, all of these failures are timeouts.

All of these behaviour are very consistent.

Maybe I'll try a new gateway next.

Thanks.
ad_101
 
I tried a LinkSys WRT54G using ethernet cable and the problem is
exactly the same.

I have only two options left.

(a) Re-init the hard disk to factory settings
(b) send it out for "repair"

I'll try the (a) and will let you know.

Thanks
 
Final status: I reset the harddisk to factory settings from the set of CD
that came with the machine and now everything is fine.

Therefore, it was definitely some software issue.

In this case, none of the "software fixes" worked.

Thanks !
 
Back
Top