[Webinar] Streamline your web hosting managementRegister Today

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

Confused on DNS - Problem with Tracert with Fixed IP vs DHCP

I am stumped - I have a Windows 2003 Server Domain which is connected via T-1 to other company servers.   Some computers have fixed IPs,  some have their IP assigned by DHCP

Let's call the fixed IP computer A, and the DHCP assigned computer B
I am trying to ping a remote computer.  I know the IP address and it is in WINS

When A tries to pings it succeeds, when B tries to pings it fails
The same with tracert, A succeeds and B fails on the third jump
Both are looking in the right IP which happens to be 10.49.0.61
This is the route from A
*************************
Tracing route to 10.49.0.61 over a maximum of 30 hops
  1     1 ms    <1 ms     1 ms  192.168.44.2
  2    41 ms    41 ms    41 ms  192.168.43.2
  3    42 ms    42 ms    42 ms  192.168.16.5
  4    65 ms    65 ms   413 ms  162.97.62.153  === > Success

This is the route from B
Tracing route to 10.49.0.61 over a maximum of 30 hops

  1     1 ms    <1 ms    <1 ms  192.168.44.2
  2    41 ms    41 ms    41 ms  192.168.43.2
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.

Both computers get to 192.168.44.2, then to 192.168.43.2, but B never makes it to 192.168.16.5

Why would the DNS request be different from two computers with the same gateway and DNS servers.
What could cause this problem?

TIA - TOMG








The IPCONFIG results for A and B are identical.  


0
Tgilbert
Asked:
Tgilbert
1 Solution
 
Rob WilliamsCommented:
Have any routes been added to the PC's that can ping? Compare the output from    route print    of each.
0
 
QlemoDeveloperCommented:
I guess the routing table on 192.168.16.5 has no entry for DHCP ip address range. Let's say A is out of 192.168.1.0/24 and DHCP is out of 192.168.2.0/24. Since this are different networks, they are routed different.
0
 
TgilbertAuthor Commented:
Good Call - Yep - they had not configured the router to accept our new DHCP addresses. Fixed now - Thanks
0

Featured Post

Evaluating UTMs? Here's what you need to know!

Evaluating a UTM appliance and vendor can prove to be an overwhelming exercise.  How can you make sure that you're getting the security that your organization needs without breaking the bank? Check out our UTM Buyer's Guide for more information on what you should be looking for!

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