Server unavailable because it has a different DG and DNS entry

Posted on 2007-07-23
Last Modified: 2010-04-10
Hi All

Very confused with a network issue I have at the moment so I hope you can help.

I have a complete windows 2003 network running AD. On this network I have a server which is in the same IP range as all the other server but has a differnent Default Gateway and different DNS servers assigned. This server can ping and access all other servers on the internal network but other servers can not access it via its IP address or its name.

I dont understand why. Hope you can help. If you need more information about my network then please do ask. Many thanks. Owais
Question by:museudf
    LVL 25

    Expert Comment

    chances are because of the gateway difference.  why is it different anyway?  It should be the same as all the other servers and clients.  Also, the DNS should generally be the same as well; however I don't believe the DNS is at fault in this particular problem

    Author Comment

    Hi Cyclops, thanks for the quick reply.

    My understanding was that the gateway was only used to tell the local computer which way to get out, and that other computers on the network could access the machine as they do not access it via its gateway.

    Is there not a work around I could use to get past this problem without changing the gateway, eg a static route or something.

    Your help on this would be great. Many thanks.

    LVL 7

    Expert Comment

    museudf: your understanding of the gateway is correct. It isn't involved here. When you are using AD, you're supposed to point all of the member computers to the internal AD DNS servers. They will then dynamically register themselves with the AD-integrated DNS so that other hosts in the domain can find them by name and IP address. Since you haven't done that, there is no record in your internal DNS for the server in question and the other servers have no idea it exists. So it is indeed a DNS issue. If you really need to have it pointing to a different DNS server, just go to one of the internal DNS servers and create an A record in the zone with the name of the server and its IP address. That will work but you'll have to remember that this won't be maintained manually so if that computer's IP address or name changes (or if you should ever remove the server), you'll have to update that A record manually.

    There are some other potential issues with using a different DNS server so if you can change that (point to AD instead), it would resolve all of your problems. You can leave the gateway as is - that isn't a problem.
    LVL 25

    Accepted Solution

    >>server can ping and access all other servers on the internal network but other servers can not access it via its IP address or its name
    Please explain this further then.  To me this says same segment server communication is good, different segment communication is bad.  This is why I said that the gateway is the issue.

    >>other servers can not access it via its IP address
    And this is why its not a DNS issue, although there could be a DNS issue, this particular problem is not caused by it.  This is because if you ping by IP address and it doesn't work, DNS isn't even being used so how can DNS be the culprit.

    However if I'm reading the original Q wrong, please let me know.  At any rate, is there a real reason you are using a different DG and DNS as everything else on this server.  Its just very odd.

    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    How to improve team productivity

    Quip adds documents, spreadsheets, and tasklists to your Slack experience
    - Elevate ideas to Quip docs
    - Share Quip docs in Slack
    - Get notified of changes to your docs
    - Available on iOS/Android/Desktop/Web
    - Online/Offline

    Suggested Solutions

    BIND is the most widely used Name Server. A Name Server is the one that translates a site name to it's IP address. There is a new bug in BIND (, affecting all versions of BIND 9 from BIND 9.1.0 (inclusive) thro…
    If you're not part of the solution, you're part of the problem.   Tips on how to secure IoT devices, even the dumbest ones, so they can't be used as part of a DDoS botnet.  Use PRTG Network Monitor as one of the building blocks, to detect unusual…
    Viewers will learn how to connect to a wireless network using the network security key. They will also learn how to access the IP address and DNS server for connections that must be done manually. After setting up a router, find the network security…
    In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor ( If you're interested in additional methods for monitoring bandwidt…

    737 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

    22 Experts available now in Live!

    Get 1:1 Help Now