[SOLVED] Help! Internet Keeps Timing out

[ctxman]

Hello, I hope someone can help. For the last couple weeks our home PC which is running on 2000 has had internet connection problems. Nothing else with the computer seems to be a problem, but when we access the internet, it is VERY slow. It happens in Firefox and Netscape. We can open up a website (slowly), but when we click on a link to anything else after the first site we get a timeout error. I tried to do a DSL Report from their website but it keeps timing out before I can get the report. We also have a router and I am running my laptop via wireless and it is not affected and operates normally. It is just the home PC. Any ideas? I can't navigate much on the pc to do any reports. I tried Speed Test and it hung up as well. We can't get to our email thru Verizon or anything. Since our wireless is working fine it has to be some setting that got changed on the PC?

Thanks

[johnwill]

Please supply the following info, exact make and models of the equipment please.

Make and model of the broadband modem.
Make and model of the router.
Connection type, wired or wireless.
If wireless, encryption used, (none, WEP, WPA, or WPA2)
Make/model of your computer.
Version and patch level of Windows on all affected machines, i.e. XP-Home (or XP-Pro), SP2, Vista, etc.

Also, please give an exact description of your problem symptoms, including the exact text of any error messages.




On any problem computer, I'd also like to see this:

Start, Run, CMD to open a command prompt:

Type the following command:

IPCONFIG /ALL

Right click in the command window and choose Select All, then hit Enter.
Paste the results in a message here.

If you are on a machine with no network connection, use a floppy, USB disk, or a CD-RW disk to transfer a text file with the information to allow pasting it here.

[ctxman]

Thanks John!

The PC is a "Shuttle X" with Windows 2000 operating system. The Modem is a Toshiba WRC-1000, model # PA3227U-1ETC. The Router is a Westell Model A90-327W15-06 Rev E. The connection on this PC is Wired.

Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.

C:\>ipconfig/all

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : desktop1
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : myhome.westell.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : myhome.westell.com
Description . . . . . . . . . . . : Realtek RTL8139/810X Family PCI Fast
Ethernet NIC
Physical Address. . . . . . . . . : 00-30-1B-2B-48-1C
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.10.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.10.1
DHCP Server . . . . . . . . . . . : 192.168.10.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
192.168.1.1
Lease Obtained. . . . . . . . . . : Sunday, December 16, 2007 12:33:15 P
M
Lease Expires . . . . . . . . . . : Wednesday, December 19, 2007 12:33:1
5 PM

C:\>

It is agonizingly slow. It took several attempts just to get this posted. I was able to open up the Tech Support Forum, but when I click on the link for "Networking Support", I get a "Time Out" message on the browser. The screen is white and says that it took too long for the Tech support website and it times out. It does this all the time on anything I try to open. It will be a miracle if this post even goes through.

[petronius]

ctxman,

I'm curious about your DNS ip address 192.168.1.1 not being the same as the device issuing it (DHCP server 192.168.1.10). I wonder if you have a different DNS server being issued for your wireless connection.

Please do this from BOTH systems:

Start, Run, CMD to open a command prompt:

Type the following command:

nslookup

At the prompt type: www.techsupportforum.com (hit enter)

type: exit (hit enter)

Right click in the command window and choose Select All, then hit Enter.
Paste the results in a message here.

Also, please paste the "/ipconfig all" results from the laptop as well.

Thanks

[ctxman]

Petronius,

Our system has been set up like this for a long time. My wife thinks she remembers that when they had the same number there was a conflict because one routes through the other. The router and modem are in series. It's been like this since the beginning.

A couple weeks ago my wife went to the computer and there was some kind of message from AIM (kids have it). IT was a Welcome screen. My wife thought that it had done some kind of automatic update but we aren't really sure. That same day all of our home email was missing and somehow my wife searched and found it, but she thinks that all this is somehow related.

Here are the results from the laptop. It might take several minutes to get the same from the Desktop because it will want to time out. I'll keep trying until I get it posted.

Laptop:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\jdguerra>nslookup
Default Server: dslrouter
Address: 192.168.1.1

> www.techsupportforum.com
Server: dslrouter
Address: 192.168.1.1

Non-authoritative answer:
Name: www.techsupportforum.com.swna.wdpr.disney.com
Addresses: 63.251.179.13, 8.15.7.117

>
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\jdguerra>ipconfig/all

Windows IP Configuration

Host Name . . . . . . . . . . . . : CALA-AM00355352
Primary Dns Suffix . . . . . . . : swna.wdpr.disney.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : swna.wdpr.disney.com
wdpr.disney.com
crp.disney.com
disney.com
abc.com

Ethernet adapter Wireless Network Connection 2:

Connection-specific DNS Suffix . : myhome.westell.com
Description . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG Networ
k Connection
Physical Address. . . . . . . . . : 00-18-DE-65-F7-FE
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.46
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
192.168.1.1
Lease Obtained. . . . . . . . . . : 2007-12-16 08:34
Lease Expires . . . . . . . . . . : 2007-12-17 08:34

Ethernet adapter Local Area Connection 3:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Intel(R) PRO/1000 PL Network Connect
ion
Physical Address. . . . . . . . . : 00-16-41-AC-0B-8C

