Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, 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.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Extremely odd network problem, I'm stumped.


  • Please log in to reply
21 replies to this topic

#1 EdwardHowton

EdwardHowton

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:04:37 AM

Posted 26 April 2014 - 12:19 PM

A few days ago my internet connection suddenly began getting extremely slow. Over-20-minutes-to-register-an-account-and-so-slow-the-captcha-picture-wouldn't-load slow. I don't know how else to explain the problem other than with traceroute. A very successful trace today:

 

 

Tracing route to bleepingcomputer.com [141.101.123.117]
over a maximum of 30 hops:

1     *          *         *     Request timed out.
2 10 ms 11 ms 12 ms x.x.x.x
3     *     20 ms  19 ms x.x.x.x
4 22 ms 23 ms     *      x.x.x.x
5 20 ms 20 ms 19 ms x.x.x.x
6     *     19 ms  26 ms x.x.x.x
7     *     15 ms  15 ms 141.101.123.117

Trace complete.

 

I say successful because the traces are actually completing. For others, this is what's happening:

 

 

Tracing route to videotron.com [24.201.243.21]
over a maximum of 30 hops:

1 * * * Request timed out.
2 11 ms 11 ms 11 ms x.x.x.x
3 16 ms 11 ms 15 ms x.x.x.x
4 8 ms 8 ms 8 ms x.x.x.x
5 13 ms 7 ms 7 ms x.x.x.x
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * *

 

and so on and so forth, all the way to 30. I'm not going to paste the whole thing because it takes forever for it to finish, but you get the idea.

 

Even more oddly, if I try to trace to the second IP address, the first non-local bounce, then the entire thing times out.

 

Contacted my ISP, they couldn't query my modem remotely, and sent some techs. Techs replaced much of the installation outside, changing plugs and connectors, then ran a cable from the box directly to my modem, same issues. Replaced modem, same issues, but my ISP could see my modem on their network. Typical, though, my connection was okay while the techs were here and the whole day before they arrived. Then it went to bleep again.

 

