Welcome Guest ( Log In | Click here to Register a free account now! )
Welcome to Bleeping Computer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.![]() ![]() |
Oct 14 2008, 04:53 AM
Post
#1
|
|
|
New Member ![]() Group: Members Posts: 3 Joined: 14-October 08 Member No.: 246,363 |
I have very little time before my connection will drop out again, and I have no idea why! I'm running Windows XP, sp3. When the connection drops, MSN will stay connected (I can still chat to people etc), and I can download an update through ad-aware, but after about 10 - 15 mins, my browser (Firefox, then I also try IE) will not connect to anything. I did a network diagnostic, and some of the tests passed, some failed: Please let me know if you or anyone can help!!! Or if you need more info... Maybe something to do with DNS? I have no idea how I can be connected one minute, and not connected the next... Please help! - Network Adapters FAILED - [00000011] Realtek RTL8168/8111 PCI-E Gigabit Ethernet NIC (FAILED) Caption = [00000011] Realtek RTL8168/8111 PCI-E Gigabit Ethernet NIC DatabasePath = %SystemRoot%\System32\drivers\etc + DefaultIPGateway = 192.168.1.1(Same Subnet) (PASSED) Pinging 192.168.1.1 with 32 bytes of data: Reply from 192.168.1.1: bytes=32 time=1ms TTL=1 Reply from 192.168.1.1: bytes=32 time=1ms TTL=1 Reply from 192.168.1.1: bytes=32 time=1ms TTL=1 Reply from 192.168.1.1: bytes=32 time=1ms TTL=1 Ping statistics for 192.168.1.1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss) Approximate round trip times in milli-seconds: Minimum = 1ms, Maximum = 1ms, Average = 1ms Description = Realtek RTL8168/8111 PCI-E Gigabit Ethernet NIC - Packet Scheduler Miniport DHCPEnabled = TRUE DHCPLeaseExpires = 7:36:41 PM 15/10/2008 DHCPLeaseObtained = 7:36:41 PM 14/10/2008 + DHCPServer = 192.168.1.1 (PASSED) Pinging 192.168.1.1 with 32 bytes of data: Reply from 192.168.1.1: bytes=32 time=1ms TTL=1 Reply from 192.168.1.1: bytes=32 time=1ms TTL=1 Reply from 192.168.1.1: bytes=32 time=1ms TTL=1 Reply from 192.168.1.1: bytes=32 time=1ms TTL=1 Ping statistics for 192.168.1.1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss) Approximate round trip times in milli-seconds: Minimum = 1ms, Maximum = 1ms, Average = 1ms DNSDomain = vic.bigpond.net.au DNSEnabledForWINSResolution = FALSE DNSHostName = xciled - DNSServerSearchOrder (FAILED) - 61.9.134.49 (FAILED) Pinging 61.9.134.49 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 61.9.134.49: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss) - 61.9.133.193 (FAILED) Pinging 61.9.133.193 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 61.9.133.193: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss) DomainDNSRegistrationEnabled = FALSE FullDNSRegistrationEnabled = TRUE GatewayCostMetric = 20 Index = 11 + IPAddress = 192.168.1.101 (PASSED) Pinging 192.168.1.101 with 32 bytes of data: Reply from 192.168.1.101: bytes=32 time<1ms TTL=0 Reply from 192.168.1.101: bytes=32 time<1ms TTL=0 Reply from 192.168.1.101: bytes=32 time<1ms TTL=0 Reply from 192.168.1.101: bytes=32 time<1ms TTL=0 Ping statistics for 192.168.1.101: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss) Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms IPConnectionMetric = 20 IPEnabled = TRUE IPFilterSecurityEnabled = FALSE IPSecPermitIPProtocols = 0 IPSecPermitTCPPorts = 0 IPSecPermitUDPPorts = 0 IPSubnet = 255.255.255.0 IPXEnabled = FALSE MACAddress = 00:1A:4D:5C:EF:8A ServiceName = RTLE8023xp SettingID = {F1FBEBBB-133B-4B9A-9C49-0A0F279FD3A3} TcpipNetbiosOptions = 0 WINSEnableLMHostsLookup = TRUE + [00000014] Bluetooth Device (Personal Area Network) Caption = [00000014] Bluetooth Device (Personal Area Network) DatabasePath = %SystemRoot%\System32\drivers\etc Description = Bluetooth Device (Personal Area Network) DHCPEnabled = TRUE DNSEnabledForWINSResolution = FALSE DNSHostName = xciled DomainDNSRegistrationEnabled = FALSE FullDNSRegistrationEnabled = TRUE Index = 14 IPConnectionMetric = 1 IPEnabled = TRUE IPFilterSecurityEnabled = FALSE IPSecPermitIPProtocols = 0 IPSecPermitTCPPorts = 0 IPSecPermitUDPPorts = 0 IPXEnabled = FALSE MACAddress = 00:0B:0D:0E:22:7C ServiceName = BthPan SettingID = {9D39CCE4-A5FF-41D0-8976-AC4DE0838DCD} TcpipNetbiosOptions = 0 WINSEnableLMHostsLookup = TRUE - DNS Servers FAILED - [00000011] Realtek RTL8168/8111 PCI-E Gigabit Ethernet NIC (FAILED) - DNSServerSearchOrder (FAILED) - 61.9.134.49 (FAILED) Pinging 61.9.134.49 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 61.9.134.49: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss) - 61.9.133.193 (FAILED) Pinging 61.9.133.193 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 61.9.133.193: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss) + Default Gateways PASSED + [00000011] Realtek RTL8168/8111 PCI-E Gigabit Ethernet NIC (PASSED) + DefaultIPGateway = 192.168.1.1(Same Subnet) (PASSED) Pinging 192.168.1.1 with 32 bytes of data: Reply from 192.168.1.1: bytes=32 time=1ms TTL=1 Reply from 192.168.1.1: bytes=32 time=1ms TTL=1 Reply from 192.168.1.1: bytes=32 time=1ms TTL=1 Reply from 192.168.1.1: bytes=32 time=1ms TTL=1 Ping statistics for 192.168.1.1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss) Approximate round trip times in milli-seconds: Minimum = 1ms, Maximum = 1ms, Average = 1ms + DHCP Servers PASSED + [00000011] Realtek RTL8168/8111 PCI-E Gigabit Ethernet NIC (PASSED) + DHCPServer = 192.168.1.1 (PASSED) Pinging 192.168.1.1 with 32 bytes of data: Reply from 192.168.1.1: bytes=32 time=1ms TTL=1 Reply from 192.168.1.1: bytes=32 time=1ms TTL=1 Reply from 192.168.1.1: bytes=32 time=1ms TTL=1 Reply from 192.168.1.1: bytes=32 time=1ms TTL=1 Ping statistics for 192.168.1.1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss) Approximate round trip times in milli-seconds: Minimum = 1ms, Maximum = 1ms, Average = 1ms + IP Address PASSED + [00000011] Realtek RTL8168/8111 PCI-E Gigabit Ethernet NIC (PASSED) + IPAddress = 192.168.1.101 (PASSED) Pinging 192.168.1.101 with 32 bytes of data: Reply from 192.168.1.101: bytes=32 time<1ms TTL=0 Reply from 192.168.1.101: bytes=32 time<1ms TTL=0 Reply from 192.168.1.101: bytes=32 time<1ms TTL=0 Reply from 192.168.1.101: bytes=32 time<1ms TTL=0 Ping statistics for 192.168.1.101: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss) Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms WINS Servers + Network Clients |
|
|
|
Oct 14 2008, 05:05 AM
Post
#2
|
|
|
New Member ![]() Group: Members Posts: 3 Joined: 14-October 08 Member No.: 246,363 |
Also, I am not sure if it's worth mentioning... But Zone Alarm doesn't show up in the system tray.
It's definitely running under processes in the task manager, but not showing in the system tray. |
|
|
|
Oct 14 2008, 07:01 AM
Post
#3
|
|
![]() Still visually handicapped, new avatar (a camel) :0) ![]() ![]() ![]() ![]() ![]() ![]() Group: BC Advisor Posts: 16,689 Joined: 2-October 05 From: Southeastern CT, USA Member No.: 35,824 |
I'd suggest uninstalling ZoneAlarm to see if that helps the problem. But first download a new copy so that you can install it when you're done.
If that doesn't fix it, then there's a lot of other stuff to try. I'll move this over to the networking forum if you post back that the ZoneAlarm removal didn't fix it. -------------------- - John
**If you need a more detailed explanation, please ask for it. I have the Knack. ** |
|
|
|
Oct 14 2008, 08:51 AM
Post
#4
|
|
|
New Member ![]() Group: Members Posts: 3 Joined: 14-October 08 Member No.: 246,363 |
Well as soon as I uninstalled Zone Alarm and tried to load a web page, it worked!
I was going through the problem with a friend, and he also believed it to be something to do with the DNS. Trace route would go 2 hops, then time out. I could still ping most websites, but when I tried telnet google.com 80, it timed out. It's now almost 1am on a work night, and I'm screwed tomorrow! Thanks usasma. |
|
|
|
Oct 14 2008, 09:53 AM
Post
#5
|
|
![]() Still visually handicapped, new avatar (a camel) :0) ![]() ![]() ![]() ![]() ![]() ![]() Group: BC Advisor Posts: 16,689 Joined: 2-October 05 From: Southeastern CT, USA Member No.: 35,824 |
I had first thought about all those things that you'd mentioned - and even composed a lengthy post with a lot of suggestions.
Then, because of my eye problems, I reread your post and noted that: 1 - you could connect on different ports (other than port 80 for your browser), and 2 - you mentioned a "glitch" with ZoneAlarm -------------------- - John
**If you need a more detailed explanation, please ask for it. I have the Knack. ** |
|
|
|
![]() ![]() |
| Lo-Fi Version | Time is now: 21st November 2009 - 11:20 PM |