Packet Loss Between Here (VM) and Office PC on Be* Broadband.

[Graham M]

Hi, I rely on being able to connect to my Office PC which is on a Be Broadband connection on a daily basis, but for the last week I have been getting near on 100% packet loss between here and there, yet I can connect using VNC on my iPad if I drop off of our wireless and onto 3G with no problems at all.

Traceroute is completely inconclusive as it starts timing out after the first hop (my router) and the same occurs when trying it from the other end, here are the ping stats from a few minutes ago just to illustrate.

Ping statistics for <IP address removed>:
    Packets: Sent = 38, Received = 9, Lost = 29 (76% loss),
Approximate round trip times in milli-seconds:
    Minimum = 52ms, Maximum = 195ms, Average = 82ms
Control-C

Any ideas?

Cheers
Graham

[kwikbreaks]

Try using something like LogMeIn instead of VNC - I've found that because of the way it works corporate firewalls don't cause it so many problems.

[Graham M]

Originally Posted by kwikbreaks

Try using something like LogMeIn instead of VNC - I've found that because of the way it works corporate firewalls don't cause it so many problems.

No corporate firewalls here,just an Adsl2+ router

---------- Post added at 15:47 ---------- Previous post was at 13:59 ----------

Well I've just had the engineer out for the other issue and it is better though not fixed, had some new filters and superhub fitted, so not sure if it's coincidental.

[Skie]

Try doing a pathping (same basic syntax as ping/tracert iirc)

That should show where the problem is.

[qasdfdsaq]

Routing problem between VM and Be by the looks of things - do what Skie said - pathping or tracert to find out where the issue is.

[Ignitionnet]

Be are having routing problems, the issue is theirs.

http://forums.thinkbroadband.com/beunlimited.html

[Graham M]

Thanks for that, weird issue though

[Chrysalis]

yeah ignition beat me to it, I expect its BE side.