DNS issues between 2 offices; please help!

R

RavinDJ

Supreme [H]ardness
Joined
Apr 9, 2002
Messages
4,450
I was asked to help out on 2 offices... here are the specs:

office 1: NetVanta 3305 @ 192.168.10.100 with all workstations @ 192.168.10.xxx

office 2: NetVanta 3305 @ 192.168.1.1 with all workstations @ 192.168.1.xxx

There's a direct point to point b/w the two offices using a T1. There are two servers in office 1:

192.168.10.1 (domain controller)
192.168.10.250 (data server)

From office 2 (192.168.1.xxx) I can connect and ping 192.168.10.250 but I cannot connect or pint 192.168.10.1

Any ideas???
 
Wondering if on that router..the default LAN interface is somehow left on or with some rules...I see you changed it to .100...but was it defaulting to .1 on that IP range, and perhaps some rules left. Although I've held a NetVanta in my hands...have not actually worked on one...just scratching my head.
 
YeOldeStonecat said:
Wondering if on that router..the default LAN interface is somehow left on or with some rules...I see you changed it to .100...but was it defaulting to .1 on that IP range, and perhaps some rules left. Although I've held a NetVanta in my hands...have not actually worked on one...just scratching my head.
Click to expand...

It's extremely frustrating... I didn't even set up the NetVanta, but the IT company that installed it couldn' tuse 192.168.10.1 b/c that's the IP address of the server.

I don't get it... from 192.168.1.150 (created by DHCP), I can ping 192.168.1.250 (win2003 server), I can ping 192.168.1.35 (a WinXP Pro workstation), I can remote desktop into both of those, but I cannot ping or RD into 192.168.10.1 (Win2000 Server)... argh... I tried to google:

windows 2000 server joining domain from another subnet
windows 2000 server different subnet
etc.

