Moved to enta - lost part of the internet

[aekostas]

Hi,

I managed to move to Entanet (Vivaciti) this week and the throughput is good.

For the sites I can access. High-profile losses are microsoft.com, hp.com and (wait for it) vivaciti.com.

Is this expected after migration? Entanet support went through MTU (correctly set on router and all my adapters to 1458 and verified by ping tests to be optimum there) and DNS and gave up.

Some stats:

http://www.dslreports.com/tweakr/block:3ee3246?service=dsl&speed=8000&os=winXP&via=pppoA

Any ideas?

 

[Rygar]

Assuming you currently use windows and assuming you use use a router, I would boot up with an easy to use linux live CD like Linspire. Then try to get to those sites using the bundled browser. If you can then the problem is related to your windows installation (firewall, Peerguardian etc) if you cannot then it narrows the problem down to your ISP or hardware configuration.

Further to that all I could suggest is you post in the Entanet forum at Thinkbroadband, where various Entanet & Vivaciti staff post and give help (along with other knowledgable members).

FWIW I'm with Enta and can get to those sites no problem.

 

[The Dude]

Could just be a problem with Enta DNS... try pinging www.hp.com and see what response you get.



If you're not getting responses, set this as your primary DNS and see what happens...


83.170.64.2

 

[freeman]

I'm with UKFSN (Entanet) & all those sites work ok for me too
What DNS did Entanet say use ? It appears UKFSN use something called Open DNS (I thought it strange no more page cannot be displayed pages )

 

[aekostas]

I'm with UKFSN (Entanet) & all those sites work ok for me too
What DNS did Entanet say use ? It appears UKFSN use something called Open DNS (I thought it strange no more page cannot be displayed pages )

Thanks for all the answers. Enta suggested 195.74.102.146 and 195.74.113.62. I will try the other one and tell you.

In the meanwhile, streaming at 450 does not work well for me at the moment.

 

[aekostas]

The new DNS does not make much difference, in that I can now see hp.com (with either DNS servers or with no explicit DNS set) but microsoft.com still says "Waiting for http://www.microsoft.com/..." for ever.

 

[aekostas]

With both the 82... and the 192... DNS servers I get the same result (they resolve to the same IP address but fail).

Thanks for any help you may be able to provide.
p.s.: Rygar, thanks for the idea, but I am not going to stick with Linux, so even if it works your way I will still be none the wiser about fixing the problem. If it helps, I am getting the same results both with my desktop that has seen use with Virgin before and with a new laptop whose settings (bar MTU) should be pretty virgin.

C:\Documents and Settings>ping www.microsoft.com

Pinging lb1.www.ms.akadns.net [207.46.198.60] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 207.46.198.60:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Documents and Settings>ping www.hp.com

Pinging www.hpgtm.nsatc.net [192.151.52.187] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.151.52.187:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

 

[aekostas]

I can now see hp.com

Scrap that, lost it again...

Can somebody post/mail me a tracert www.hp.com please?

Here is mine...

C:\Documents and Settings\Owner>tracert www.hp.com

Tracing route to www.hpgtm.nsatc.net [15.200.30.24]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 41 ms 39 ms 41 ms nutmeg.dsl.enta.net [87.127.229.98]
3 45 ms 40 ms 39 ms thc1h.gi2-6.telehouse-east.dsl.enta.net [87.127.229.78]
4 41 ms 40 ms 40 ms te5-2.telehouse-east.core.enta.net [62.249.192.121]
5 41 ms 47 ms 94 ms 197.ge-1-2-3.mpr1.lhr3.uk.above.net [213.161.78.217]
6 * * * Request timed out.
7 145 ms 140 ms 140 ms so-5-0-0.cr2.dfw2.us.above.net [64.125.29.145]
8 141 ms 152 ms 261 ms so-0-0-0.cr1.dfw2.us.above.net [64.125.28.209]
9 144 ms 153 ms 145 ms above-gw.dlstx.ip.att.net [192.205.32.161]
10 151 ms 150 ms 150 ms tbr1010201.dlstx.ip.att.net [12.123.16.194]
11 151 ms 151 ms 151 ms tbr2-cl12.hs1tx.ip.att.net [12.122.10.130]
12 152 ms 151 ms 150 ms ar4-p3110.hs1tx.ip.att.net [12.123.134.45]
13 151 ms 174 ms 152 ms 12.116.42.166
14 * * * Request timed out.
15 150 ms 151 ms 154 ms cce01gwes411-po2.houston.hp.com [16.225.8.38]
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.

 

[aekostas]

Problem solved! The MRU was set too low (1200); set it to 1458 and I am away!

http://www.dslreports.com/tweakr/block:1de80c5?service=dsl&speed=8000&os=winXP&via=pppoA

 

[RedRooster]

Problem solved! The MRU was set too low (1200); set it to 1458 and I am away!

http://www.dslreports.com/tweakr/block:1de80c5?service=dsl&speed=8000&os=winXP&via=pppoA

Don't forget your on ADSL Max with Enta, which means your line will be unstable for around 4/5 days of your 10 day training period. This is normal.
I'm with Swift, via Entanet and once my 10 day training was over, I was maxed out on NNTP and the connection really flys now

Also, try not to turn your router or modem off too much during the 10 day training period.
Also, you can visit the Entanet forum on here:-
http://www.thinkbroadband.com/
Many Entanet CS bods get on here to try and help solve problems before you raise a ticket with them.

 

[aekostas]

Thanks RedRooster. I don't think my MRU problem would have been solved without my intervention (I don't think it was a training issue). Maybe the Enta CS team would benefit from this (I asked about the MRU setting and they did not have a recommendation), but I cannot face another forum.

 

[freeman]

I take it Vivaciti didn't sugest MTU settings then ?
UKFSN recommended MTU set at 1492 or lower in their "order is complete" E-mail

 

[aekostas]

mRu is different to mTu. They suggested MTU (according to my calculations and their suggestion 1458 is the right value for Enta, by the way) but not MRU.