Quote:
|
Originally Posted by BLKDOG40 Not a networking pro or anything but heres some ideas-
Are there firmware updates for the router? |
Not any new ones. I have downloaded all the previous ones, but there haven't been any for months.
Quote:
|
Originally Posted by BLKDOG40 Possible IP address conflicts- you using dhcp or static IP addresses? |
Not using static IP addresses.
Quote:
|
Originally Posted by BLKDOG40 You sure its the router and not your internet connection- can you ping your router? hit start-run-command- type ping 192.168.1.1 (that is a typical default address, yours may be different) |
No, not sure. Here in a second, I'll go direct to the modem, but then I can't work and surf mud simultaneously...

. Here's what I get when I ping. Sometimes it works good. Next minute, it will tell me a network cable is unplugged, and give me the "request timed out" error. This makes me think router? This is on my desktop which is a cable connection to the router, so no wireless issues involved. On my laptop with wireless, the signal strength will periodically oscillate between good and poor about every second or so.
C:\DOCUME~1\EMILY>ping 192.168.0.1
Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time=7ms 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 = 7ms, Average = 2ms
C:\DOCUME~1\EMILY>ping 192.168.0.1
Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time=13ms TTL=64
Reply from 192.168.0.1: bytes=32 time=13ms 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 = 1ms, Maximum = 13ms, Average = 7ms
C:\DOCUME~1\EMILY>ping 192.168.0.1
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 = 1ms, Maximum = 1ms, Average = 1ms
C:\DOCUME~1\EMILY>ping 192.168.0.1
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 = 1ms, Average = 0ms
C:\DOCUME~1\EMILY>ping 192.168.0.1
Pinging 192.168.0.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\DOCUME~1\EMILY>