Solved

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

Posted on 2008-06-17
3
326 Views
Last Modified: 2013-11-05
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
Comment
Question by:Tgilbert
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
3 Comments
 
LVL 77

Expert Comment

by:Rob Williams
ID: 21806675
Have any routes been added to the PC's that can ping? Compare the output from    route print    of each.
0
 
LVL 70

Accepted Solution

by:
Qlemo earned 125 total points
ID: 21806712
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
 

Author Closing Comment

by:Tgilbert
ID: 31469870
Good Call - Yep - they had not configured the router to accept our new DHCP addresses. Fixed now - Thanks
0

Featured Post

Database Solutions Engineer FAQs

In this series, we will discuss common questions received as a database Solutions Engineer at Percona. In this role, we speak with a wide array of MySQL and MongoDB users responsible for both extremely large and complex environments to smaller single-server environments.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Is your computer hacked? learn how to detect and delete malware in your PC
Join Greg Farro and Ethan Banks from Packet Pushers (http://packetpushers.net/podcast/podcasts/pq-show-93-smart-network-monitoring-paessler-sponsored/) and Greg Ross from Paessler (https://www.paessler.com/prtg) for a discussion about smart network …
There's a multitude of different network monitoring solutions out there, and you're probably wondering what makes NetCrunch so special. It's completely agentless, but does let you create an agent, if you desire. It offers powerful scalability …
Monitoring a network: why having a policy is the best policy? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the enormous benefits of having a policy-based approach when monitoring medium and large networks. Software utilized in this v…
Suggested Courses

635 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question