Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[kevinla]

Hello,

(DIR-655 with a D-Link DWA-142 USB adapter)

About every hour, web pages don't load, but the connection manager says I am connected at full strength. Is there some type of problem with my computer? What else could cause this? Do I need to run sort of tweak test?

IS

[JHK]

When you are not online, click on Start and then Run. Type in command or CMD, and then press Enter.

Type "ipconfig".  What is your IP Address?
Type "ping 192.168.0.1".  What is the response?
Type "ping yahoo.com".  What is the response?
Type "ping 216.109.112.135". What is the response?

[mr_nyx]

I just picked up a DWA-142 as well, and I'm also having connectivity problems.  I can be connected, but some time later, packets will not be passing through the interface anymore.  Therefore, pings of any kind will fail, including those from the router itself...

[JHK]

I just picked up a DWA-142 as well, and I'm also having connectivity problems.  I can be connected, but some time later, packets will not be passing through the interface anymore.  Therefore, pings of any kind will fail, including those from the router itself...

What was your IP address when the packets were not passing through? Did you ensure disabling all the software firewalls on the computers in the network?

[mr_nyx]

What was your IP address when the packets were not passing through? Did you ensure disabling all the software firewalls on the computers in the network?

The interface's IP address was a valid address (192.168.0.196), and I do not use any firewall except for the Windows XP Firewall, which still should allow pings in an outward direction (DWA-142 to the Internet).

However, I will attempt to disable the XP Firewall on that interface.  NAT from the router should be enough for a home-user (me).

[JHK]

The interface's IP address was a valid address (192.168.0.196)...

Then were you able to ping the gateway? How about the DNS address? After disabling the XP firewall, post the symptom so the future suggestion will not be redundant.

[mr_nyx]

Then were you able to ping the gateway? How about the DNS address? After disabling the XP firewall, post the symptom so the future suggestion will not be redundant.

No, I was unable to ping the gateway.  In fact, I supplied static IP addresses, including those for the gateway / DNS, without any positive effect.
Regardless of disabling the firewall, this issue continues.  I can be connected with a valid IP address, but after some time, packets are lost.
Issueing a traceroute fails to resolve any addresses.

If i had a wireless packet sniffer, I could try to determine if the packets are exiting the adapter at all... unfortunately, such equipment is only at work.

Note: I have a similar thread in the DWA-142 forums.

[JHK]

After some time, when you lose the packets, try pigging the 127.0.0.1 which is a loopback test.
c:/>ping 127.0.0.1 Or c:/>ping 127.0.0.1 -t
If everything is fine, you should get the following response or something similar:

Pinging 127.0.0.1 with 32 bytes of data

Reply from 127.0.0.1: bytes=32 time<10ms TTL=32
Reply from 127.0.0.1: bytes=32 time<10ms TTL=32
Reply from 127.0.0.1: bytes=32 time<10ms TTL=32
Reply from 127.0.0.1: bytes=32 time<10ms TTL=32

This means that TCP/IP is working on the machine that you are typing on.  127.0.0.1 is a special address that "loops back" to the machine you are pinging from. You can also type ping localhost and receive a similar response, since localhost and 127.0.0.1 mean the same thing. Also try telnet 127.0.0.1 mr_nyx. For example, if your system was named "mr_nyx", and you attempted to telnet to 127.0.0.1, you would see:

Trying 127.0.0.1...
Connected to mr_nyx

Ensure disabling the Local Area Network before you try the above steps. Please post the outcomes and other diagnostic tests which you have done so far.

[mr_nyx]

I'll give this a try if/when the connection fails again.
As a side-note (which is also in the DWA-142 forum), the newest beta drivers (1.20) seem to have stabilized my connectivity problems...
I need to test further to ensure that things are kosher.

After some time, when you lose the packets, try pigging the 127.0.0.1 which is a loopback test.
c:/>ping 127.0.0.1 Or c:/>ping 127.0.0.1 -t
If everything is fine, you should get the following response or something similar:

Pinging 127.0.0.1 with 32 bytes of data

Reply from 127.0.0.1: bytes=32 time<10ms TTL=32
Reply from 127.0.0.1: bytes=32 time<10ms TTL=32
Reply from 127.0.0.1: bytes=32 time<10ms TTL=32
Reply from 127.0.0.1: bytes=32 time<10ms TTL=32

