DNS ISSUES - LATENCY FROM REMOTE SITE

Our remote site shares the same active directory domain name (abc.com)

Headquarters hosts a few websites, which the remote sites needs to access.

The DNS records on the  the remote site's DNS erver point to the public address of the www housed at HQ.
When the remote site attempts to access, the latency is unacceptable.  However, if a users access the sites from any other location in the world, the sites are served up quite quickly.  Any ideas.

Thanks
LVL 9
tl121000Asked:
Who is Participating?
 
Paul MacDonaldDirector, Information SystemsCommented:
Yes, that's what I was driving at, but it's odd the return path would be wonky for the remote site but no one else when they're both going across the Internet.  

Can you run a tracert to the site and see if you can identify a hop with high latency?  It's likely to be at one end or the other, probably not in the middle.
0
 
Paul MacDonaldDirector, Information SystemsCommented:
Is it possible the remote users are accessing the web site(s) via the WAN connection between the two facilities?  That would make the path "longer" than if they used the local default gateway.
0
 
tl121000Author Commented:
Paulmacd -

This is not a site to site VPN.  To access they need to aces via the Internet.

The gateway set on the clients is the default gateway of the inside interface of the remote router.
0
On-Demand: Securing Your Wi-Fi for Summer Travel

Traveling this summer?Check out our on-demand webinar to learn about the importance of Wi-Fi security and 3 easy measures you can start taking immediately to protect your private data while using public Wi-Fi. Follow us today to learn more!

 
Paul MacDonaldDirector, Information SystemsCommented:
Interesting!  Is there anything in DNS that might point them locally first?  

Does the behavior change if the use http://domain.tld versus http://www.domain.tld?
0
 
tl121000Author Commented:
the www record is actually hosted by an ASP and that's fine - the DNS is pointing to the proper public address, as it is for the HQ housed servers.
the other servers are glued to the proper public nat address (i.e. public1.abc.com >>> http://public1.abc.com).
Even if I go directly to the IP address, it is still slow (i.e. http://201.x.x.x)
0
 
sugunakarCommented:
Looks like there is some kind of routing issues in here.
I assume the site is hosted in head office. you are accessing site from remote site A and remote site B.  
Acess from remote site A is slow.
If you compare the routing to remote site A and remote site B from the head office, it may give some insights.



0
 
sugunakarCommented:
we have experience such kind of issues and you may have to involve your ISP in case you see the delays in somewhere in between.
trace route should throw some light in this regard.
0
 
tl121000Author Commented:
Sorry for the wait this was resolved some time ago.  It actually was a problem with the ISP.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.