Server cannot ping another server - DNS?

[fruitloopy]

This is a bit of an unusual problem. I'm not too bad with networking but this has me stumped!

Here's the story:

The accounts dept moved out of the head office to a new office. A new server was bought, mostly to host a Sage database but also for future needs.
This was installed with Windows 2003 Server as a domain controller on the same domain. I set it up originally to connect to the domain controller in the head office via VPN for synchronisation.
This all seemed to work ok.

A few weeks ago I persuaded the boss to let me buy 2 VPN routers (Draytek Vigor) to establish a LAN to LAN VPN connection between accounts and head office via broadband.
These were bought, installed, setup and VPN established no probs.

The problem:

The accounts domain controller cannot ping the head office domain controller. It can ping every other PC on the head office network except for the DC.

The Accounts PC's can happily ping the domain controller plus any other PC in the head office over the VPN link.

So what the hell has happened? I have gone through the DNS entries and it did have an old entry for an IP address it gained when it used a VPN dialup but I deleted that. Its even been rebooted since then.

I cannot ping by name or by IP but a PC on the same network can happily ping by name and IP.

Any help?

Head office Network
192.168.1.x
255.255.255.0

Accounts network
192.168.10.x
255.255.255.0

Thanks.

Edit...since typing this I tried a TRACERT. The first traced the route from the accounts server to a PC in the head office.
Result:
Tracing route to WST01 [192.168.1.36]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.10.254 (DG of local subnet)
2 47 ms 46 ms 47 ms 192.168.1.254 (DG of remote subnet)
3 48 ms 46 ms 48 ms echoketsrv01 [192.168.1.36]

Trace complete.

Do a trace route to the head office DC:
Tracing route to dcsrv01 [192.168.1.2]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.10.254
2 47 ms 46 ms 47 ms 192.168.1.254
3 * * * Request timed out
4 * * * Request timed out

This carried on to the max 30 hops with the same result.

 

[cajuntank]

DO yo by chance have more than one NIC on those servers?

 

[fruitloopy]

I know what you were thinking but no, it only has 1 NIC installed.

I should also state that there is no firewall on either of the servers.

Thanks for reply.

 

[lpblauen]

make sure the firewall if off. or set to allow ping...

 

[fruitloopy]

There is no firewall involved, on either of the servers

 

[kmcferrin]

How do the routing tables on the DCs look? If you had previously configured a VPN connection on the Accounts DC to use a tunnel when connecting to the head office DC it may still be trying to use a tunnel that doesn't exist rather than the new VPN router device.

Try a ROUTE PRINT and see what comes up.

________________________________________
CompTIA A+, Network+, Server+, Security+
MCTS:Windows 7
MCSE:Security 2003
MCITP:Server Administrator
MCITP:Enterprise Administrator
MCITP:Virtualization Administrator 2008 R2
Certified Quest vWorkspace Administrator

 

[fruitloopy]

Here are the route tables for both servers:

Route Table from DC

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.254 192.168.1.2 25
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
192.168.1.0 255.255.255.0 On-link 192.168.1.2 276
192.168.1.2 255.255.255.255 On-link 192.168.1.2 276
192.168.1.35 255.255.255.255 192.168.1.35 192.168.1.47 28
192.168.1.37 255.255.255.255 192.168.1.37 192.168.1.47 28
192.168.1.40 255.255.255.255 192.168.1.40 192.168.1.47 28
192.168.1.47 255.255.255.255 On-link 192.168.1.47 283
192.168.1.255 255.255.255.255 On-link 192.168.1.2 276
224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 192.168.1.2 276
224.0.0.0 240.0.0.0 On-link 192.168.1.47 283
255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
255.255.255.255 255.255.255.255 On-link 192.168.1.2 276
255.255.255.255 255.255.255.255 On-link 192.168.1.47 283
===========================================================================
Persistent Routes:
Network Address Netmask Gateway Address Metric
0.0.0.0 0.0.0.0 192.168.1.254 5
===========================================================================

IPv6 Route Table
===========================================================================
Active Routes:
If Metric Network Destination Gateway
1 306 ::1/128 On-link
10 276 fe80::/64 On-link
10 276 fe80::7412:2de1:2062:6223/128
On-link
10 276 fe80::e889:7833:b963:c32b/128
On-link
1 306 ff00::/8 On-link
10 276 ff00::/8 On-link
===========================================================================
Persistent Routes:
None




Route table from Accounts Server:

IPv4 Route Table
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x10003 ...1c c1 de fa 4b 7b ...... HP NC107i PCIe Gigabit Server Adapter
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.10.254 192.168.10.1 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.1 192.168.10.1 20
192.168.10.1 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.10.255 255.255.255.255 192.168.10.1 192.168.10.1 20
224.0.0.0 240.0.0.0 192.168.10.1 192.168.10.1 20
255.255.255.255 255.255.255.255 192.168.10.1 192.168.10.1 1
Default Gateway: 192.168.10.254
===========================================================================
Persistent Routes:
None