FAO Bob Pullen - John Lewis mail server

[Marmaduke Jinks]

Bob

I'm having timeout issues in getting to this server either by the web page
or by (trying to) download mail into my mail client. I did a tracert and it
stopped at hop 4.

I rang through to the support desk (plusnet) and they told me to switch off
my router at 7pm and leave it off until 7pm.

Is this normal practice? Would it not suggest that the 4th step device
isn't working and that's what has to be fixed?

Cheers
MJ

[Plusnet Support Team]

On 14/12/2016 12:33, Marmaduke Jinks wrote:
> Bob
>
> I'm having timeout issues in getting to this server either by the web page
> or by (trying to) download mail into my mail client. I did a tracert and it
> stopped at hop 4.

Fine from here:

Tracing route to mail.johnlewisbroadband.com [212.159.8.37]
over a maximum of 30 hops:

1 3 ms 4 ms 3 ms home.gateway [192.168.1.254]
2 11 ms 11 ms 13 ms lo0.central10.pcn-bng02.plus.net
[195.166.130.249]
3 12 ms 12 ms 12 ms 411.be6.pcn-ir02.plus.net [84.93.253.79]
4 13 ms 12 ms 12 ms fa3-0-35.ptb-gw2.plus.net [195.166.129.29]
5 12 ms 12 ms 12 ms ae1.ptw-cr01.plus.net [195.166.129.0]
6 13 ms 13 ms 13 ms te9-4.ptn-gw01.plus.net [195.166.129.33]
7 19 ms 20 ms 20 ms gi5-1.peh-cr02.plus.net [84.93.232.61]
8 20 ms 22 ms 23 ms po5.peh-cr01.plus.net [84.93.232.16]
9 49 ms 27 ms 25 ms vlan2657.peh-elb01.plus.net [84.93.232.44]
10 20 ms 23 ms 20 ms 212.159.8.37

Trace complete.

Webmail working as well assuming you're referring to here -
https://webmail.johnlewisbroadband.com/

> I rang through to the support desk (plusnet) and they told me to switch off
> my router at 7pm and leave it off until 7pm.
>
> Is this normal practice? Would it not suggest that the 4th step device
> isn't working and that's what has to be fixed?

I'm not aware of any widespread issues. Can you get to anything on the
Plusnet/JLP network?

Is there any possibility somebody on another Plusnet line somewhere is
connected using the same login credentials as you?

--
|Bob Pullen Support
|Plusnet Plc. www.plus.net
|Raising £££ for Alzheimer's: http://bit.ly/2b1qEoq
+--------------- twitter.com/plusnet ----------------

[Marmaduke Jinks]

"Plusnet Support Team" <sup...@plus.net> wrote in message
news:9tCdnf2DDqsrx8zF...@brightview.co.uk...

> |Raising ŁŁŁ for Alzheimer's: http://bit.ly/2b1qEoq
> +--------------- twitter.com/plusnet ----------------

Hi

Thanks for replying.

Connection times out to:
https://webmail.johnlewisbroadband.com/

When I do tracert

Tracing route to webmail.johnlewisbroadband.com [212.159.8.35]

over a maximum of 30 hops:

1 41 ms 100 ms 99 ms dsldevice.lan [192.168.1.254]
2 24 ms 23 ms 24 ms lo0.central10.pcn-bng01.plus.net
[195.166.130.24
8]
3 24 ms 24 ms 24 ms 411.be5.pcn-ir01.plus.net [84.93.253.67]
4 * * * Request timed out.
5 *

It times out there and eventually gives up after 30.
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.

Is the routing table ok on 84.93.253.67?

Funnily enough I can now downlaod mail onto my mail client. But can't get
any web pages for JohnLewisbroadband?

MJ

[Plusnet Support Team]

>> |Raising £££ for Alzheimer's: http://bit.ly/2b1qEoq

If it wasn't I think we'd know about it. That router serves thousands of
subscribers.

> Funnily enough I can now downlaod mail onto my mail client. But can't get
> any web pages for JohnLewisbroadband?

If you can't get to the main homepage either then it suggests an issue
reaching things on our network (Webmail is hosted on different servers
to the main website).

When I see that, it's normally due to two concurrent connections using
the same account credentials.

Alternatively, it could be an issue with the dynamic (?) IP you're assigned.

