#1
  1. No Profile Picture
    Registered User
    Devshed Newbie (0 - 499 posts)

    Join Date
    Feb 2010
    Posts
    4
    Rep Power
    0

    Problem viewing one web page internally


    Hi,
    Our company website used to be hosted on one of our servers (server 2003 DC/DNS/DHCP/IIS6...). I simply pointed the domain at it and added host headers. It is now hosted elsewhere and I amended the A records accordingly with our registrar.
    I removed the zone for the .com domain (internally it is .local) and stripped out all host headers. There are still a few subdomains that are pointing at my servers for various hosted web applications. nslookup from all servers (set up the same at 4 sites) gives the right address although reports the name servers (my registrars) as non authoritative.
    I can ping from 3 sites but not the 4th. Tracert is slow, as is loading the web pages at these 3 sites, but times out, as does the web page, at the 4th. I have tried changing forwarders to Google 8.8.8.8 and 8.8.4.4 with the same results.
    I can ping from the broadband router at each site and it works perfectly externally so I am assuming that the problem is internal.
    PLEASE HELP as this is driving me mad.
    Cheers
    Graeme
    Last edited by fordy1765; October 1st, 2013 at 12:15 PM. Reason: Forgot something
  2. #2
  3. No Profile Picture
    Contributing User
    Devshed Newbie (0 - 499 posts)

    Join Date
    Jun 2004
    Location
    West Coxsackie, NY
    Posts
    37
    Rep Power
    11
    are you able to see the site on the server directly? Have you tested on more then 1 workstation.

    The domain in question is not the domain for the windows network correct?
  4. #3
  5. No Profile Picture
    Registered User
    Devshed Newbie (0 - 499 posts)

    Join Date
    Feb 2010
    Posts
    4
    Rep Power
    0
    Thanks for your reply. Answers below.

    Originally Posted by remcom
    are you able to see the site on the server directly? Have you tested on more then 1 workstation.

    No. I have generally tested from the server. If I connect directly to the broadband router I can ping etc at the site that I can't ping from any internal machine including the server and all workstations.

    The domain in question is not the domain for the windows network correct?
    Yes. Internal is oldname.local website is newconame.com
  6. #4
  7. No Profile Picture
    Registered User
    Devshed Newbie (0 - 499 posts)

    Join Date
    Feb 2010
    Posts
    4
    Rep Power
    0

    Tracert


    Below are 2 tracert results. The first from within the local network. The second from the same laptop when connected to the guest broadband at the same sight which is outside of the local network. The first times out at the same server as the second completes.


    Tracing route to macplc.com [69.16.244.151]
    over a maximum of 30 hops:

    1 3 ms 2 ms 3 ms xxxxxx.macukneuroscience.local [192.168.3.5]
    2 * * * Request timed out.
    3 34 ms 35 ms 37 ms te0-7-0-20.ccr22.lon01.atlas.cogentco.com [149.6
    .3.61]
    4 33 ms 33 ms * te0-1-0-2.ccr21.lon02.atlas.cogentco.com [130.11
    7.1.17]
    5 36 ms 34 ms 35 ms savvis.lon02.atlas.cogentco.com [130.117.14.58]

    6 35 ms 35 ms 36 ms cr1-te-0-0-5-0.uk1.savvis.net [204.70.206.61]
    7 130 ms 129 ms 131 ms cr1-te-0-6-0-0.chd.savvis.net [204.70.198.118]
    8 130 ms 128 ms 131 ms ber1-te-4-4.chq.savvis.net [206.28.96.30]
    9 132 ms 132 ms 135 ms 208.173.176.222
    10 138 ms 167 ms 145 ms lw-dc2-core6-te9-2.rtr.liquidweb.com [209.59.157
    .226]
    11 139 ms 139 ms 141 ms lw-dc3-dist10-po6.rtr.liquidweb.com [69.167.128.
    167]
    12 * * * Request timed out.
    13 * * * Request timed out.
    14 * General failure.

    Trace complete.



    Tracing route to macplc.com [69.16.244.151]
    over a maximum of 30 hops:

    1 3 ms 2 ms 1 ms homeportal [192.168.1.254]
    2 3 ms 31 ms 27 ms host81-134-80-1.in-addr.btopenworld.com [81.134.
    80.1]
    3 30 ms 29 ms 29 ms 213.120.182.141
    4 30 ms 29 ms 29 ms 213.120.161.82
    5 32 ms 30 ms 29 ms 31.55.164.185
    6 30 ms 29 ms 36 ms 31.55.164.107
    7 30 ms 28 ms 28 ms acc1-10GigE-0-2-0-7.bm.21cn-ipp.bt.net [109.159.
    248.110]
    8 * * * Request timed out.
    9 * * 34 ms 62.172.103.143
    10 34 ms 33 ms 32 ms t2c4-xe-9-0-0-0.uk-ilf.eu.bt.net [166.49.168.113
    ]
    11 36 ms 31 ms 32 ms t2c2-ge8-0-0.uk-ilf.eu.bt.net [166.49.237.177]
    12 109 ms 101 ms 101 ms t2c2-p5-0-0.us-nyc.eu.bt.net [166.49.164.82]
    13 116 ms 111 ms 115 ms be-10-301-pe01.111eighthave.ny.ibone.comcast.net
    [75.149.228.161]
    14 106 ms 105 ms 105 ms pos-1-10-0-0-cr01.newyork.ny.ibone.comcast.net [
    68.86.86.73]
    15 124 ms 125 ms 123 ms he-0-5-0-0-cr01.350ecermak.il.ibone.comcast.net
    [68.86.88.150]
    16 125 ms 122 ms 121 ms be-11-pe03.350ecermak.il.ibone.comcast.net [68.8
    6.84.102]
    17 127 ms 125 ms 125 ms 66.208.216.86
    18 131 ms 131 ms 129 ms lw-dc2-core6-te9-2.rtr.liquidweb.com [209.59.157
    .226]
    19 130 ms 129 ms 129 ms lw-dc3-dist10-po6.rtr.liquidweb.com [69.167.128.
    167]
    20 130 ms 127 ms 129 ms 69.16.244.151

    Trace complete.
    Last edited by fordy1765; October 2nd, 2013 at 05:43 AM. Reason: mistake
  8. #5
  9. No Profile Picture
    Registered User
    Devshed Newbie (0 - 499 posts)

    Join Date
    Oct 2013
    Location
    Oklahoma
    Posts
    11
    Rep Power
    0
    Okay I'm assuming that all domains on the local network have local ip addresses and your using port forwarding to the local address. But when your behind the router on the local network and you enter the address it looks up DNS records of the domain name and it redirects you back to your externel IP address.

    Accept if you are behind the network you are simply crashing traffic into each other and hanging at the router as it doesn't know how to route this.

    Basically your doing this

    Local Network > router > DNS servers > router > local server > back throu web > router (stuck and confused no longer nows how to route.). Basically it gets stuck and crashes data into each other because it will try to port forward all data back to the server which the router just gets clueless.


    But on lcoal network it goes
    Local computer > router > local server >> router > local computer

    I'm not sure if that is the best example, it just let it fly off my head.

    Basically how a local network works with the public network is through NAT (Network Address Translation). when you connect to a put say to a website on port 80 the request leaves from your local ip 192.168.1.100/24 it goes to the router and the router translates it from your local ip to externel ip, then it goes through your isp to its destination and replies then it goes back to your isp and router then translates back to local ip back to your computer.

    Your router is usually configure to work with all out going ports and only open inbound reports for replies only. Basically established connections. But if you open outbound port 80 the router is going to reply to port 80 which causes a NAT conflict. I know some Cisco routers have some features to deal with this, while others don't.

    Hopefully its a tad more understandable now.

    but basically its a network loopback problem, I can't think of its name. Best way to resolve this issue is get a router that can handle this or make a local dns server and configure clients to use it so it can resolve local ip's first.
    Last edited by jcarney1987; October 18th, 2013 at 10:18 PM. Reason: added more info
  10. #6
  11. No Profile Picture
    Registered User
    Devshed Newbie (0 - 499 posts)

    Join Date
    Feb 2010
    Posts
    4
    Rep Power
    0

    Solved


    Thanks for all your help. I finally sorted this. Turns out the forwarders I had used for years are no longer working and the alternates, Google, didn't work for some reason either so I assumed that wasn't the problem. When I tried a 3rd, OpenDNS, everything was sorted.
    Cheers
    Graeme

IMN logo majestic logo threadwatch logo seochat tools logo