Solved

Name resolution problems ever since cisco router install

Posted on 2004-08-11
7
494 Views
Last Modified: 2010-04-14
I have had internal and external name resolution problems ever since deploying 2 cisco routers (2501s) in my LAN consisting mostly of windows boxes..  Schematic here: http://mvpbaseball.cc/network.jpg

All my hosts (on the 192.168.1.0 network and 192.168.2.0 network) can ping each other fine. They can also ping any WAN address fine (so long as you use the IP, not the host name of the WAN address).  All my hosts can ping my gateway fine as well (cable router).  

However, when it comes to pinging my ISP's DNS server.....none of my hosts can ping it.  You are only able to ping my ISP's DNS server if you are connected directly to my cable router.

Any idea as to why local name resolution is not occuring? I know netbios broadcasts to resolve host names locally. Why isnt it working?  I know routers dont forward broadcasts by default, but that shouldnt make a different for the hosts all on the same subnet?

Thanks

0
Comment
Question by:dissolved
  • 4
  • 3
7 Comments
 
LVL 14

Expert Comment

by:dlwyatt82
ID: 11777202
The link to your network diagram isn't working.

Please post the output of "ipconfig /all" and "route print" from a PC that is having these problems. Also post the IP address(es) of your ISP's DNS server and your local DNS server (I assume this IP will be in your network.jpg once the link is fixed).
0
 

Author Comment

by:dissolved
ID: 11777392
Sorry here is the address of the schematic
http://mvpbaseball.cc/post.jpg
I will get the route print to you soon, as I am at work.

My ISPs dns server is 68.34.76.5
My internal dns server is 192.168.1.98

I have all my hosts using either the 2501a cisco router as their gateway. Or the 2501b router as their gateway. When the clients plug directly into the cable router, everything works fine.
0
 
LVL 14

Expert Comment

by:dlwyatt82
ID: 11777727
I will be able to troubleshoot a bit more when I see the "ipconfig /all" and "route print" output... It might actually be helpful to get that output from a client machine on each subnet, 192.168.1. and 192.168.2.

However, based on your network diagram, I have some concerns right off the bat:

1 - Why so many routers? A single Cisco router can easily act as a gateway between a WAN (internet) link and 2 or more private networks.
2 - Why include a DSL / Cable router in this situation? Those are intended for home users who do not have a more expensive, complicated solution (like your Cisco 2500s) available. I can't say this for certain yet, but I think part of your problem may be due to the fact that the cable router is not managable beyond a certain degree... ie, it has no idea that 192.168.0.* and 192.168.2.* are valid networks on its INTERNAL ports. Traffic bound for those addresses in some situations may be send back out through its default interface (the port connected to your cable modem and ISP).

0
Comprehensive Backup Solutions for Microsoft

Acronis protects the complete Microsoft technology stack: Windows Server, Windows PC, laptop and Surface data; Microsoft business applications; Microsoft Hyper-V; Azure VMs; Microsoft Windows Server 2016; Microsoft Exchange 2016 and SQL Server 2016.

 

Author Comment

by:dissolved
ID: 11778360
This is my home LAN, just testing things out trying to learn Cisco.  
I have a static route placed in my cable router, so it knows how to find the 192.168.2.0 network. When this wasnt in there, the 192.168.2.0 network couldnt ping WAN

I just added an internal DNS server and DHCP server (192.168.1.98). It's gateway is 192.168.1.1 and it CAN ping the WAN. All of my clients can now resolve names locally and remotely. However, I still cannot ping my ISP's DNS server (68.34.76.5) when I use the ciscos as the gateway. Pinging everything else on the WAN works.

Here is ipconfig all of the 192.168.1.0  client:



Windows IP Configuration



        Host Name . . . . . . . . . . . . : dissolved

        Primary Dns Suffix  . . . . . . . :

        Node Type . . . . . . . . . . . . : Unknown

        IP Routing Enabled. . . . . . . . : No

        WINS Proxy Enabled. . . . . . . . : No



