Saturday, November 17, 2012 1:19 AM
Hi to all,
I've got a problem within my DC server. My DC server is running in VMWARE esxi. Both my DC and it's backup DC are in VMWARE. My problem is my main DC which is running under Windows SERVER 2008 can't ping other pc's or routers in other subnets, but my backup DC running under server 2003 r2 can ping pc's and router in other subnet. Windows Firewall is disabled in server 2008. The router can ping the ip address of my main DC but DC cant ping that router. DC can only ping pc's and router which belong in his subnet.
Any help will be appreciated. Thank You.
Saturday, November 17, 2012 4:14 AMDefault gateway set in the NIC's configuration ? and correct subnet's mask set ?
- Edited by Yagmoth555 Saturday, November 17, 2012 4:15 AM
Saturday, November 17, 2012 6:52 AM
yes.. the configuration of my main DC and backup DC have the same mask and gateway config but how come my backup DC can ping pc and router in other subnet while my main DC can't.
main DC (W2k8)-can't ping pc and router in other subnets. only with the same subnet
backup DC (W2k3r2)-can ping pc and router in other subnets/vlan
- Edited by irwin29 Saturday, November 17, 2012 7:00 AM
Sunday, November 18, 2012 3:40 AM
Sunday, November 18, 2012 4:10 AM
Are you pinging IP addersses, FQDN's or NetBIOS names?
Are both DC's connected to the same switch?
Are both DC's on the same VLAN ID/Group?
Have you tried a Trace Route?
- Edited by Miguel FraMicrosoft Community Contributor Sunday, November 18, 2012 4:13 AM
Sunday, November 18, 2012 6:22 AM
thanks for the reply. ok i'll try to run wireshark but i can ping the ip add of the DC using my router in other subnet but DC cant ping that router.
im pinging the ip address of the DC from router or from DC to router. my DC's are in a single virtual box. Yes both DC's are on the same VLAN/Switch since it's in a single virtual box.
Tuesday, November 20, 2012 5:41 AMModerator
Please go through below thread for more assistance:
Windows Server is unable to ping the other DC Windows 2008 Server.
TechNet Community Support
Wednesday, November 21, 2012 1:06 PM
Incorect network configuration
Your configuration is 192.168.1.0 /24 ( 255.255.255.0) and the ip adresses allowed in this subnet are : 192.168.1.0-192.168.1.255 ( class C ip adress) and you get only one subnet no matter what subnet mask you use.
If you you want multiple subnets without having to route them you should use a diffrent ipadress class like B or A .
In a B class for example for 172.16.0.0 /24 (255.255.255.0) ip adresses allowes in this subnet are 172.16.0.0-172.16.0.254 , but if you change the subnet mask to 255.255.240.0 ( /20 ) you get 172.16.0.1 - 172.16.15.254 ( 16 subnets ).
Hope it helps!
Monday, November 26, 2012 12:50 AM
Thanks for reply. I'm aware of ip subnetting. As you can see in my older post that only my main DC (W2k8) can't ping that router. My Backup DC and all pc's under 192.168.1.0 subnet can ping router which is 192.168.100.1 and also that router can ping my main DC but can't ping back
Monday, November 26, 2012 1:56 AMWell i've noticed I had another W2k8 server (192.168.1.1) can ping that router. But in IPV4 connection status, they have diff status. In main DC IPV4 connection status is LOCAL ONLY while in another W2k8 server (192.168.1.1) status is NO INTERNET CONNECTION. I understand the no internet conn status but the IPV4 conn status of DC is the prob? I think LOCAL ONLY status is the issue? can i change it?
Monday, November 26, 2012 2:38 AM
ok now i've got this problem solved with the other forums
i manually enter the def gw in LAN properties but when i enter ipconfig i saw in default gw:0.0.0.0 then 192.168.1.251. the solution is to delete the route by entering route delete 0.0.0.0 in command prompt then manually enter the def gw ip add again. problem solved and i can ping the other subnets!!
thank you for all the people who helped.
- Marked As Answer by irwin29 Monday, November 26, 2012 2:38 AM