--
|Bob Pullen Support
|Plusnet Plc. www.plus.net

|Raising £££ for Alzheimer's: http://bit.ly/2b1qEoq
+--------------- twitter.com/plusnet ----------------

[Marmaduke Jinks]

"Marmaduke Jinks" <Ji...@Totopoly.com> wrote in message
news:o2rn79$rru$1...@dont-email.me...

The download to the mail app was a one off. Now I get this error again

The server responded with an error. Account: '-------', Server:
'mail.waitrose.com', Protocol: POP3, Server Response: '-ERR Cannot connect
to POP server 212.159.9.242 (212.159.9.242:110), connect error 10060', Port:
110, Secure(SSL): No, Server Error: 0x800CCC90, Error Number: 0x800CCC90

I have used this mail down load every day for a long time and today is the
first time I have seen this message.

Can't log these details as I have no web access route to JLB

MJ

[Marmaduke Jinks]

"Plusnet Support Team" <sup...@plus.net> wrote in message

news:L8adnel0MPyN-czF...@brightview.co.uk...

>>> |Raising ŁŁŁ for Alzheimer's: http://bit.ly/2b1qEoq

> |Raising ŁŁŁ for Alzheimer's: http://bit.ly/2b1qEoq
> +--------------- twitter.com/plusnet ----------------

When I do a tracert to your

>>> Tracing route to mail.johnlewisbroadband.com [212.159.8.37]
>>> over a maximum of 30 hops:

Tracing route to 212.159.8.37 over a maximum of 30 hops

1 39 ms 100 ms 99 ms dsldevice.lan [192.168.1.254]
2 24 ms 24 ms 24 ms lo0.central10.pcn-bng01.plus.net
[195.166.130.24
8]
3 24 ms 24 ms 25 ms 411.be5.pcn-ir02.plus.net [84.93.253.71]

4 * * * Request timed out.
5 *

I get timed out at 4 - although different server.

MJ

[Richmond]

"Marmaduke Jinks" <Ji...@Totopoly.com> writes:

> The download to the mail app was a one off. Now I get this error again
>
> The server responded with an error. Account: '-------', Server:
> 'mail.waitrose.com', Protocol: POP3, Server Response: '-ERR Cannot connect
> to POP server 212.159.9.242 (212.159.9.242:110), connect error 10060', Port:
> 110, Secure(SSL): No, Server Error: 0x800CCC90, Error Number: 0x800CCC90
>

Excuse me for butting in, but 110 is the wrong port for SSL I think
isn't it?

[Bob Eager]

Yes. Which is why it says it ISN'T SSL. "Secure(SSL):No" !!

[Marmaduke Jinks]

"Bob Eager" <news...@eager.cx> wrote in message
news:ebd8or...@mid.individual.net...

Very interesting.. as we used to say at school.

DNS flush then a re-boot of the router and logging in as the admin results
in success.

Tracing route to webmail.johnlewisbroadband.com [212.159.8.35]
over a maximum of 30 hops:

1 42 ms 99 ms 99 ms dsldevice.lan [192.168.1.254]
2 23 ms 23 ms 23 ms lo0-plusnet.pcn-bng04.plus.net
[195.166.130.24]

3 24 ms 24 ms 23 ms 413.be8.pcn-ir01.plus.net [84.93.253.219]
4 24 ms 24 ms 24 ms gr-11-1-0.ptw-cr01.plus.net
[195.166.129.185]
5 25 ms 33 ms 24 ms te9-4.ptn-gw01.plus.net [195.166.129.33]
6 33 ms 31 ms 31 ms gi5-1.peh-cr02.plus.net [84.93.232.61]
7 31 ms 30 ms 33 ms reth1.peh-elbfw.plus.net [84.92.0.103]
8 31 ms 35 ms 32 ms 10.104.0.7
9 34 ms 34 ms 30 ms webmail.johnlewisbroadband.com
[212.159.8.35]

Trace complete.

I wonder why? Some network update, while I was logged in?

MJ

[Graham J]

Have you tried what the support desk suggested in the first place?
Allowing for typos in your original email you should power off your
router for at least 30 minutes. This ought to allow any "stale session"
to expire, thereby resolving any routing issue that prevents you
connecting to some public IP addresses.