Ethernet adapter Local Area Connection 4:



        Connection-specific DNS Suffix  . : 192.168.1.98

        Description . . . . . . . . . . . : 3Com EtherLink XL 10/100 PCI For Complete PC Management NIC (3C905C-TX)

        Physical Address. . . . . . . . . : 00-04-75-86-10-B3

        Dhcp Enabled. . . . . . . . . . . : Yes

        Autoconfiguration Enabled . . . . : Yes

        IP Address. . . . . . . . . . . . : 192.168.1.5

        Subnet Mask . . . . . . . . . . . : 255.255.255.0

        Default Gateway . . . . . . . . . : 192.168.1.40

        DHCP Server . . . . . . . . . . . : 192.168.1.98

        DNS Servers . . . . . . . . . . . : 192.168.1.98

        Lease Obtained. . . . . . . . . . : Wednesday, August 11, 2004 4:54:05 PM

        Lease Expires . . . . . . . . . . : Monday, May 07, 2007 4:54:05 PM



Here is the route

===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 04 75 86 10 b3 ...... 3Com EtherLink XL 10/100 PCI For Complete PC Management NIC (3C905C-TX) - Packet Scheduler Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0     192.168.1.40     192.168.1.5        20
    63.208.194.17  255.255.255.255      192.168.1.1     192.168.1.5        1
   64.156.132.140  255.255.255.255      192.168.1.1     192.168.1.5        1
        127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1        1
      192.168.1.0    255.255.255.0      192.168.1.5     192.168.1.5        20
      192.168.1.5  255.255.255.255        127.0.0.1       127.0.0.1        20
    192.168.1.255  255.255.255.255      192.168.1.5     192.168.1.5        20
     209.66.98.92  255.255.255.255      192.168.1.1     192.168.1.5        1
   216.109.118.66  255.255.255.255      192.168.1.1     192.168.1.5        1
   216.109.127.16  255.255.255.255      192.168.1.1     192.168.1.5        1
        224.0.0.0        240.0.0.0      192.168.1.5     192.168.1.5        20
  255.255.255.255  255.255.255.255      192.168.1.5     192.168.1.5        1
Default Gateway:      192.168.1.40
===========================================================================
Persistent Routes:
  None
0
 
LVL 14

Expert Comment

by:dlwyatt82
ID: 11778629
Hmm, your cable router must have a lot more configuration options than mine, since you were able to add that static route for 192.168.2.0 :) That's a good thing in this situation, though.

With that in mind, your clients on the 192.168.1. subnet should be using 192.168.1.1 as their default gateway, and the cable router will know that any traffic bound for 192.168.2.* will need to go through the 192.168.1.40 router. That's a small design change, really. You'll notice how your local routing table has several entries for public Internet IPs, and the gateway listed for those IPs is 192.168.1.1 - this happens because the OS / IP drivers are smart enough to figure out at some point that 192.168.1.40 is not the router that should be handling those packets, and it dynamically adjusts your local routing table so future traffic to those IPs will take the most efficient route.
I don't know a great deal about how these communication protocols work, just the concepts and the result.

I am a bit stumped as to why you can't ping the provider's DNS server though, when all you changed was the gateway of your clients. Your name resolution is probably working correctly only due to the fact that your Server is configured with the 192.168.1.1 gateway, and all forwarded DNS queries pass through the server (not directly from the client workstations).
0
 
LVL 14

Accepted Solution

by:
dlwyatt82 earned 125 total points
ID: 11778654
One thing to note - we have no idea exactly where the ping is failing... your packets may have travelled all the way to the provider's DNS server, it may have sent a reply, and somewhere on the return trip, something could have gone wrong with the routing. I don't see anything in your setup that would cause that to happen (perhaps someone else will notice an error),. Normally I would run a packet sniffer to see exactly what's happening, but I doubt you'll be able to sniff your ISP's network beyond your cable modem.
0
 

Author Comment

by:dissolved
ID: 11778689
Found the problem. Router issue.
Thanks man!
0

Featured Post

Better Security Awareness With Threat Intelligence

See how one of the leading financial services organizations uses Recorded Future as part of a holistic threat intelligence program to promote security awareness and proactively and efficiently identify threats.

Join & Write a Comment

NTFS file system has been developed by Microsoft that is widely used by Windows NT operating system and its advanced versions. It is the mostly used over FAT file system as it provides superior features like reliability, security, storage, efficienc…
In this article, I will show you HOW TO: Suppress Configuration Issues and Warnings Alert displayed in Summary status for ESXi 6.5 after enabling SSH or ESXi Shell.
Here's a very brief overview of the methods PRTG Network Monitor (https://www.paessler.com/prtg) offers for monitoring bandwidth, to help you decide which methods you´d like to investigate in more detail.  The methods are covered in more detail in o…
In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're interested in additional methods for monitoring bandwidt…

759 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

Need Help in Real-Time?

Connect with top rated Experts

18 Experts available now in Live!

Get 1:1 Help Now