Hours of research spent and nothing good to show for it... argh :( :( :eek:
 
Sounds like a routing issue.

Normally the Netvantas should handle routing between the subnets, however I have seen instances where static routes were added to machines for the other subnets.

Check the Netvantas for any routing rules that may be setup and post an "IPconfig /all" and "route print" from both servers and a workstation on the 192.168.1.x subnet.
 
SJConsultant said:
Sounds like a routing issue.

Normally the Netvantas should handle routing between the subnets, however I have seen instances where static routes were added to machines for the other subnets.

Check the Netvantas for any routing rules that may be setup and post an "IPconfig /all" and "route print" from both servers and a workstation on the 192.168.1.x subnet.
Click to expand...

I swear... this is the biggest mess I've seen in a very long time. Whoever did all this crap should be forced to fix this...

Code: 
================================
WINDOWS 2000 SERVER ON 192.168.10.1
================================

Windows 2000 IP Configuration

        Host Name . . . . . . . . . . . . : medicware
        Primary DNS Suffix  . . . . . . . : bartnic.med
        Node Type . . . . . . . . . . . . : Hybrid
        IP Routing Enabled. . . . . . . . : Yes
        WINS Proxy Enabled. . . . . . . . : No
        DNS Suffix Search List. . . . . . : bartnic.med

Ethernet adapter Internal Area Network:

        Connection-specific DNS Suffix  . : bartnic.med
        Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
        Physical Address. . . . . . . . . : 00-0c-9F-AA-2B-87
        DHCP Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : 192.168.10.1
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . :
        DNS Servers . . . . . . . . . . . : 127.0.0.1
        Primary WINS Server . . . . . . . : 192.168.10.1

Ethernet adapter Covad Area Network:

        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : Intel(R) PRO/100 S Server Adapter
        Physical Address. . . . . . . . . : 00-0c-B3-AD-28-D6
        DHCP Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : 192.168.0.220
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.0.1
        DNS Servers . . . . . . . . . . . : 127.0.0.1
        NetBIOS over Tcpip. . . . . . . . : Disabled

===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 0C 9F AA 2B 87 ...... Intel(R) PRO/1000 MT Network Connection (Microsoft's Packet Scheduler)
0x3 ...00 0C B3 AD 28 D6 ...... Intel(R) PRO/100 S Server Adapter (Microsoft's Packet Scheduler)
===========================================================================
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.0.1   192.168.0.220       1
    xx.xx.xxx.xxx  255.255.255.255      192.168.0.1   192.168.0.220       1
        127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1       1
      192.168.0.0    255.255.255.0    192.168.0.220   192.168.0.220       1
    192.168.0.220  255.255.255.255        127.0.0.1       127.0.0.1       1
    192.168.0.255  255.255.255.255    192.168.0.220   192.168.0.220       1
     192.168.10.0    255.255.255.0     192.168.10.1    192.168.10.1       1
     192.168.10.1  255.255.255.255        127.0.0.1       127.0.0.1       1
   192.168.10.255  255.255.255.255     192.168.10.1    192.168.10.1       1
        224.0.0.0        224.0.0.0    192.168.0.220   192.168.0.220       1
        224.0.0.0        224.0.0.0     192.168.10.1    192.168.10.1       1
  255.255.255.255  255.255.255.255     192.168.10.1    192.168.10.1       1
Default Gateway:       192.168.0.1
===========================================================================
Persistent Routes:
  None

=====================================
WINDOWS 2003 SERVER ON 192.168.10.250
=====================================

Windows IP Configuration

   Host Name . . . . . . . . . . . . : ADS-SERVER
   Primary Dns Suffix  . . . . . . . : bartnic
   Node Type . . . . . . . . . . . . : Broadcast
   IP Routing Enabled. . . . . . . . : Yes
   WINS Proxy Enabled. . . . . . . . : Yes
   DNS Suffix Search List. . . . . . : bartnic

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
   Physical Address. . . . . . . . . : 00-18-8A-46-86-3D
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : 192.168.10.250
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.10.100
   DNS Servers . . . . . . . . . . . : 192.168.10.1


===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x10003 ...00 18 8A 46 86 3D ...... Broadcom NetXtreme Gigabit Ethernet
===========================================================================
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0   192.168.10.100   192.168.10.250     10
        127.0.0.0        255.0.0.0        127.0.0.1        127.0.0.1      1
     192.168.10.0    255.255.255.0   192.168.10.250   192.168.10.250     10
   192.168.10.250  255.255.255.255        127.0.0.1        127.0.0.1     10
   192.168.10.255  255.255.255.255   192.168.10.250   192.168.10.250     10
        224.0.0.0        240.0.0.0   192.168.10.250   192.168.10.250     10
  255.255.255.255  255.255.255.255   192.168.10.250   192.168.10.250      1
Default Gateway:    192.168.10.100
===========================================================================
Persistent Routes:
  None


===========================
WORKSTATION @ 192.168.10.35
===========================

Windows IP Configuration

        Host Name . . . . . . . . . . . . : MNGR
        Primary Dns Suffix  . . . . . . . : bartnic
        Node Type . . . . . . . . . . . . : Hybrid
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No
        DNS Suffix Search List. . . . . . : bartnic
                                            bartnic.med

Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix  . : bartnic.med
        Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connection
        Physical Address. . . . . . . . . : 00-82-3F-AB-AB-EC
        Dhcp Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : 192.168.10.35
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.10.100
        DNS Servers . . . . . . . . . . . : 192.168.10.1
                                            xx.xxx.xxx.xxx


===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x20002 ...00 82 3F AB AB EC ...... Intel(R) PRO/100 VE Network Connection
===========================================================================
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0   192.168.10.100   192.168.10.35       20
        127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1       1
     192.168.10.0    255.255.255.0    192.168.10.35   192.168.10.35       20
    192.168.10.35  255.255.255.255        127.0.0.1       127.0.0.1       20
   192.168.10.255  255.255.255.255    192.168.10.35   192.168.10.35       20
        224.0.0.0        240.0.0.0    192.168.10.35   192.168.10.35       20
  255.255.255.255  255.255.255.255    192.168.10.35   192.168.10.35       1
Default Gateway:    192.168.10.100
===========================================================================
Persistent Routes:
  None

I did some xxx'ing out of the public ip address and dns (just for security, i guess).
 
Some of the basic things I found:

Code: 
        Default Gateway . . . . . . . . . :

Why is it blank? When I go to network connection > connection > tcp/ip > advanced, the DEFAULT GATEWAY is listed there as 192.168.10.100

Why is the DNS SUFFIX SEARCH LIST sometimes bartnic and sometimes bartnic.med? Geez...
 
do you have two NIC in that W2K server? looks like you do and two DFG set. You can't do that. You can probably set the DFG metric on both interfaces but I would just remove the DFG from the Covad NIC.
 
Why is the network setup in that network traffic flows "through" the DC to the Netvanta to the other Netvanta?

Can you provide a diagram of the physical network connections?
 
oakfan52 said:
do you have two NIC in that W2K server? looks like you do and two DFG set. You can't do that. You can probably set the DFG metric on both interfaces but I would just remove the DFG from the Covad NIC.
Click to expand...

I'll try to do it tonight when everyone's out of the office... I'll let you know what's up with that... the Covad one is used so that people can Remote Desktop into the server.

SJConsultant said:
Why is the network setup in that network traffic flows "through" the DC to the Netvanta to the other Netvanta?

Can you provide a diagram of the physical network connections?
Click to expand...

I don't know why it was set up that way... to be quite honest, the company had a fall-out with their last IT guy (either he didn't know what he was doing or he did it on purpose). Either way... everything works fine for them, but they would like to optimize everything and get things straightened out...

I didn't even look to see that teh traffic flows 'through' the DC... hmmm...
 
RavinDJ said:
I'll try to do it tonight when everyone's out of the office... I'll let you know what's up with that... the Covad one is used so that people can Remote Desktop into the server.



I don't know why it was set up that way... to be quite honest, the company had a fall-out with their last IT guy (either he didn't know what he was doing or he did it on purpose). Either way... everything works fine for them, but they would like to optimize everything and get things straightened out...

I didn't even look to see that teh traffic flows 'through' the DC... hmmm...
Click to expand...

I didn't relize you were using the DC as a router. In that case the LAN Nic should have DFG removed.
 
It's a bit hazy overall going by the ipconfig, routing tables, and previous configs posted.

What would really help is a topology diagram of the servers, workstations, T1, and any internet connections showing the IP addy, subnet, and default gateway on each device.
 
Thanks for the help, SJConsultant!

I'll finish a Visio design tonite and will post it ASAP. In the meantime, I'll let some other people get some help from everyone... and, as always... I'll try to help anyone that has a question that I can actually answer.

I do appreciate your help, though. For now, it's Saturday night and I need a break from this.

What do you guys do on a Fri/Sat nite???
 
RavinDJ said:
Thanks for the help, SJConsultant!

I'll finish a Visio design tonite and will post it ASAP. In the meantime, I'll let some other people get some help from everyone... and, as always... I'll try to help anyone that has a question that I can actually answer.

I do appreciate your help, though. For now, it's Saturday night and I need a break from this.

What do you guys do on a Fri/Sat nite???
Click to expand...


Browse [H] obviously :D
 
You need to add a persistent static route for the 192.168.1.0 subnet with a mask of 255.255.255.0 using 192.168.10.100 as the gateway; on the server with IP address 192.168.10.1. Should straighten everything out. That will make all the traffic for your other internal network go out the adapter with the IP address 192.168.10.1. Right now, it is trying to use your Covad connection to send traffic to that location.

The following at the command line should do it:

route add 192.168.1.0 mask 255.255.255.0 192.168.10.100 metric 1 -p

You could run it without the "-p" to test. The "-p" makes the route survive reboots.
 
You must log in or register to reply here.
Back
Top