cancel
Showing results for 
Search instead for 
Did you mean: 

Very slow speeds and can't connect to work VPN (dns failure)

chewit
Newbie
Posts: 1
Registered: ‎02-10-2015

Very slow speeds and can't connect to work VPN (dns failure)

Hi. I am trying to work from home using my work VPN.
When I try to connect to the VPN (nottshc.nhs.uk) I just get a DNS resolution failure.
My work has provided me with an alternative DNS www.access.nottshc.nhs.uk this does not work either.
I ran a tracert on this and found that there was timeouts/huge latency when traversing the virgin media network causing it to fail to connect/remain connected.
Is there anything you can do about this?
In addition to this it took 10 minutes to load these forums so I suspec there is a line or network fault as well.
I am not technical so could you please test my line and/or look at the dns issues I am having?
I may have to consider changing bb provider if not as I regularly need to work from home sadly.
Many thanks!
4 REPLIES 4
Townman
Superuser
Superuser
Posts: 22,920
Thanks: 9,537
Fixes: 158
Registered: ‎22-08-2007

Re: Very slow speeds and can't connect to work VPN (dns failure)

Hi Chewit,
A warm welcome to the forums.
This rather looks like an issue with your employer's IT services.  nottshc.nhs.uk does not appear to have any DNS routing information what so ever... neither PlusNet's nor Google's DNS has an IP address for that URL

#Microsoft Windows [Version 6.1.7601]
#02/10/15-12:57:57.43
C:\Users\Kevin>nslookup
Default Server:  dsldevice.lan
Address:  192.168.1.254
> set type=any
> nottshc.nhs.uk
Server:  dsldevice.lan
Address:  192.168.1.254
Non-authoritative answer:
nottshc.nhs.uk
       primary name server = external.nhs.uk
       responsible mail addr = hostmaster.nhs.uk
       serial  = 2015081401
       refresh = 86400 (1 day)
       retry   = 3600 (1 hour)
       expire  = 604800 (7 days)
       default TTL = 600 (10 mins)
nottshc.nhs.uk  nameserver = nsb.nhs.uk
nottshc.nhs.uk  nameserver = nsa.nhs.uk
nottshc.nhs.uk  nameserver = ns.nhs.uk
nottshc.nhs.uk  MX preference = 50, mail exchanger = mail.nhs.uk
nottshc.nhs.uk  MX preference = 50, mail exchanger = mail2.nhs.uk
> server 8.8.8.8
Default Server:  google-public-dns-a.google.com
Address:  8.8.8.8
> nottshc.nhs.uk
Server:  google-public-dns-a.google.com
Address:  8.8.8.8
Non-authoritative answer:
nottshc.nhs.uk
       primary name server = external.nhs.uk
       responsible mail addr = hostmaster.nhs.uk
       serial  = 2015081401
       refresh = 86400 (1 day)
       retry   = 3600 (1 hour)
       expire  = 604800 (7 days)
       default TTL = 600 (10 mins)
nottshc.nhs.uk  nameserver = nsa.nhs.uk
nottshc.nhs.uk  nameserver = nsb.nhs.uk
nottshc.nhs.uk  nameserver = ns.nhs.uk
nottshc.nhs.uk  MX preference = 50, mail exchanger = mail2.nhs.uk
nottshc.nhs.uk  MX preference = 50, mail exchanger = mail.nhs.uk


#Microsoft Windows [Version 6.1.7601]
#02/10/15-13:00:22.95
C:\Users\Kevin>tracert nottshc.nhs.uk
Unable to resolve target system name nottshc.nhs.uk.

There appears to be internet routing issues somewhere in Virgin Media's network to www.access.nottshc.nhs.uk

#Microsoft Windows [Version 6.1.7601]
#02/10/15-13:00:38.06
C:\Users\Kevin>tracert www.access.nottshc.nhs.uk
Tracing route to www.access.nottshc.nhs.uk [86.28.18.68]
over a maximum of 30 hops:
 1   242 ms     6 ms     1 ms  dsldevice.lan [192.168.1.254]
 2    38 ms    33 ms    35 ms  lo0-central10.ptn-ag01.plus.net [195.166.128.190]
 3    33 ms    33 ms    32 ms  link-b-central10.ptn-gw02.plus.net [212.159.2.130]
 4    32 ms    32 ms    33 ms  xe-5-2-0.ptw-cr02.plus.net [212.159.0.106]
 5    33 ms    34 ms    36 ms  linx-gw2.router.ntli.net [195.66.236.22]
 6    35 ms    35 ms    38 ms  brnt-bb-1a-ae14-0.network.virginmedia.net [212.250.14.201]
 7     *        *        *     Request timed out.
 8     *        *        *     Request timed out.
 9     *        *        *     Request timed out.