Ethernet adapter Bluetooth Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Bluetooth Device (Personal Area Netw
ork)
Physical Address. . . . . . . . . : 00-16-CF-DD-D2-99

C:\Documents and Settings\jdguerra>

[ctxman]

and from the PC:

Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.

C:\>ntlookup
'ntlookup' is not recognized as an internal or external command,
operable program or batch file.

C:\>nslookup
DNS request timed out.
timeout was 2 seconds.
*** Can't find server name for address 192.168.1.1: Timed out
*** Default servers are not available
Default Server: UnKnown
Address: 192.168.1.1

> www.techsupportforum.com
Server: UnKnown
Address: 192.168.1.1

DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out
>

Also our yahoo IM closes down and used to stay open until we shut it down, so I assume it loses it's connection too.

[petronius]

ctxman,

Ok well I see your problem and I wanted you to do the nslookup just to see if your dns requests were being forwarded somehow.

On the windows 2000 PC you'll notice that your IP address is 192.168.10.100 with a /24 netmask (255.255.255.0). That means your network number is 192.168.10.0. Here is the problem, the dns server address being issued to you is 192.168.1.1 with a /24 netmask...making it's network number 192.168.1.0.

What this boils down to is your DNS server is not on the same network as your PC and they can't talk to each other. More than likely your router is forwarding that traffic upstream and it is taking forever for it to come back with a reply from an upstream DNS server.

Solution: you need to get your PC on the same network as your laptop is using or you need to use a different DNS server for the PC. It looks the like the westell is acting as the DHCP server for both the laptop and the PC but they are on different networks so that makes no sense.

In practical terms...whatever is acting as the DHCP server for the PC needs to issue the PC a working DNS server that is on the 192.168.10.0 network or you need to get that PC on the 192.168.1.0 network (the one the laptop is using) somehow.

It is possible the westell is a DHCP server and the Toshiba modem is also functioning as a DHCP server. I am curious about the configuration of that Toshiba now. You might be routing through it.

Please reply with *detail* about how everything is connected....from the DSL jack all the way through to the PC. That means the dsl modem, the westell, any switches/hubs and the PC. Please explain to me how they are all *physically* interconnected; please include all the cables etc.

TTY soon...

[johnwill]

You have two routers, the Toshiba and the Westell. I suspect since the Westell is connected directly to the DSL account, and the Toshiba is only an 802.11b wireless device, you should lose it. Also, you may need a plain Ethernet switch to expand the wired connection from the Westell if desired. Optionally, you could configure the Toshiba router as a plain switch with the following configuration.

Connecting two SOHO broadband routers together.

Configure the IP address of the secondary router to be in the same subnet as the primary router, but out of the range of the DHCP server in the primary router. For instance DHCP server addresses 192.168.0.2 through 192.168.0.100, I'd assign the secondary router 192.168.0.254 as it's IP address.

Note: Do this first, as you will have to reboot the computer to connect to the router again for the remaining changes.

Disable the DHCP server in the secondary router.

Setup the wireless section just the way you would if it was the primary router, channels, encryption, etc.

Connect from the primary router's LAN port to one of the LAN ports on the secondary router. If there is no uplink port and neither of the routers have auto-sensing ports, use a cross-over cable. Leave the WAN port unconnected!

This procedure bypasses the routing function (NAT layer) and configures the router as a switch (or wireless access point for wireless routers).

[petronius]

He stated in post #3 that his modem is the Toshiba. We need to find out which device is actually the dsl modem since obviously he only needs one.

[johnwill]

petronius, if you look up the model of the Toshiba posted, you'll see it's a plain router and not a modem. Try reading my reply again armed with this new knowledge.

[petronius]

johnwill, it's as you said.

The westell is also wireless:

http://www.westell.com/images/extran...alink_7500.pdf

He can probably just turn off the toshiba and connect through the westell just fine if the PC is close enough. Regardless, his DNS server is not on the same network as the PC and that is why NR is failing.

[johnwill]

I didn't realize it included four wired ports, so it's even simpler than I said. I should have looked closer when I looked that model up.

It's unanimous, lose the Toshiba router!

[ctxman]

Petronius and Johnwill,

Sorry for the late response. We figured out the problem. First off, let me state that we've had this same setup for a long time and no wiring has changed, so it was odd that things stopped working like this. The reason for both routers is because the Westell unit which is provided by our provider never worked for networking our computers. It was supposed to work so we could network them up but after several phone calls with our provider and No success, we ended up buying a second router to get network printing to work.

This morning we disconnected the Toshiba and connected directly to the Westell and everything worked as normal! So, in a way you were correct to delete the Toshiba. And, as it turns out, we managed to get the other 2 laptops to be able to print to the network printer as well. So, we're back up to speed, can print to our printer from all computers, and trashed the Toshiba.

I still don't know why it stopped working, if it just went bad on us or somehow a setting got changed, but at any rate the problem is solved.

Thanks to both of you for your quick response and efforts to help us out, it is much appreciated.

John

[johnwill]

Thanks for the feedback. Glad it was resolved.

[petronius]

ditto