Advertisement

06.17.2008 at 11:49AM PDT, ID: 23492804
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!
9.3

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

Asked by Tgilbert in Network Management, Windows Networking, Microsoft Server

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.  


Start Free Trial
 
Keywords: Confused on DNS - Problem with Trac…
Title
1 tracert
2 Tracert at least one timeout per hop
3 First hop on tracert timesout
4 Allow ping but not tracert
5 tracert
6 Network Tracert Question
 
Loading Advertisement...
 
[+][-]06.17.2008 at 12:38PM PDT, ID: 21806675

At Experts Exchange, members can ask their questions to thousands of technology professionals, also known as Experts. Experts compete and collaborate to answer those questions by leaving comments like this one.

Start your 30-day free trial to view this Expert Comment or ask the Experts your question.

 
[+][-]06.17.2008 at 12:41PM PDT, ID: 21806712

View this solution now by starting your 30-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

 

About this solution

Zones: Network Management, Windows Networking, Microsoft Server
Sign Up Now!
Solution Provided By: Qlemo
Participating Experts: 2
Solution Grade: A
 
 
 
Loading Advertisement...
20081112-EE-VQP-44 / EE_QW_2_20070628