I'm not sure what you mean here.yes, I have. I made the without the router.
I just pinged 8.8.8.8 and got a ~280 avg. if I was to ping google.com, it wouldn't respond. .
So that 'good' packet has a different origination IP address from your machine? Weird.here's something of interest
Protocol LAN IP:Port Verizon IP:Port DNS Direction
bad packet: UDP 192.168.1.45:64096 [snip] 10.13.0.1:53 Outgoing
good packet: TCP 192.168.1.42:64560 [snip] 23.202.251.229:80 Outgoing
the good packet comes from a different machine; my laptop. I'll try it later, as I'm pretty much about to sleep.So that 'good' packet has a different origination IP address from your machine? Weird.
IF the DNS change doesn't work:
Try manually setting you IP address. Pick an IP that is not in your DHCP Client table. Maybe something like 192.168.1.100 with netmask of 255.255.255.0 and default gateway of 192.168.1.1.
If you don't want to totally replace your DNS server maybe try ipconfig /flushdns firstthe good packet comes from a different machine; my laptop. I'll try it later, as I'm pretty much about to sleep.
I don't really mind replacing the DNS; I did the other day in fact.If you don't want to totally replace your DNS server maybe try ipconfig /flushdns first
it also wouldn't hurt to run malware/virus scan
So, how did that affect the problem?I don't really mind replacing the DNS; I did the other day in fact.
did this, too. just cookies.
didn't at all, actually. I can try it again.So, how did that affect the problem?