Help - IP address on block lists - Page 2

Kymmy · 20-07-2010, 22:17

You sure it's not a firewall issue? You have turned it off to test? Just that the router will give you a local trusted gateway where as a direct modem connection will give you a WAN gateway

colinsunderland · 20-07-2010, 22:25

yes, just switched everything off and tried again and same results.

blue sabre · 21-07-2010, 09:22

Does it just appear to affect secure websites - ie start https:// rather then just http://?

Ignitionnet · 21-07-2010, 12:58

Dum de dum.

Quote:

Originally Posted by Ignitionnet

Oh I see.

When you have your PC directly connected you need to opt out of the crappy Advanced Network Error thing again.

When plugged in directly go to https://my.virginmedia.com/advancederrorsearch/settings

pip08456 · 21-07-2010, 15:14

Quote:

Originally Posted by Ignitionnet

Dum de dum.

Brick wall comes to mind

colinsunderland · 21-07-2010, 22:53

Sorry for not updating before now.
Turned the advanced network error thing off, same
Spoke to tech support again today, they actually said, 'this is a weird one, I have no idea whats wrong, all i can suggest is you wait until your IP address changes on the 27th (yep its chaged now to the 27th) and see if that fixes it'
Well thanks for that - loads of help

blackthorn · 22-07-2010, 04:19

Had this issue once and never did get to the bottom of it. What I did find out though was that changing browers helped. I could get to the Halifax with internet explorer but not firefox. Then all of a sudden it started to work again.

caph · 22-07-2010, 17:28

"Reply from 62.172.161.126: Destination net unreachable."

This gives clues.

Colin, can you try and reduce your MTU on your PC? It may be too high. Your router will have its own MTU set and will be different from your PC's MTU which could explain why you get problems on one but not the other.

colinsunderland · 22-07-2010, 20:52

rather than mess with the registry i believe the command ive used below does the same (please correct me if I'm wrong)
Tried various values down to 100, roughly all the same as below

Quote:

C:\Windows\system32>ping www.halifax.co.uk -f -l 450

Pinging www.halifax.co.uk [212.140.245.97] with 450 bytes of data:

Reply from 62.172.161.126: Destination net unreachable.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 212.140.245.97:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),

C:\Windows\system32>ping www.halifax.co.uk -f -l 800

Pinging www.halifax.co.uk [212.140.245.97] with 800 bytes of data:

Reply from 62.172.161.126: Destination net unreachable.
Reply from 62.172.161.126: Destination net unreachable.
Request timed out.
Request timed out.

Ping statistics for 212.140.245.97:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),

22-07-2010, 21:27

Quote:

Originally Posted by colinsunderland

Sorry for not updating before now.
Turned the advanced network error thing off, same
Spoke to tech support again today, they actually said, 'this is a weird one, I have no idea whats wrong, all i can suggest is you wait until your IP address changes on the 27th (yep its chaged now to the 27th) and see if that fixes it'
Well thanks for that - loads of help

did you change the mac address of the nic card on your pc? or have you tried a proxy or even opendns?

caph · 23-07-2010, 20:33

Quote:

Originally Posted by colinsunderland

