Can't ping remote network from Windows 2003 Domain Controller although I can ping from any other host

I just installed and Airaya wireless bridge between two networks.  The remote network is 192.168.2.0/24, the local network is 192.168.1.0/24.  The networks are connected by an openbsd box acting as a router.  Any and all hosts are pingable and are functioning from either side of the network, except the Windows 2003 Domain controller (192.168.1.3). Becuase of this the remote network has no access to windows dns services.  I can't ping the domain controller from the remote network nor can I ping the remote network from the domain controller. I am confused because the network is pingable either way from both sides of the network on any other host.

Must be some strange Windows routing set up I am not aware of.  Any ideas?
lowrycitoAsked:
Who is Participating?
 
jeffkellConnect With a Mentor Commented:
Can you ping the domain controller from the local subnet?
If yes, but you cannot ping it from the remote, check that the default gateway of the domain controller is pointing to the router.

If that doesn't do it, =ounds like the network configuration of the domain controller is incorrect.  Can you post an 'ipconfig /all' and a 'route print all' ??
0
 
Scotty_ciscoCommented:
One of the things with Service packs and windows is that they enable the firewall feature of the windows box.  They will not be pingable from a remote subnet unless the firewall is deactivated.  So if you can ping it locally and not remotely that is also something you want to look at.

Thanks
Scott
0
 
prashsaxCommented:
Try pinging the machines using there IP addresses and not by there names.

If DNs server is not accessible from remote network, there names will not be resolved to the IP address.

Now, you can try and ping those machines from Windows Server using there IP.

Also, make sure the Default gateway on the Windows Server is correctly defined. It should be the BSD box acting as router.



0
Improved Protection from Phishing Attacks

WatchGuard DNSWatch reduces malware infections by detecting and blocking malicious DNS requests, improving your ability to protect employees from phishing attacks. Learn more about our newest service included in Total Security Suite today!

 
papimichelCommented:
is it possible that the domain controller machine has 2 NIC's, and it's routing configuration isn't configured correctly ?
0
 
mbavisiCommented:
run ethereal or windump on your windows server, you will then know exactly whats going on.
0
 
scrathcyboyCommented:
Just activate RIP on the windows 2003 server.  

technet2.microsoft.com/WindowsServer/en/Library/a7a09a2c-8ec1-48fb-85f0-6363e42fd7801033.mspx
technet2.microsoft.com/windowsserver/en/operations/routera.mspx
content1.skillsoft.com/content/cm/126092_ENG/summary.htm
support.microsoft.com/?kbid=323381
vpn.shmoo.com/vpn/vpn-ipsec.html
0
 
lowrycitoAuthor Commented:
So I did a route print and noticed that there were two static routes added more than a year ago that were casuing the problem.  They had been set up for the prior network configuration. I totally forgot about this.  Thanks for the reminder to check there.
0
 
papimichelCommented:
glad i helped..
:)
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.