Uninstalled/reinstalled the network adapter, ran antivirus and malware scans unsuccessfully (AVG and Ad-Aware, neither of which seem to be any good, but I can't download anything much at the moment), and now the entire internet is at a trickle.

 

What makes no sense to me is that the first bounce times out. It seems to me that that should not be possible, and the only explanation I can come up with is that all of a sudden my computer is trying to route my connection through a router that I don't have.

 

ConnectionAnalyzer.com when I tried it showed a mass of red warning results, but I don't know how useful that is and don't understand most of it anyway.

 

I'm completely stumped, and I've tried everything else I can think of. Rolling the dice here twice: once for help, but most annoyingly once to see if I'll be able to post this question. Here goes nothing.


Edited by hamluis, 26 April 2014 - 04:17 PM.
Moved from Win 7 to Networking - Hamluis.


BC AdBot (Login to Remove)

 


#2 CaveDweller2

CaveDweller2

  • Members
  • 2,629 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:04:37 AM

Posted 27 April 2014 - 03:28 PM

Run MiniToolBox  and check the first 8 boxes from "flush DNS" to list "Winsock Entries" then click GO. Notepad will open click Edit, then Select All, then Copy, and then paste it in your reply.

 

Also the request timed out on a tracert just means the router is not set to reply to pings. If it weren't actually getting forwarded, it would just stop there and there would be no next hop.


Hope this helps thumbup.gif

Associate in Applied Science - Network Systems Management - Trident Technical College


#3 EdwardHowton

EdwardHowton
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:04:37 AM

Posted 27 April 2014 - 05:28 PM

The weird thing about tracert is that it used to work just fine, every bounce showing. Anyhow:

 

MiniToolBox by Farbar Version: 23-01-2014
Ran by User (administrator) on 27-04-2014 at 18:26:00
Running from "C:\Users\User\AppData\Local\Opera\Opera\temporary_downloads"
Microsoft Windows 7 Home Premium Service Pack 1 (X64)
Boot Mode: Normal
***************************************************************************

========================= Flush DNS: ===================================

Windows IP Configuration

Successfully flushed the DNS Resolver Cache.

========================= IE Proxy Settings: ==============================

Proxy is not enabled.
No Proxy Server is set.

"Reset IE Proxy Settings": IE Proxy Settings were reset.
========================= Hosts content: =================================



========================= IP Configuration: ================================

Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller = Local Area Connection (Connected)


# ----------------------------------
# IPv4 Configuration
# ----------------------------------
pushd interface ipv4

reset
set global icmpredirects=enabled
add route prefix=0.0.0.0/0 interface="ethernet_9" nexthop=5.0.0.1 publish=Yes
add route prefix=0.0.0.0/0 interface="Local Area Connection-WFP LightWeight Filter-0000" nexthop=25.0.0.1 publish=Yes
set interface interface="ethernet_9" forwarding=disabled advertise=disabled metric=1 siteprefixlength=0 nud=disabled routerdiscovery=disabled managedaddress=disabled otherstateful=disabled weakhostsend=disabled weakhostreceive=disabled ignoredefaultroutes=disabled advertisedrouterlifetime=0 advertisedefaultroute=disabled currenthoplimit=0 forcearpndwolpattern=disabled enabledirectedmacwolpattern=disabled
set interface interface="Local Area Connection-WFP LightWeight Filter-0000" forwarding=disabled advertise=disabled metric=9000 siteprefixlength=0 nud=disabled routerdiscovery=disabled managedaddress=disabled otherstateful=disabled weakhostsend=disabled weakhostreceive=disabled ignoredefaultroutes=disabled advertisedrouterlifetime=0 advertisedefaultroute=disabled currenthoplimit=0 forcearpndwolpattern=disabled enabledirectedmacwolpattern=disabled


popd
# End of IPv4 configuration



Windows IP Configuration

Host Name . . . . . . . . . . . . : User-PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller
Physical Address. . . . . . . . . : F4-6D-04-25-69-36
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::858e:a54d:7dc9:405%15(Preferred)
IPv4 Address. . . . . . . . . . . : 24.203.12.141(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : April-26-14 4:58:31 AM
Lease Expires . . . . . . . . . . : April-28-14 4:13:38 PM
Default Gateway . . . . . . . . . : 24.203.12.1
DHCP Server . . . . . . . . . . . : 10.23.113.4
DHCPv6 IAID . . . . . . . . . . . : 318008580
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-15-91-D7-58-F4-6D-04-25-69-36
DNS Servers . . . . . . . . . . . : 24.200.241.37
24.202.72.13
24.200.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{16C6C97C-6C23-4C98-A948-D0CB9886BD2B}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:9d38:6abd:41f:136a:e734:f372(Preferred)
Link-local IPv6 Address . . . . . : fe80::41f:136a:e734:f372%11(Preferred)
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter 6TO4 Adapter:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2002:18cb:c8d::18cb:c8d(Preferred)
Default Gateway . . . . . . . . . : 2002:c058:6301::c058:6301
DNS Servers . . . . . . . . . . . : 24.200.241.37
24.202.72.13
24.200.0.1
NetBIOS over Tcpip. . . . . . . . : Disabled
Server: dns1.videotron.ca
Address: 24.200.241.37

Name: google.com
Addresses: 2607:f8b0:4006:809::1002
74.125.226.164
74.125.226.165
74.125.226.163
74.125.226.160
74.125.226.166
74.125.226.174
74.125.226.161
74.125.226.168
74.125.226.169
74.125.226.162
74.125.226.167


Pinging google.com [74.125.226.231] with 32 bytes of data:
Reply from 74.125.226.231: bytes=32 time=38ms TTL=52
Reply from 74.125.226.231: bytes=32 time=34ms TTL=52

Ping statistics for 74.125.226.231:
Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 34ms, Maximum = 38ms, Average = 36ms
Server: dns1.videotron.ca
Address: 24.200.241.37

Name: yahoo.com
Addresses: 98.139.183.24
98.138.253.109
206.190.36.45


Pinging yahoo.com [206.190.36.45] with 32 bytes of data:
Reply from 206.190.36.45: bytes=32 time=94ms TTL=54
Reply from 206.190.36.45: bytes=32 time=88ms TTL=54

Ping statistics for 206.190.36.45:
Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 88ms, Maximum = 94ms, Average = 91ms

Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Ping statistics for 127.0.0.1:
Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
===========================================================================
Interface List
15...f4 6d 04 25 69 36 ......Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller
1...........................Software Loopback Interface 1
10...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
11...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
12...00 00 00 00 00 00 00 e0 Microsoft 6to4 Adapter
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 24.203.12.1 24.203.12.141 10
24.203.12.0 255.255.255.0 On-link 24.203.12.141 266
24.203.12.141 255.255.255.255 On-link 24.203.12.141 266
24.203.12.255 255.255.255.255 On-link 24.203.12.141 266
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 24.203.12.141 266
255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
255.255.255.255 255.255.255.255 On-link 24.203.12.141 266
===========================================================================
Persistent Routes:
Network Address Netmask Gateway Address Metric
0.0.0.0 0.0.0.0 5.0.0.1 Default
0.0.0.0 0.0.0.0 25.0.0.1 Default
===========================================================================

IPv6 Route Table
===========================================================================
Active Routes:
If Metric Network Destination Gateway
12 1110 ::/0 2002:c058:6301::c058:6301
1 306 ::1/128 On-link
11 58 2001::/32 On-link
11 306 2001:0:9d38:6abd:41f:136a:e734:f372/128
On-link
12 1010 2002::/16 On-link
12 266 2002:18cb:c8d::18cb:c8d/128
On-link
15 266 fe80::/64 On-link
11 306 fe80::/64 On-link
11 306 fe80::41f:136a:e734:f372/128
On-link
15 266 fe80::858e:a54d:7dc9:405/128
On-link
1 306 ff00::/8 On-link
11 306 ff00::/8 On-link
15 266 ff00::/8 On-link
===========================================================================
Persistent Routes:
If Metric Network Destination Gateway
0 4294967295 2620:9b::/96 On-link
0 4294967295 2620:9b::/96 On-link
0 9000 ::/0 2620:9b::1900:1
===========================================================================
========================= Winsock entries =====================================

Catalog5 01 C:\Windows\SysWOW64\NLAapi.dll [52224] (Microsoft Corporation)
Catalog5 02 C:\Windows\SysWOW64\napinsp.dll [52224] (Microsoft Corporation)
Catalog5 03 C:\Windows\SysWOW64\pnrpnsp.dll [65024] (Microsoft Corporation)
Catalog5 04 C:\Windows\SysWOW64\pnrpnsp.dll [65024] (Microsoft Corporation)
Catalog5 05 C:\Windows\SysWOW64\mswsock.dll [232448] (Microsoft Corporation)
Catalog5 06 C:\Windows\SysWOW64\winrnr.dll [20992] (Microsoft Corporation)
Catalog5 07 C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live\WLIDNSP.DLL [134528] (Microsoft Corporation)
Catalog5 08 C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live\WLIDNSP.DLL [134528] (Microsoft Corporation)
Catalog9 01 C:\Windows\SysWOW64\mswsock.dll [232448] (Microsoft Corporation)
Catalog9 02 C:\Windows\SysWOW64\mswsock.dll [232448] (Microsoft Corporation)
Catalog9 03 C:\Windows\SysWOW64\mswsock.dll [232448] (Microsoft Corporation)
Catalog9 04 C:\Windows\SysWOW64\mswsock.dll [232448] (Microsoft Corporation)
Catalog9 05 C:\Windows\SysWOW64\mswsock.dll [232448] (Microsoft Corporation)
Catalog9 06 C:\Windows\SysWOW64\mswsock.dll [232448] (Microsoft Corporation)
Catalog9 07 C:\Windows\SysWOW64\mswsock.dll [232448] (Microsoft Corporation)
Catalog9 08 C:\Windows\SysWOW64\mswsock.dll [232448] (Microsoft Corporation)
Catalog9 09 C:\Windows\SysWOW64\mswsock.dll [232448] (Microsoft Corporation)
Catalog9 10 C:\Windows\SysWOW64\mswsock.dll [232448] (Microsoft Corporation)
x64-Catalog5 01 C:\Windows\System32\NLAapi.dll [70656] (Microsoft Corporation)
x64-Catalog5 02 C:\Windows\System32\napinsp.dll [68096] (Microsoft Corporation)
x64-Catalog5 03 C:\Windows\System32\pnrpnsp.dll [86016] (Microsoft Corporation)
x64-Catalog5 04 C:\Windows\System32\pnrpnsp.dll [86016] (Microsoft Corporation)
x64-Catalog5 05 C:\Windows\System32\mswsock.dll [326144] (Microsoft Corporation)
x64-Catalog5 06 C:\Windows\System32\winrnr.dll [28672] (Microsoft Corporation)
x64-Catalog5 07 C:\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDNSP.DLL [168304] (Microsoft Corporation)
x64-Catalog5 08 C:\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDNSP.DLL [168304] (Microsoft Corporation)
x64-Catalog9 01 C:\Windows\System32\mswsock.dll [326144] (Microsoft Corporation)
x64-Catalog9 02 C:\Windows\System32\mswsock.dll [326144] (Microsoft Corporation)
x64-Catalog9 03 C:\Windows\System32\mswsock.dll [326144] (Microsoft Corporation)
x64-Catalog9 04 C:\Windows\System32\mswsock.dll [326144] (Microsoft Corporation)
x64-Catalog9 05 C:\Windows\System32\mswsock.dll [326144] (Microsoft Corporation)
x64-Catalog9 06 C:\Windows\System32\mswsock.dll [326144] (Microsoft Corporation)
x64-Catalog9 07 C:\Windows\System32\mswsock.dll [326144] (Microsoft Corporation)
x64-Catalog9 08 C:\Windows\System32\mswsock.dll [326144] (Microsoft Corporation)
x64-Catalog9 09 C:\Windows\System32\mswsock.dll [326144] (Microsoft Corporation)
x64-Catalog9 10 C:\Windows\System32\mswsock.dll [326144] (Microsoft Corporation)

**** End of log ****



#4 technonymous

technonymous

  • Members
  • 2,499 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:01:37 AM

Posted 27 April 2014 - 08:09 PM

Maybe mods ought to post something about this. If your ISP is Comcast they recently had a fiber line cut in Washington State the thieves was expecting to steal copper. Google search results sometimes freezes and streaming is choppy or will freeze due to packet losses.



#5 EdwardHowton

EdwardHowton
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:04:37 AM

Posted 27 April 2014 - 08:29 PM

I'm nowhere near Washington, I don't use Comcast, and Videotron is a local company so it wouldn't make sense for bounces to go from Montreal to Washington back to Montreal for an ISP that is basically a gigantic LAN.

Tracert is the very first thing I use when my connection starts crapping out, precisely because of the possibility of cut lines as you mentioned. What worried me this time is the consistent timing out locally and for bounces 6 onwards. Makes no sense to me at all.



#6 czarboom

czarboom

  • Members
  • 608 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Central Texas
  • Local time:03:37 AM

Posted 28 April 2014 - 02:17 AM

Try in CMD as admin, running  ipconfig release the renew.

Flush the DNS cache and I noticed in the DNS table your DNS are all over, they should be tighter

 

 

Default Gateway . . . . . . . . . : 24.203.12.1
DHCP Server . . . . . . . . . . . : 10.23.113.4

These need to be the same or your DHCP should not be a private IP while your gateway is a public one.  So using a fake example

IP addy 192.168.1.10

Default Gateway 192.168.1.1

DHCP Server 192.168.1.1

DNS 192.168.1.100

         24.203.x.xxx

 

This is with a router set up.  But even direct there should be tighter.  Try going into your adapter and set everything to auto.  Also did you try to echo and not ping.  Echo should work if ping is, but I have had that happen before. 

Last, if you know what your doing go start and type hosts and hit enter. 

This is your look up table, make sure that and ipconfig /all are matching up.  If not change your IPs if Fixed or reset your Hosts file to configure for DHCP


CZARBOOM 
 
"Never Stop Asking Questions, Question Your Environment, Question Your Government, above all Question Yourself.  We all lose when you Stop asking Why?

#7 EdwardHowton

EdwardHowton
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:04:37 AM

Posted 28 April 2014 - 06:14 AM

Did all the ipconfig stuff, thanks for that, but I'm not entirely sure how to go into my adapter. Going through device manager shows a list of dropdown menu items that seem irrelevant to what you suggested; Energy Star and jumbo packets and that kind of thing, no 'auto'. Some network connection menu has options for Internet Protocols v4 and v6, both already auto everything. Maybe it's a Windows 7 thing I'm unfamiliar with?

 

Running 'hosts' did nothing, searching in Start did find internet options to configure a proxy server, but I don't know what I'm doing, so I stopped there. I'm assuming that has something to do with making my default match up to DHCP somehow?

 

Sheesh. This is making me long for the days of DOS, where I knew my way around. Thanks for the help so far.



#8 Orecomm

Orecomm

  • Members
  • 266 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Roseburg, Oregon
  • Local time:01:37 AM

Posted 28 April 2014 - 09:36 AM

Hello Edward,

 

The one really curious thing I see in your results are the two static "default routes" pointing to 5.0.0.1 and 25.0.0.1. They aren't addresses on your local network, nor are they loopbacks to firewall or filters on your computer. I have no idea how they got there, but they seem to be bogus. They would certainly cause confusion in your routing, and always on the first hop. I would suggest removing them. To do this get back to your friendly CMD prompt and enter:

Route delete 0.0.0.0

This will probably break your DHCP installed default route as well, so you will need to do:

ipconfig /release

ipconfig /renew

to get your default back. 

 

From your config it looks like you are directly connected to the ISP modem and getting a public IP. You also have netbios over TCP enabled on the interface. This is risky, exposing your computer directly to the raw internet with lots of ports open. I generally recommend a NAT router of some sort between the Internet and your computer, or at least turn off the Microsoft Client and File and Print services. There could also be a problem if you have more than one device installed behind your ISP modem (for instance on a switch) without a local router. Many modems support only a single device, and if multiples are connected only one at a time will function, and which can change over a matter of seconds. 

 

As for the 10. net DHCP server, that is actually quite possible. An ISP may do this to keep it from being accessed remotely but any devices on the local network segment can still reach it. A DHCP server does not have to be on the same address range that it is handing out, although that is the usual default. DHCP happens before your device gets it's "real" IP address, at the link level, so the address of the server really doesn't matter to the protocol.

 



#9 C03_M4NN

C03_M4NN

  • Members
  • 36 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Earth
  • Local time:04:37 AM

Posted 28 April 2014 - 10:52 PM

I'd be curious to find out if it's hardware or software related... Have you tried a trace or path ping in safemode w networking at all?



#10 czarboom

czarboom

  • Members
  • 608 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Central Texas
  • Local time:03:37 AM

Posted 29 April 2014 - 01:54 AM

 

Did all the ipconfig stuff, thanks for that, but I'm not entirely sure how to go into my adapter. Going through device manager shows a list of dropdown menu items that seem irrelevant to what you suggested; Energy Star and jumbo packets and that kind of thing, no 'auto'. Some network connection menu has options for Internet Protocols v4 and v6, both already auto everything. Maybe it's a Windows 7 thing I'm unfamiliar with?

 

  • To get into your adapter, go down to the internet icon in the bottom right corner of your device.  (if using wifi it will look like cell phone bars)
  • Click on the adapter
  • move your cusor to your network and right click on it
  • select status
  • in the window that pops up in the bottom right side click on Properties again
  • another window pops up, Click to highlight "internet Protocol Version 4 (TCP/IPv4)"
  • Then select properties
  • Make sure (unless you did it on purpose) that DHCP is set (meaning in auto)
  • You can click on advanced and check the setting there also. 

Hope that explains it a little.

 

You own your own router?  Are you using a router or do you just connect to the modem?  If your using a router check the manufactures website for a firmware update.  This can cause all types of issues.  I had one that one day started dropping the wifi signal, no reason for it.  Couldnt stay connected at all.  Found it had a firmware update and all was good.

 

Last thing you can try is to reset all TCP/IP stack info.  This will clean out all know connections in your device.  Just to be safe though save a copy of your registry before you do this.  This will get rid of all the know paths and from there you can run mini tool box again after you set back up your connection.  

If you want to do this (I would and have before) do the following:

1. Click on Start button.
2. Type Cmd in the Start Search text box.
3. Press Ctrl-Shift-Enter keyboard shortcut to run Command Prompt as Administrator. Allow elevation request.
4. Type netsh int ip reset in the Command Prompt shell, and then press the Enter key.  If you want to see all the options type netsh int ip     (this will give you the list for other options)
5. Restart the computer.

The command will remove all user configured settings on TCP/IP stack and return it to original default state by rewriting pertinent registry keys that are used by the Internet Protocol (TCP/IP) stack to achieve the same result as the removal and the reinstallation of the protocol. The registry keys affected are:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\

and

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DHCP\Parameters\

 

After you do this you will need to reconnect to your network / gateway.  Lets see what the new info to connects you with. 


CZARBOOM 
 
"Never Stop Asking Questions, Question Your Environment, Question Your Government, above all Question Yourself.  We all lose when you Stop asking Why?

#11 technonymous

technonymous

  • Members
  • 2,499 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:01:37 AM

Posted 29 April 2014 - 09:18 AM

Could try to reset the router. Save the router config.bin file and then reset the router to factory defaults and then load the config.bin back in. Had to do this to a router that was having same issue.



#12 EdwardHowton

EdwardHowton
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:04:37 AM

Posted 29 April 2014 - 03:53 PM

C03 brought up a good point: safe mode with networking started up, but couldn't find the network adapter. I double checked and it was set up to use it (had to follow a Microsoft tech's instructions to force safe mode manually because my F8 key opens up BIOS), but networking wasn't written on the safe mode border and I wasn't connected to the internet. That's when the tech started asking me my credit card information, because extortion is a good business model now.

 

The instructions on how to get to the adapter didn't work for me; I guess my icon is different because I'm on a glorified LAN or something, but I did find the Internet Protocol version 4 properties screens and everything is set to auto.

 

Don't own a router, so that can't be the problem. Plugged directly into my modem.

 

Backed up those registry entries, did the netsh stuff, ran minibox.

 

 

MiniToolBox by Farbar Version: 23-01-2014
Ran by User (administrator) on 29-04-2014 at 16:47:23
Running from "C:\Users\User\Desktop"
Microsoft Windows 7 Home Premium Service Pack 1 (X64)
Boot Mode: Normal
***************************************************************************

========================= Flush DNS: ===================================

Windows IP Configuration

Successfully flushed the DNS Resolver Cache.

========================= IE Proxy Settings: ==============================

Proxy is not enabled.
No Proxy Server is set.

"Reset IE Proxy Settings": IE Proxy Settings were reset.
========================= Hosts content: =================================



========================= IP Configuration: ================================

Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller = Local Area Connection (Connected)


# ----------------------------------
# IPv4 Configuration
# ----------------------------------
pushd interface ipv4

reset


popd
# End of IPv4 configuration



Windows IP Configuration

Host Name . . . . . . . . . . . . : User-PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller
Physical Address. . . . . . . . . : F4-6D-04-25-69-36
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::858e:a54d:7dc9:405%15(Preferred)
IPv4 Address. . . . . . . . . . . : 24.203.12.141(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : April-29-14 4:41:43 PM
Lease Expires . . . . . . . . . . : April-29-14 5:34:08 PM
Default Gateway . . . . . . . . . : 24.203.12.1
DHCP Server . . . . . . . . . . . : 10.23.113.4
DHCPv6 IAID . . . . . . . . . . . : 318008580
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-15-91-D7-58-F4-6D-04-25-69-36
DNS Servers . . . . . . . . . . . : 24.201.245.77
24.200.241.37
24.200.243.189
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{16C6C97C-6C23-4C98-A948-D0CB9886BD2B}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:5ef5:79fd:433:3061:e734:f372(Preferred)
Link-local IPv6 Address . . . . . : fe80::433:3061:e734:f372%11(Preferred)
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter 6TO4 Adapter:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2002:18cb:c8d::18cb:c8d(Preferred)
Default Gateway . . . . . . . . . : 2002:c058:6301::c058:6301
DNS Servers . . . . . . . . . . . : 24.201.245.77
24.200.241.37
24.200.243.189
NetBIOS over Tcpip. . . . . . . . : Disabled
Server: dns2.videotron.ca
Address: 24.201.245.77

Name: google.com
Addresses: 2607:f8b0:4006:808::100e
74.125.226.68
74.125.226.67
74.125.226.73
74.125.226.72
74.125.226.65
74.125.226.71
74.125.226.78
74.125.226.66
74.125.226.69
74.125.226.70
74.125.226.64


Pinging google.com [74.125.226.64] with 32 bytes of data:
Reply from 74.125.226.64: bytes=32 time=33ms TTL=54
Reply from 74.125.226.64: bytes=32 time=32ms TTL=54

Ping statistics for 74.125.226.64:
Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 32ms, Maximum = 33ms, Average = 32ms
Server: dns2.videotron.ca
Address: 24.201.245.77

Name: yahoo.com
Addresses: 206.190.36.45
98.138.253.109
98.139.183.24


Pinging yahoo.com [98.139.183.24] with 32 bytes of data:
Reply from 98.139.183.24: bytes=32 time=29ms TTL=55
Reply from 98.139.183.24: bytes=32 time=40ms TTL=55

Ping statistics for 98.139.183.24:
Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 29ms, Maximum = 40ms, Average = 34ms

Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Ping statistics for 127.0.0.1:
Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
===========================================================================
Interface List
15...f4 6d 04 25 69 36 ......Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller
1...........................Software Loopback Interface 1
10...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
11...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
12...00 00 00 00 00 00 00 e0 Microsoft 6to4 Adapter
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 24.203.12.1 24.203.12.141 10
24.203.12.0 255.255.255.0 On-link 24.203.12.141 266
24.203.12.141 255.255.255.255 On-link 24.203.12.141 266
24.203.12.255 255.255.255.255 On-link 24.203.12.141 266
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 24.203.12.141 266
255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
255.255.255.255 255.255.255.255 On-link 24.203.12.141 266
===========================================================================
Persistent Routes:
None

IPv6 Route Table
===========================================================================
Active Routes:
If Metric Network Destination Gateway
12 1110 ::/0 2002:c058:6301::c058:6301
1 306 ::1/128 On-link
11 58 2001::/32 On-link
11 306 2001:0:5ef5:79fd:433:3061:e734:f372/128
On-link
12 1010 2002::/16 On-link
12 266 2002:18cb:c8d::18cb:c8d/128
On-link
15 266 fe80::/64 On-link
11 306 fe80::/64 On-link
11 306 fe80::433:3061:e734:f372/128
On-link
15 266 fe80::858e:a54d:7dc9:405/128
On-link
1 306 ff00::/8 On-link
11 306 ff00::/8 On-link
15 266 ff00::/8 On-link
===========================================================================
Persistent Routes:
If Metric Network Destination Gateway
0 4294967295 2620:9b::/96 On-link
0 4294967295 2620:9b::/96 On-link
0 9000 ::/0 2620:9b::1900:1
===========================================================================
========================= Winsock entries =====================================

Catalog5 01 C:\Windows\SysWOW64\NLAapi.dll [52224] (Microsoft Corporation)
Catalog5 02 C:\Windows\SysWOW64\napinsp.dll [52224] (Microsoft Corporation)
Catalog5 03 C:\Windows\SysWOW64\pnrpnsp.dll [65024] (Microsoft Corporation)
Catalog5 04 C:\Windows\SysWOW64\pnrpnsp.dll [65024] (Microsoft Corporation)
Catalog5 05 C:\Windows\SysWOW64\mswsock.dll [232448] (Microsoft Corporation)
Catalog5 06 C:\Windows\SysWOW64\winrnr.dll [20992] (Microsoft Corporation)
Catalog5 07 C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live\WLIDNSP.DLL [134528] (Microsoft Corporation)
Catalog5 08 C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live\WLIDNSP.DLL [134528] (Microsoft Corporation)
Catalog9 01 C:\Windows\SysWOW64\mswsock.dll [232448] (Microsoft Corporation)
Catalog9 02 C:\Windows\SysWOW64\mswsock.dll [232448] (Microsoft Corporation)
Catalog9 03 C:\Windows\SysWOW64\mswsock.dll [232448] (Microsoft Corporation)
Catalog9 04 C:\Windows\SysWOW64\mswsock.dll [232448] (Microsoft Corporation)
Catalog9 05 C:\Windows\SysWOW64\mswsock.dll [232448] (Microsoft Corporation)
Catalog9 06 C:\Windows\SysWOW64\mswsock.dll [232448] (Microsoft Corporation)
Catalog9 07 C:\Windows\SysWOW64\mswsock.dll [232448] (Microsoft Corporation)
Catalog9 08 C:\Windows\SysWOW64\mswsock.dll [232448] (Microsoft Corporation)
Catalog9 09 C:\Windows\SysWOW64\mswsock.dll [232448] (Microsoft Corporation)
Catalog9 10 C:\Windows\SysWOW64\mswsock.dll [232448] (Microsoft Corporation)
x64-Catalog5 01 C:\Windows\System32\NLAapi.dll [70656] (Microsoft Corporation)
x64-Catalog5 02 C:\Windows\System32\napinsp.dll [68096] (Microsoft Corporation)
x64-Catalog5 03 C:\Windows\System32\pnrpnsp.dll [86016] (Microsoft Corporation)
x64-Catalog5 04 C:\Windows\System32\pnrpnsp.dll [86016] (Microsoft Corporation)
x64-Catalog5 05 C:\Windows\System32\mswsock.dll [326144] (Microsoft Corporation)
x64-Catalog5 06 C:\Windows\System32\winrnr.dll [28672] (Microsoft Corporation)
x64-Catalog5 07 C:\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDNSP.DLL [168304] (Microsoft Corporation)
x64-Catalog5 08 C:\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDNSP.DLL [168304] (Microsoft Corporation)
x64-Catalog9 01 C:\Windows\System32\mswsock.dll [326144] (Microsoft Corporation)
x64-Catalog9 02 C:\Windows\System32\mswsock.dll [326144] (Microsoft Corporation)
x64-Catalog9 03 C:\Windows\System32\mswsock.dll [326144] (Microsoft Corporation)
x64-Catalog9 04 C:\Windows\System32\mswsock.dll [326144] (Microsoft Corporation)
x64-Catalog9 05 C:\Windows\System32\mswsock.dll [326144] (Microsoft Corporation)
x64-Catalog9 06 C:\Windows\System32\mswsock.dll [326144] (Microsoft Corporation)
x64-Catalog9 07 C:\Windows\System32\mswsock.dll [326144] (Microsoft Corporation)
x64-Catalog9 08 C:\Windows\System32\mswsock.dll [326144] (Microsoft Corporation)
x64-Catalog9 09 C:\Windows\System32\mswsock.dll [326144] (Microsoft Corporation)
x64-Catalog9 10 C:\Windows\System32\mswsock.dll [326144] (Microsoft Corporation)

**** End of log ****



#13 C03_M4NN

C03_M4NN

  • Members
  • 36 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Earth
  • Local time:04:37 AM

Posted 29 April 2014 - 06:08 PM

since you can't get into safemode, w networking, try disabling your firewall that you have running and try your tracert (if you have the same loss, check msconfig to see that it still isn't running in the background.)  

The only reason i suggest that is from what i see, it looks like you have a firewall set to pretty well have everything locked down but SSL on 443 which may be causing some of this issue. . . chances are it won't fix the issue but it sure will eliminate a lot of steps.



#14 EdwardHowton

EdwardHowton
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:04:37 AM

Posted 03 May 2014 - 02:32 AM

I'm about ready to give up here. Not only has trying everything changed nothing at all, but now I get random times where my computer's hard drive goes into work overload, which wasn't happening a week ago.



#15 technonymous

technonymous

  • Members
  • 2,499 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:01:37 AM

Posted 05 May 2014 - 11:59 PM

Did you see my post #11? Seriously it can be the router causing it, I have seen this a dozen times. It looks like the ISP is dropping packets when it was the local router.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users