rather than mess with the registry i believe the command ive used below does the same (please correct me if I'm wrong)
Tried various values down to 100, roughly all the same as below

Yes, spot on, much better idea. Don't ping Halifax or OPSI though, their servers don't respond to pings. Why did you pick those ones? Can you not get on their websites? Out of interest which websites can't you get on to? A tracert to a problem site might also shed more light on things. It still might be worth dropping your MTU and trying to access Halifax or OPSI.

---------- Post added at 21:33 ---------- Previous post was at 21:30 ----------

Quote:

Originally Posted by zing

or even opendns?

Zing, in all examples posted all addresses pinged are being resolved correctly. Unless the OP can provide an example of a ping to a website that doesn't resolve then this isn't a DNS issue.

Kymmy · 23-07-2010, 21:09

If you read the original post Halifax is one that he has problems with

colinsunderland · 23-07-2010, 21:45

Quote:

Originally Posted by caph

Yes, spot on, much better idea. Don't ping Halifax or OPSI though, their servers don't respond to pings. Why did you pick those ones? Can you not get on their websites? Out of interest which websites can't you get on to? A tracert to a problem site might also shed more light on things. It still might be worth dropping your MTU and trying to access Halifax or OPSI.

---------- Post added at 21:33 ---------- Previous post was at 21:30 ----------

Zing, in all examples posted all addresses pinged are being resolved correctly. Unless the OP can provide an example of a ping to a website that doesn't resolve then this isn't a DNS issue.

I used those as they are ones that don't load, some others with tracert's below (none of these load in browsers)

Quote:

Microsoft Windows [Version 6.0.6000]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Windows\system32>cd..

C:\Windows>cd..

C:\>tracert www.natwest.com

Tracing route to www.natwest.com [155.136.80.213]
over a maximum of 30 hops:

1 22 ms 8 ms 5 ms 10.37.68.1
2 23 ms 11 ms 31 ms midd-cam-1a-v135.network.virginmedia.net [213.10
6.239.53]
3 6 ms 24 ms 21 ms midd-core-1a-ae1-0.network.virginmedia.net [195.
182.176.97]
4 6 ms 9 ms 10 ms leed-bb-1a-as7-0.network.virginmedia.net [213.10
5.75.45]
5 13 ms 17 ms 15 ms popl-bb-1b-as1-0.network.virginmedia.net [62.253
.185.238]
6 34 ms 22 ms 15 ms tele-ic-2-as0-0.network.virginmedia.net [62.253.
184.6]
7 19 ms 19 ms 22 ms linx8.ukcore.bt.net [195.66.226.56]
8 20 ms 19 ms 19 ms core1-te-0-3-4-0.ilford.ukcore.bt.net [62.172.10
2.26]
9 22 ms 22 ms 50 ms core1-pos3-1.birmingham.ukcore.bt.net [62.6.204.
9]
10 32 ms 30 ms 31 ms core1-pos6-0.edinburgh.ukcore.bt.net [62.6.204.1
34]
11 36 ms 35 ms 40 ms interconnect1-gig1-0.edinburgh.fixed.bt.net [62.
6.199.3]
12 34 ms 35 ms 35 ms 62.172.57.238
13 62 ms 35 ms 34 ms 194.72.41.158
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Quote:

Microsoft Windows [Version 6.0.6000]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Windows\system32>cd..

C:\Windows>cd..

C:\>tracert www.pattinson.co.uk

Tracing route to www.pattinson.co.uk [195.97.206.68]
over a maximum of 30 hops:

1 6 ms 15 ms 5 ms 10.37.68.1
2 6 ms 5 ms 25 ms midd-cam-1b-v135.network.virginmedia.net [213.10
6.239.101]
3 6 ms 8 ms 7 ms midd-core-1b-ae2-0.network.virginmedia.net [195.
182.176.117]
4 15 ms 15 ms 15 ms manc-bb-1b-as6-0.network.virginmedia.net [213.10
5.75.49]
5 15 ms 15 ms 15 ms manc-bb-1a-ae0-0.network.virginmedia.net [62.253
.187.177]
6 23 ms 23 ms 24 ms glfd-bb-1b-ae1-0.network.virginmedia.net [213.10
5.175.146]
7 22 ms 24 ms 22 ms redb-ic-1-as0-0.network.virginmedia.net [62.253.
185.78]
8 18 ms 19 ms 22 ms linx-gw.onyx.net [195.66.224.35]
9 34 ms 28 ms 27 ms ge0-1.thlon-cr01.onyx.net [194.176.73.18]
10 28 ms 28 ms 30 ms ge0-3.dbncl-cr01.onyx.net [195.97.199.2]
11 28 ms 28 ms 28 ms v5.dbncl-esw04.onyx.net [194.176.72.23]
12 29 ms 31 ms 26 ms 195-97-207-124.onyx.net [195.97.207.124]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

C:\>

If I go through a site such as http://www.hidemyass.com/ they all load perfectly fine.

23-07-2010, 21:53

did you change the mac on you nic or just the router?

caph · 24-07-2010, 10:20

Quote:

Originally Posted by colinsunderland

I used those as they are ones that don't load, some others with tracert's below (none of these load in browsers)

If I go through a site such as http://www.hidemyass.com/ they all load perfectly fine.

Hmmm, I get exactly the same tracert's to these sites and I can't ping them either but I can browse to them. I don't think the tracert's are telling us anything to be honest. Can you try "telnet www.natwest.com 80" from a command prompt and then "GET /private.ashx" then hit enter when you are directly connected to your modem? If you get raw HTML then the problem could be with your browser. If you get a timeout or, even better, an error then it might help tracking this down. It might also help to give us "IPCONFIG /ALL" output for your active network connection when directly connected, don't worry about masking out MACs it's only cable modem MACs that are sensitive data.