This means that TCP/IP is working on the machine that you are typing on.  127.0.0.1 is a special address that "loops back" to the machine you are pinging from. You can also type ping localhost and receive a similar response, since localhost and 127.0.0.1 mean the same thing. Also try telnet 127.0.0.1 mr_nyx. For example, if your system was named "mr_nyx", and you attempted to telnet to 127.0.0.1, you would see:

Trying 127.0.0.1...
Connected to mr_nyx

Ensure disabling the Local Area Network before you try the above steps. Please post the outcomes and other diagnostic tests which you have done so far.

[kevinla]

When you are not online, click on Start and then Run. Type in command or CMD, and then press Enter.

Type "ipconfig".  What is your IP Address?
Type "ping 192.168.0.1".  What is the response?
Type "ping yahoo.com".  What is the response?
Type "ping 216.109.112.135". What is the response?

mpcshop:

I entered those in the command prompt.  Below are the results.


> Type "ipconfig".  What is your IP Address?

   IP Address. . . . . . . . . . . . : 192.168.0.194

> Type "ping 192.168.0.1".  What is the response?

Pinging 192.168.0.1 with 32 bytes of data:

Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.0.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

> Type "ping yahoo.com".  What is the response?

Pinging yahoo.com [216.109.112.135] with 32 bytes of data:

Reply from 216.109.112.135: bytes=32 time=100ms TTL=57
Reply from 216.109.112.135: bytes=32 time=101ms TTL=57
Reply from 216.109.112.135: bytes=32 time=99ms TTL=57
Reply from 216.109.112.135: bytes=32 time=102ms TTL=57

Ping statistics for 216.109.112.135:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 99ms, Maximum = 102ms, Average = 100ms

> Type "ping 216.109.112.135".
Pinging 216.109.112.135 with 32 bytes of data:

Reply from 216.109.112.135: bytes=32 time=104ms TTL=57
Reply from 216.109.112.135: bytes=32 time=101ms TTL=57
Reply from 216.109.112.135: bytes=32 time=101ms TTL=57
Reply from 216.109.112.135: bytes=32 time=104ms TTL=57

Ping statistics for 216.109.112.135:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 101ms, Maximum = 104ms, Average = 102ms

[AWDL]

Ping times are with in reason.

Are you experiencing browsing problems at the same time you have these relative ping times?

Do you have the same browsing experience with other browsers ( IE, Opera, Firefox, Netscape, Safari)?

If you refresh (ctrl +F5, in IE) does the page load completely. Give an example URL that doesn't load.

[kevinla]

The disconnect problems have pretty much stopped. 

There aren't any pages that don't load. They are just not as fast as I want them to be.  What is funny is, there is a laptop with an 802.11g card getting blazing speeds.   Faster than my computer and another computer hard wired to the router.   If I changed the 802.11 setting to "802.11 N" only, will I get better speeds with the USB adapter and still get connectivity with the 802.11g card?

The problem is with all browers.

I still can't stream video from some sites.  Although, YouTube is not a problem.

If it matters, I just remebered.  I was not able to get a connection hooked up directly with the modem. I had to hard wire to the router.  Not sure why.  I forgot to make the router and firewall pingable. I am not sure if I could get better results.

Kevin

[JHK]

Try the following then. c:>\ping www.yahoo.com -t (If your connection drops, it will display 'request timed out'. You can hold 'Ctrl' key and 'C' to exit out from the operation to view the results.) Then post the outcomes here.

And, open Internet Explorer and select Tools then the Internet Options.  Click on the Security tab and select Local Intranet. Click the Default level button (if available). Now select Internet and click the Default level button (if available).

Click on the Connections tab and make sure that "Never dial a connection" is selected.  Click the LAN Settings button, make sure that nothing is checked, then press OK.  Click the Advanced tab and click the Restore Defaults button (if available).  Click OK.

If you are running the proxy server, please disable it before you run the above diagnostic.

[kevinla]

If you are running the proxy server, please disable it before you run the above diagnostic.

How do I do this?  I do not know if I am running one or not.

KLA

[JHK]

To check for proxies, go to the Connection tab from the Internet Options, and uncheck everything in the LAN Settings then press OK.