IE11 "Server unreachable" issues

[stuart]

Hi

I have a member contact me who is having issue with a "server unreachable message when using IE11 and Windows 8..anyone else have this issue?

As a rule I do not use IE11, but I will be testing this out today to see if I can replicate the issue. I will be running in "compatibility mode" as I do know that this needs to be done as vBulletin does have another issue with IE10/11 with the return key.. This is a known issue.

Stuart

[VAG-Abound]

That's me . To add a bit more detail (and I'm still trying to spot the trend)...

I have a work laptop with 64-bit W8.1 and IE11, and I can't easily get new / different stuff installed. If I access VWAF then after a while I get 'Server Unavailable' white IE pages. Not only does it affect the laptop but it seems that other devices using the same ADSL box (home PC and phone on WiFi) and hence public IP address are blocked. So you may think it is my ADSL box, but I have seen the same effect while using a hotel WiFi as well.

My best guess at the moment is that some network device close to the VWAF servers is disliking some network traffic and barring the connection for a while (it comes back after an hour or so). Even if I do:

telnet www.vwaudiforum.co.uk 80

I can't get a connection .

All a bit unscientific at the moment, and I'll try to get more concrete if it keeps happening.

[Sam]

What is the result of;

tracert -d vwaudiforum.co.uk

[VAG-Abound]

What is the result of;

tracert -d vwaudiforum.co.uk

I did that without the -d once when it failed, but didn't record the results. IIRC about 10 hops that gave a response then another half dozen or so that didn't.

I've never really understood the relevance of checking ICMP packet routing when looking at a TCP problem as I expect various devices to behave differently. Does it tell us much?

EDIT: Hmmm. Just tried it while the server is alive for me and it looks very different to what I recall. I'll try and force the problem to check again.

[Sam]

I did that without the -d once when it failed, but didn't record the results. IIRC about 10 hops that gave a response then another half dozen or so that didn't.

I've never really understood the relevance of checking ICMP packet routing when looking at a TCP problem as I expect various devices to behave differently. Does it tell us much?

EDIT: Hmmm. Just tried it while the server is alive for me and it looks very different to what I recall. I'll try and force the problem to check again.

Perhaps you could run it now so we have two results to compare?

You appear to be knowledgeable already so I won't teach you to suck eggs but ...

For me, the website is reachable, for you it is not. It would therefore make sense to assume your route to the website is failing somewhere. Hopefully a traceroute will show us where.

Pathping would be better still but it takes a lot longer to do anything and I know how precious our time is

[VAG-Abound]

Perhaps you could run it now so we have two results to compare?

Arrgh, I typed a "let's see what happens next, the compat thing may be masking it" reply to that on my work laptop, and when I clicked send - BAM: Server Unreachable. That's on W8.1 64-bit with IE11 with VWAF in the compatibility list - this does allow the editor to work at least .

So I've waited about an hour to be able to send this from the desktop machine in the house - quick reminder that this loses the server as well when the laptop that tickles the problem.

I now have traces from that desktop of when I can access VWAF:

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

Tracing route to vwaudiforum.co.uk [207.58.161.89]
over a maximum of 30 hops:
[Snipped first few pings]
  8    17 ms    17 ms    17 ms  194.25.6.194
  9    18 ms    17 ms    17 ms  63-218-55-213.static.pccwglobal.net [63.218.55.213]
 10    99 ms    99 ms   272 ms  servint.tenge10-3.br01.rst01.pccwbtn.net [63.218.125.22]
 11    99 ms    99 ms    98 ms  sc-sdv4255.servint.net [207.58.153.97]
 12    97 ms    97 ms    97 ms  vps.vwaudiforum.co.uk [207.58.161.89]
Trace complete.

and when I can't:

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

Tracing route to vwaudiforum.co.uk [207.58.161.89]
over a maximum of 30 hops:
[Snipped first few pings]
  8    17 ms    17 ms    77 ms  194.25.6.194
  9    18 ms    17 ms    17 ms  63-218-55-213.static.pccwglobal.net [63.218.55.213]
 10    98 ms    97 ms    98 ms  servint.tenge10-3.br01.rst01.pccwbtn.net [63.218.125.22]
 11    98 ms    98 ms    98 ms  sc-sdv4255.servint.net [207.58.153.97]
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
[Snipped further lost pings]
Trace complete.

so it looks like it is the vps.vwaudiforum.co.uk one that gets lost. Does that help us ?

[Sam]

Arrgh, I typed a "let's see what happens next, the compat thing may be masking it" reply to that on my work laptop, and when I clicked send - BAM: Server Unreachable. That's on W8.1 64-bit with IE11 with VWAF in the compatibility list - this does allow the editor to work at least .

[...]

so it looks like it is the vps.vwaudiforum.co.uk one that gets lost. Does that help us ?

It proves (at least to me) that there's nothing wrong with your side of the path but that there's something going on closer to the server itself.

One for our hosts I think.

[VAG-Abound]

It proves (at least to me) that there's nothing wrong with your side of the path but that there's something going on closer to the server itself.

One for our hosts I think.

If I get the chance / time / inclination I'll try logging things with Wireshark on both machines to see if that gives a clue. Feel free to jump in and tell me you've figured out the issue .

[VAG-Abound]

I haven't had time to visit the forum for a while, but have this week and am hitting the same issue. So if anyone thought they'd done something to fix it then it hasn't worked .

And reading the above reminds me I meant to dig out Wireshark...