Need to fix an internal network routing problem so that network requests sent to internal network computers are not sent out to the internet (log)

When I run a tracert command on a client computer (Windows XP, Windows Vista, or Windows 7) the network path that is taken goes out onto the internet and then back onto our internal company network.

Our Active Directory DNS server is installed on Windows Server 2008 R2.

I need to fix this routing problem so that when the hostname of a server is resolved by a client computer on our network, the correct network route that will be taken directly to the server without being routed onto the internet.

I belive that this issue might be being caused by incorrect DNS entries.

The internal static IP address assigned to the SCIAEX01 computer is 192.168.1.6.

What exactly can I do to resolve this issue?

This is the result of the tracert SCICAEX01 command line command:

Tracing route to sciaex01.sci-cg.dom [67.215.65.132]

over a maximum of 30 hops:



  1    <1 ms    <1 ms    <1 ms  192.168.1.1

  2    <1 ms    <1 ms    <1 ms  adsl-75-62-105-94.dsl.snfc21.sbcglobal.net [75.62.105.94]

  3    20 ms     8 ms    10 ms  192.0.2.100

  4    10 ms     9 ms     8 ms  dist1-vlan52.snfcca.sbcglobal.net [206.13.3.65]

  5     9 ms     8 ms     8 ms  bb1-10g2-0.snfcca.sbcglobal.net [216.102.176.224]

  6    10 ms    49 ms    20 ms  ppp-151-164-52-205.rcsntx.swbell.net [151.164.52.205]

  7    10 ms    10 ms    10 ms  xe-0-2-0-6.r07.snjsca04.us.bb.gin.ntt.net [129.250.8.93]

  8    10 ms    10 ms    11 ms  ae-7.r20.snjsca04.us.bb.gin.ntt.net [129.250.5.52]

  9    28 ms    28 ms    28 ms  as-2.r20.sttlwa01.us.bb.gin.ntt.net [129.250.4.140]

 10    28 ms    28 ms    28 ms  po-2.r00.sttlwa01.us.bb.gin.ntt.net [129.250.2.205]

 11    29 ms    51 ms    30 ms  ge-0.opendns.sttlwa01.us.bb.gin.ntt.net [129.250.12.78]

 12    28 ms    28 ms    28 ms  hit-nxdomain.opendns.com [67.215.65.132]



Trace complete.
IT GuyNetwork EngineerAsked:
Who is Participating?
 
Chris DentPowerShell DeveloperCommented:

I would ignore the router entirely for the moment. This is a problem with DNS lookup not routing.

The tracert you've posted indicates that a lookup for the hostname produces a public IP address:

Tracing route to sciaex01.sci-cg.dom [67.215.65.132]

Can you run "nslookup sciaex01.sci-cg.dom" and check the response you get? Can you also run "ping sciaex01.sci-cg.dom" and verify the IP it displays?

If you expect that to return 192.168.1.6 then the lookup, ping and tracert must reflect that.

Chris
0
 
hawardenCommented:
What are the dns servers configured on your client computers? nslookup in the command window of the client computer will also tell you what the default server for the client is.
0
 
IT GuyNetwork EngineerAuthor Commented:
I have the DNS servers configured at 192.168.1.5 (which is the DNS server and active directory domain controller for my company).

The other two DNS servers are DNS servers on the internet that provide DNS resolution for resolving website IP addresses to host names.
0
 
hawardenCommented:
Ok, a couple more questions:

1) Do you get the same results for the same type of query on the server itself (192.168.1.5)?

2) How is your router configured? It almost looks like the router is configured to route all traffic to default gateway, instead of just external.... if you have multiple internal networks you need to route between them if I recall correctly (haven't done that in a while so I may be a bit rusty)
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.