The term "stale session" covers a multitude of possibilities, but the
resolution costs 30 minutes and requires no thought or diagnostic work
on the part of the support desk, which was why it was suggested.

Of course it would be nice to know the actual cause of the problem, but
unless you are tasked with preventing its future occurrence then a quick
and dirty solution is probably acceptable.

--
Graham J

[Marmaduke Jinks]

"Graham J" <gra...@invalid.com> wrote in message
news:o2rs9j$f2l$1...@dont-email.me...
<SNIP>

> Have you tried what the support desk suggested in the first place?
> Allowing for typos in your original email you should power off your router
> for at least 30 minutes. This ought to allow any "stale session" to
> expire, thereby resolving any routing issue that prevents you connecting
> to some public IP addresses.
>
> The term "stale session" covers a multitude of possibilities, but the
> resolution costs 30 minutes and requires no thought or diagnostic work on
> the part of the support desk, which was why it was suggested.
>
> Of course it would be nice to know the actual cause of the problem, but
> unless you are tasked with preventing its future occurrence then a quick
> and dirty solution is probably acceptable.
>
> --
> Graham J
>

Hi

They suggested 7pm tonight. But had read somewhere about a Windows 10 issue
requiring a dns refresh on the router. So I did both together and rather
than waiting til 7pm did it just a little while ago.

The old switch it off and on again did ultimately work.

Funny that they are my isp and it was their site that was the one affected
(?) and all the others were ok.

Thanks all and Bob too.

MJ

[Adrian Caspersz]

On 14/12/16 16:35, Graham J wrote:
>
> Have you tried what the support desk suggested in the first place?
> Allowing for typos in your original email you should power off your
> router for at least 30 minutes. This ought to allow any "stale session"
> to expire, thereby resolving any routing issue that prevents you
> connecting to some public IP addresses.
>
> The term "stale session" covers a multitude of possibilities, but the
> resolution costs 30 minutes and requires no thought or diagnostic work
> on the part of the support desk, which was why it was suggested.
>
> Of course it would be nice to know the actual cause of the problem, but
> unless you are tasked with preventing its future occurrence then a quick
> and dirty solution is probably acceptable.
>

TG582n WANDownSpoofing bug?

--
Adrian C

[Plusnet Support Team]

That would have shown in the traceroute resolution of the host name (it
didn't).

--
|Bob Pullen Broadband Solutions for
|Support Home & Business @
|Plusnet Plc. www.plus.net
+--------------- twitter.com/plusnet ----------------

[Plusnet Support Team]

On 14/12/2016 16:58, Marmaduke Jinks wrote:
> "Graham J" <gra...@invalid.com> wrote in message
> news:o2rs9j$f2l$1...@dont-email.me...
> <SNIP>
>> Have you tried what the support desk suggested in the first place?
>> Allowing for typos in your original email you should power off your router
>> for at least 30 minutes. This ought to allow any "stale session" to
>> expire, thereby resolving any routing issue that prevents you connecting
>> to some public IP addresses.
>>
>> The term "stale session" covers a multitude of possibilities, but the
>> resolution costs 30 minutes and requires no thought or diagnostic work on
>> the part of the support desk, which was why it was suggested.
>>
>> Of course it would be nice to know the actual cause of the problem, but
>> unless you are tasked with preventing its future occurrence then a quick
>> and dirty solution is probably acceptable.
>>
>> --
>> Graham J
>>
> Hi
>
> They suggested 7pm tonight. But had read somewhere about a Windows 10 issue
> requiring a dns refresh on the router. So I did both together and rather
> than waiting til 7pm did it just a little while ago.

The Windows 10 issue affects DHCP and would have left your PC with an
APIPA IP rather than the usual 192.168.1.0/24 IP. You wouldn't have been
able to use the Internet at all in this state.

Glas to hear it's sorted though :)

> The old switch it off and on again did ultimately work.
>
> Funny that they are my isp and it was their site that was the one affected
> (?) and all the others were ok.
>
> Thanks all and Bob too.
>
> MJ

[Marmaduke Jinks]

"Plusnet Support Team" <sup...@plus.net> wrote in message

news:2PmdnSPm_IJZNczF...@brightview.co.uk...

All sorted now (fingers crossed).

Thanks Bob.

MJ