[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 308
  • Last Modified:

No Access to my VPN server or my terminal server from home anymore....

I can no longer access my VPN server from home. I also can't access my terminal server from home. I can't ping them anymore and my trace fails. I believe it's an external names server issue. How can I prove DNS is the issue?
0
bernardb
Asked:
bernardb
  • 3
  • 3
2 Solutions
 
nyxynCommented:
You need to start by confirming whether the problem is related to your PC or not.
Did you install any new major updates/service packs?
New firewall software?
Etc.

As to confirm whether this is a DNS problem or not, you need to know the correct IP that the name should resolve to. For example, you try to VPN/RD to yourhost.net so as a start, you should know the correct IP that yourhost.net should resolve to.
After that, you can perform these two tests,
1. Try to resolve the name from your computer. If you are using a Windows machine, one way to resolve the hostname is by using the command nslookup yourhostname.net. Does it resolve correctly?
2. Also try to VPN / RD to the IP directly. Can you connect?
0
 
clowry15Commented:
Suggesting you knew it, you could try using the ip address.
0
 
bernardbAuthor Commented:
I was able to connect using the IP Address in the browser...What can I do to fix this?
0
SMB Security Just Got a Layer Stronger

WatchGuard acquires Percipient Networks to extend protection to the DNS layer, further increasing the value of Total Security Suite.  Learn more about what this means for you and how you can improve your security with WatchGuard today!

 
nyxynCommented:
The hostname is resolving incorrectly, this means one of two reasons:

1. The DNS record is incorrect/missing. This can be fixed from the domain name registration company side. Check who has the username/password to add/fix DNS records via the domain name registration company.
2. The DNS record is correct and resolves correctly from other locations, then it is a problem with your ISP and you should escalate to them.
0
 
bernardbAuthor Commented:
I don't know what the issue was, but it resolved itself....for now.
0
 
nyxynCommented:
Case 1:
It can be a simple DNS update propagation issue. In other words, if I change the DNS record of mynetwork.xyz to resolve to 172.168.100.1 instead of 192.168.100.1, it will take the DNS servers on the Internet some time (they say up to 3 days) to reflect the change and point to the new IP. Once the new DNS record updates are propagated, you can assume that things will be stable.

Case 2:
Your DNS hosting company does not have reliable servers, in this case, this can happen any time. Or, maybe they were doing some major upgrades unefficiently, so this will be only once. When this is the case, usually the hostname won't resolve anywhere correctly.

Case 3:
Your ISP was having some problems with its DNS servers and now they fixed it. When this is the case, only when you are using this ISP's internet conneciton, the hostname won't resolve correctly.

But in general, you can assume that problem is solved. Of course, if this happened again, you will definitely check the real cause and contact the responsible depending on whether it is case 1, 2 or 3.
0
 
bernardbAuthor Commented:
Thanks
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now