Strange: Cannot communicate between 2 virgin broadband connections

[kitsimply]

Hi All

This is rather strange. Cannot find answer anywhere. I have virgin broadband for 2 locations. (1 is 20meg the other is 2 meg). I try to vpn, ping, etc from one to the other but it always times out. Tracert stops after the first hop. 10.*.*.*

I can connect from other broadband services that are non Virgin, ie UKOnline, Bt connect etc. All necessary ports are open for vpn etc so not a firewall problem.

All I can think of is that the ip address 82.*.*.* are very close between them.

I have also tried using opendns but still the same problem.

Thanks in advance.

[MovedGoalPosts]

Could both PCs have the same IP (LAN) IP address being issued to them as default by the VM modems? That could mess up their identities to each other?

Do you have router's at each end, or are they single PCs direct connected to the modems? If a router are you sure port forwards and that sort of stuff is correct?

[Graham M]

Also don't forget that some routers have the ability to block ping requests

[kitsimply]

Both are using routers, I have port forwarding set up correctly. I can connect via vpn from another broadband connection UKonline.

I recently changed from btinternet at the place I am trying to connect to using the same equipment. The only thing that has changed now is that I have changed the connection to VM 20meg.

So
VM <--> BTConnect OK
VM <--> UKonline OK
VM <--> VM No response.

[popper]

Both are using routers, I have port forwarding set up correctly. I can connect via vpn from another broadband connection UKonline.

I recently changed from btinternet at the place I am trying to connect to using the same equipment. The only thing that has changed now is that I have changed the connection to VM 20meg.

So
VM <--> BTConnect OK
VM <--> UKonline OK
VM <--> VM No response.

the fact your web side IPs are nearly the same doesnt matter as long as their not the same IP.

the fact you cant even ping the changed BT to VM20Mbit and get a response needs looking at before you even think about complicating things like using VPN etc.

its a long shot,but perhaps you have an old setting on the old BT machine thats still pointing to the old BT settings and not the new VM config by mistake.

try a total hardware reset of your router there, and see if you can at least ping both ways from each VM end and get that response.

remember to use the others VM web side IP and not the LAN side IP to ping and get a response.

80.* ,81.* ,82.* , and now 62.* are the start of the given web side IPs that i know exist, perhaps there are more ?.

[kitsimply]

It seems strange that other internet connections can ping the vm connection. Tracert stops at 10.136.232.1

May be that VM has some sort of way of blocking communication between their own ip ranges?

May be if anyone has external ip starting with 82* please try to ping 82.28.42.146

[popper]

It seems strange that other internet connections can ping the vm connection. Tracert stops at 10.136.232.1

May be that VM has some sort of way of blocking communication between their own ip ranges?

May be if anyone has external ip starting with 82* please try to ping 82.28.42.146

im on the baguley,wythenshawe,manchester exC&W with a
62.* and even that isnt getting through to your end.

tracert is interesting ,i take it your UBR is the one below?
lutn-hem1-ubr-3-ge01.inet.ntl.com [80.4.118.98] use .

http://www.cableforum.co.uk/board/misc.php?do=connection
will tell you if it is i removed your cust bit.
-----------------------------------
K:\>tracert 82.28.42.146
Tracing route to cpc3-hem13-0-0-cust*.lutn.cable.ntl.com [82.28.42.146]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms my-LAN IP
2 420 ms 794 ms 494 ms my-VM internal 10.* IP
3 882 ms 689 ms 271 ms my-webside IP
4 259 ms 265 ms 249 ms bagu-t2core-b-ge-wan61.inet.ntl.com [195.182.175.25]
5 185 ms 388 ms 438 ms lee-bb-b-so-700-0.inet.ntl.com [62.253.188.29]
6 365 ms * 202 ms pop-bb-a-so-300-0.inet.ntl.com [213.105.175.130]
7 159 ms 187 ms 111 ms lutn-t3core-1a-so-000-0.inet.ntl.com [213.105.175.150]
8 270 ms 288 ms 72 ms lutn-t2cam1-a-ge-wan32.inet.ntl.com [195.182.174.174]
9 325 ms 447 ms 60 ms lutn-hem1-ubr-3-ge01.inet.ntl.com [80.4.118.98]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
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.
-----------------------

double check your currently given web side IP again ,it could be as simple as it may have changed now perhaps, and noone else has been given that IP again yet, so it doesnt exist any more.

BTW, pinging and connecting to other VM connected customers kit isnt and never has been a problem, iv gone it many times for exC&W/NTL/VM friends/users personal web/FTP/tunneled multicast etc servers set up on their home lan connected PCs, as long as theres a ping to both ends theres hope and a good chance of fixing it.

if theres no ping ,and your sure thats your real webside IP then theres a problem somewere in the internal VM part, BUT if your able to get out to the web on these machines its most likely you have the real VM webside IP wrong.

---------- Post added at 15:44 ---------- Previous post was at 15:14 ----------

ohh, and seeing as you are connecting through a router, log into that to perform your pings in there, as that is in effect your very first machine directly connected to the WAN side, not the PC(s) pluged into the LAN side of the router to be sure.

[xpod]

Not getting through to your end from my 82 ip address or my 86 ip address.
Falling short at the same place.
Can communicate just fine between my own 2 though.

EDIT They are in the same location though.:)

[Lord Nikon]

Don't VM block the default VPN port as standard? Tried moving the VPN port to a different number?

[Toto]

Don't VM block the default VPN port as standard? Tried moving the VPN port to a different number?

Yes, VM do block some ports, you may want to try a port outside the 1024 range.

[popper]

ping would still get through though, unless the router was set to not respond, however its not as the BT connection route/IP worked at some point apparently

[kitsimply]

Now this is getting stranger. I have tried ping from UKOnline. No response. but I can vpn in there.
Tracert stops at
325 ms 447 ms 60 ms lutn-hem1-ubr-3-ge01.inet.ntl.com [80.4.118.98]

clicking on http://www.cableforum.co.uk/board/mi...?do=connection

Your IP address is 82.28.42.146
Host cpc3-hem13-0-0-cust*.lutn.cable.ntl.com

can anyone see
http://82.28.42.146/exchange

---------- Post added at 12:07 ---------- Previous post was at 11:37 ----------

I now suspect it may well be a router problem. I have the Buffalo Air Station WHR-G54S with firmware 1.40

I connected the VM Modem directly to a pc and ping worked from alternative connection.

Anyone using the WHR-G54S router. Cannot find any option to enable ping or the likes.

[kitsimply]

found the option. its all working now enabling ping seems to have kicked started everything

[popper]

good, ping and tracert are also working from here now too.