[Last Call] Learn how to a build a cloud-first strategyRegister Now

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

DNS Issue

In my companies facility we are in the process of changing our  IP scheme from a 165.154.67/24 network to a 10.0/16 network. I have a cisco router with to ethernet cards so that all servers and peripherals can pass traffic bewtween the two networks. The problem I am having is with one Server which is on the 165.154.67 segment not being able to ping servers on the 10. segment by name. Now I have other servers on the 165.154.67 segment that can ping servers by name on the 10 segment with no problems. The difference be the one that cannot and the one that can is that the one that cannot is not part of my companies domain but the ones that can are. One of my co-workers says that we have a DNS problem. He says that the Server on the 165.154.67 segment that is not part of the domain should be able to ping servers on the 10 segment, and I say just the opposite. Do I indded have a DNS problem or am I correct by stating the problem is caused by this server not being part of the domain.

0
sharthun
Asked:
sharthun
  • 6
  • 5
  • 3
  • +1
1 Solution
 
Mad_JasperCommented:
IF the 165.154.67 server is not part of the domain, it would not be able to ping the 10. segment by name unless you added an entrie to the hosts file.

So, it appears that you are correct. Now enjoy rubbin' it in. ;-)
0
 
Mad_JasperCommented:
Wait a minute. Don't rub it in yet.

Is the server on the 165.154.67 segment that is not part of the domain using a DNS server that is on the domain. I would think that if you pointed the server to a DNS server on the domain then you would be able to ping computers on that domain by name. Check your DNS properties and try it out. Now, I doubt that hosts on the domain would be able to ping the non-domain server because their would be no entry in DNS. This would require a hosts file.
0
 
ShannonHerbertCommented:
Is the server on the 165.154.67 segment assigned an IP statically?

What OS is this server?

If it is not a member of the domain, then it probably isn't adding the domain suffix to the names you are trying to ping. Can you ping a fully qualified domain name (i.e. server.domain.com)?
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
sharthunAuthor Commented:
Question 1 is the server in question pointing to a DNS server that is on the Domain.  YES
Question 2 what is the OS. Windows Server 2003
Question 3 is the IP static. YES

Some additional data. The Server in question can ping all other servers or devices on the 165.154.67.segment by name with no problems.
0
 
ShannonHerbertCommented:

Can you post the output from an IPCONFIG /ALL from the server in question?

C:\>ipconfig /all

0
 
Mad_JasperCommented:
Is the troubled server a member server? It is a DC in it's own forest? It is not running DNS?

Probably not.

If you DNS options on the troubled server are pointing to the same DNS server that the other servers are using, then you should be able to ping servers on the 10.x.x.x network.

I am sure that you have tried this, but I want to make sure.

1.) On the troubled server, Start --> Run --> ipconfig /flushdns
2.) On the DNS server, clear the DNS cache
If still unable to ping the 10.x.x.x domain,
3.) Restart the DNS service on the DNS servers.

One other question. Can you ping the troubled server from the 10.x.x.x network?
0
 
norganCommented:
the server on the 10.x network should have an entry for the dns server on the 165.x network and vice versa, on a dns level it won;t matter if they are part of a domain or not as long as they each have some reference (i.e. a dns server entry) to each others networks.
alot of people like to over complicate dns, it's very straight forward and logical, just take a step back and ensure you have a phone book to lookup stuff in. if you only have your local phonebook to look up names then you won;t be able ot find your mate over in the next county, but if you have your local phonebook and your next counties phonebook then you can find not only people in your local county but also your mates in the next.
0
 
sharthunAuthor Commented:
Sorry for the delayed responses to your questions but I have been out of the office for a few days. So here goes.

here is the  IPCONFIG/ALL that was asked for.

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : admx345
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Unknown
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Dual Port Network Co
nnection
   Physical Address. . . . . . . . . : 00-0D-60-19-D3-08
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : 165.154.67.101
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :
   DNS Servers . . . . . . . . . . . : 165.154.67.12
                                       165.154.67.251

Ethernet adapter Local Area Connection 2:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Dual Port Network Co
nnection #2
   Physical Address. . . . . . . . . : 00-0D-60-19-D3-09
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : 172.16.1.11
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . : 172.16.1.1
   DNS Servers . . . . . . . . . . . : 165.154.67.12
                                       165.154.67.251

C:\Documents and Settings\Administrator>
*************************************************************************************
*************************************************************************************
Here is the ROUTE PRINT on the server in question

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator>route print

IPv4 Route Table
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x10003 ...00 0d 60 19 d3 08 ...... Intel(R) PRO/1000 MT Dual Port Network Conne
ction
0x10004 ...00 0d 60 19 d3 09 ...... Intel(R) PRO/1000 MT Dual Port Network Conne
ction #2
===========================================================================
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0       172.16.1.1      172.16.1.11     20
         10.0.0.0      255.255.0.0   165.154.67.254   165.154.67.101      1
        127.0.0.0        255.0.0.0        127.0.0.1        127.0.0.1      1
     165.154.67.0    255.255.255.0   165.154.67.101   165.154.67.101     10
   165.154.67.101  255.255.255.255        127.0.0.1        127.0.0.1     10
  165.154.255.255  255.255.255.255   165.154.67.101   165.154.67.101     10
       172.16.0.0      255.255.0.0      172.16.1.11      172.16.1.11     20
      172.16.1.11  255.255.255.255        127.0.0.1        127.0.0.1     20
   172.16.255.255  255.255.255.255      172.16.1.11      172.16.1.11     20
      192.168.0.0      255.255.0.0   165.154.67.254   165.154.67.101      1
        224.0.0.0        240.0.0.0   165.154.67.101   165.154.67.101     10
        224.0.0.0        240.0.0.0      172.16.1.11      172.16.1.11     20
  255.255.255.255  255.255.255.255   165.154.67.101   165.154.67.101      1
  255.255.255.255  255.255.255.255      172.16.1.11      172.16.1.11      1