10    38 ms    37 ms    39 ms  brhm-core-2b-ae2-0.network.virginmedia.net [62.254.84.129]
11    45 ms    37 ms    38 ms  brhm-lam-2-tenge21.network.virginmedia.net [213.106.231.250]
12    62 ms    45 ms    39 ms  41.63-255-62.static.virginmediabusiness.co.uk [62.255.63.41]
13    40 ms    40 ms    40 ms  68-18-28-86.static.virginm.net [86.28.18.68]
Trace complete.


#Microsoft Windows [Version 6.1.7601]
#02/10/15-13:03:26.24
C:\Users\Kevin>pathping www.access.nottshc.nhs.uk
Tracing route to www.access.nottshc.nhs.uk [86.28.18.68]
over a maximum of 30 hops:
 0  ADVENT.lan [192.168.1.71]
 1  dsldevice.lan [192.168.1.254]
 2  lo0-central10.ptn-ag01.plus.net [195.166.128.190]
 3  link-b-central10.ptn-gw02.plus.net [212.159.2.130]
 4  xe-5-2-0.ptw-cr02.plus.net [212.159.0.106]
 5  linx-gw2.router.ntli.net [195.66.236.22]
 6  brnt-bb-1a-ae14-0.network.virginmedia.net [212.250.14.201]
 7     *        *        *
Computing statistics for 150 seconds...
           Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
 0                                           ADVENT.lan [192.168.1.71]
                               0/ 100 =  0%   |
 1    2ms     0/ 100 =  0%     0/ 100 =  0%  dsldevice.lan [192.168.1.254]
                               1/ 100 =  1%   |
 2   63ms     1/ 100 =  1%     0/ 100 =  0%  lo0-central10.ptn-ag01.plus.net [195.166.128.190]
                               0/ 100 =  0%   |
 3   54ms     1/ 100 =  1%     0/ 100 =  0%  link-b-central10.ptn-gw02.plus.net [212.159.2.130]
                               0/ 100 =  0%   |
 4   56ms     1/ 100 =  1%     0/ 100 =  0%  xe-5-2-0.ptw-cr02.plus.net [212.159.0.106]
                               0/ 100 =  0%   |
 5   50ms     1/ 100 =  1%     0/ 100 =  0%  linx-gw2.router.ntli.net [195.66.236.22]
                              99/ 100 = 99%   |
 6  ---     100/ 100 =100%     0/ 100 =  0%  brnt-bb-1a-ae14-0.network.virginmedia.net [212.250.14.201]
Trace complete.

I hope this helps you progress the problem with your employer's IT support.
You can point you IT staff to these diagnostics using this link - right click the link and choose 'copy shortcut' then paste into an email to your IT support..

Superusers are not staff, but they do have a direct line of communication into the business in order to raise issues, concerns and feedback from the community.

ejs
Aspiring Hero
Posts: 5,442
Thanks: 631
Fixes: 25
Registered: ‎10-06-2010

Re: Very slow speeds and can't connect to work VPN (dns failure)

I don't think there is any problem with the routing. I think pathping just gave up too quickly. Not all hops in a route will return any response, this does not indicate any problem. I had no problem pinging www.access.nottshc.nhs.uk. If I go to https://www.access.nottshc.nhs.uk I see a page titled "CISCO SSL VPN Service" with a message "Access is not permitted via this method."
Townman
Superuser
Superuser
Posts: 22,920
Thanks: 9,537
Fixes: 158
Registered: ‎22-08-2007

Re: Very slow speeds and can't connect to work VPN (dns failure)

@ejs,
As ever its always good to have another set of eyes on a problem... "there appears to be a routing problem" was intended to mean "there might be"  Wink
As you state it is very slow which might give rise to the browser timing out the connection.  The https:// connection is more than passing interest, it means there is noting responding on port 80, the usual 'target' for a web site.
Interestingly when I tried to connect to that service (using https) I get the following "dangerous site" warning...

There is a problem with this website’s security certificate.

The security certificate presented by this website was not issued by a trusted certificate authority.
Security certificate problems may indicate an attempt to trick you or intercept any data you send to the server. 
 
We recommend that you close this webpage and do not continue to this website.

Superusers are not staff, but they do have a direct line of communication into the business in order to raise issues, concerns and feedback from the community.

ejs
Aspiring Hero
Posts: 5,442
Thanks: 631
Fixes: 25
Registered: ‎10-06-2010

Re: Very slow speeds and can't connect to work VPN (dns failure)

I forgot to mention the security warning. I clicked through the warnings, the security certificate was issued by "Nottinghamshire Healthcare NHS Trust Issuing CA (DMH)", which isn't known and trusted by all the certificates that come with your web browser (or operating system, depending on which web browser and operating system you use). Probably not a big issue, although adding the certificate might be part of the VPN first time setup.
Perhaps nottshc.nhs.uk only resolves once connected to the VPN. I don't know the specific instructions or software provided.
These forums shouldn't take 10 minutes to load. They are so old fashioned and simple I find they load faster than a big modern website. It may have been a one off, or if other websites are slow to load, suggests a general connection issue.