Default Gateway:        172.16.1.1
===========================================================================
Persistent Routes:
  Network Address          Netmask  Gateway Address  Metric
         10.0.0.0      255.255.0.0   165.154.67.254       1
      192.168.0.0      255.255.0.0   165.154.67.254       1

C:\Documents and Settings\Administrator>
*************************************************************************************
*************************************************************************************
Here I can ping our Domain Controller by name. I can also ping another server on the same 165.154.67 network by name "hris1". I cannot ping by name the server"monitor" by name which is o the 10.0 network, but I can ping the IP of the server called "monitor".

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator>ping rudy

Pinging rudy [165.154.67.12] with 32 bytes of data:

Reply from 165.154.67.12: bytes=32 time<1ms TTL=128
Reply from 165.154.67.12: bytes=32 time<1ms TTL=128
Reply from 165.154.67.12: bytes=32 time<1ms TTL=128
Reply from 165.154.67.12: bytes=32 time<1ms TTL=128

Ping statistics for 165.154.67.12:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Documents and Settings\Administrator>ping hris1

Pinging hris1 [165.154.67.16] with 32 bytes of data:

Reply from 165.154.67.16: bytes=32 time<1ms TTL=128
Reply from 165.154.67.16: bytes=32 time<1ms TTL=128
Reply from 165.154.67.16: bytes=32 time<1ms TTL=128
Reply from 165.154.67.16: bytes=32 time<1ms TTL=128

Ping statistics for 165.154.67.16:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Documents and Settings\Administrator>ping monitor
Ping request could not find host monitor. Please check the name and try again.

C:\Documents and Settings\Administrator>ping 10.0.20.241

Pinging 10.0.20.241 with 32 bytes of data:

Reply from 10.0.20.241: bytes=32 time<1ms TTL=127
Reply from 10.0.20.241: bytes=32 time<1ms TTL=127
Reply from 10.0.20.241: bytes=32 time<1ms TTL=127
Reply from 10.0.20.241: bytes=32 time<1ms TTL=127

Ping statistics for 10.0.20.241:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Documents and Settings\Administrator>
*************************************************************************************
*************************************************************************************

Here you see that I can ping a ther server "monitor" which is on the 10.0 network by FQDN.

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator>ping monitor.transfreight.org

Pinging monitor.transfreight.org [10.0.20.241] with 32 bytes of data:

Reply from 10.0.20.241: bytes=32 time<1ms TTL=127
Reply from 10.0.20.241: bytes=32 time<1ms TTL=127
Reply from 10.0.20.241: bytes=32 time<1ms TTL=127
Reply from 10.0.20.241: bytes=32 time<1ms TTL=127

Ping statistics for 10.0.20.241:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Documents and Settings\Administrator>
*************************************************************************************
*************************************************************************************








0
 
ShannonHerbertCommented:
If I understand everything correctly: you would like to ping "monitor.transfreight.org" by the short name "monitor". To accomplish this, go into the properties of your "Local Area Connection" 165.154.67.101 NIC and add a suffix search order entry for transfreight.org.

Setps:
1. Start -> Control Panel -> Network Connections
2. Right-click "Local Area Connection" -> properties
3. Highlight "Internet Protocol (TCP/IP)" -> click Properties
4. Click "Advanced" button
5. Choose "DNS" tab
6. Choose the radial button for: "Append these DNS suffixes (in order):"
7. Click "ADD" and enter "transfreight.org" and click ADD again
8. Click "OK" 3 times and bingo.

This should do it. Let me know...
0
 
sharthunAuthor Commented:
Thanks for the tip but this does not answer the question that was originally asked which in a nutshell is:
Should the server at ip address 165.154.67.101 that is NOT part of my companies domain be able to ping "by netbios name" any other server i.e. "monitor" which is on a different vlan at ip 10.0.20.x and is part of my companies domain.
0
 
ShannonHerbertCommented:
No - the server at ip address 165.154.67.101 should not be able to ping the other server "monitor" by netbios name unless you add a host entry or configure DNS to append a suffix to the name of the server because it is a member of a domain.

The previous answer was to provide a way to get this to work if this was an issue, but I guess I read into this too far and did not realize you only wanted a yes or no answer.
0
 
sharthunAuthor Commented:
Is there a way do do something similar to your insctructions that will allow this server to see all other servers on the 10 network without adding each of the servers from the 10 network into the "append" list?
0
 
ShannonHerbertCommented:
You don't add each individual server into an append list. You add the domain suffix such as: "transfreight.org". That way each server in that domain can be referred to by netbios name. The DNS suffix of transfreight.org will be added to the name to fully qualify it.
0
 
sharthunAuthor Commented:
The server in question is 500 miles away. Will this change require a reboot to take effect.
0
 
ShannonHerbertCommented:
Not at all. This is a Dynamic change that will take affect immediately.
0

Featured Post

Restore individual SQL databases with ease

Veeam Explorer for Microsoft SQL Server delivers an easy-to-use, wizard-driven interface for restoring your databases from a backup. No expert SQL background required. Web interface provides a complete view of all available SQL databases to simplify the recovery of lost database

  • 6
  • 5
  • 3
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now