We have two subnets 192.168.0.x and 192.168.1.x sonicwall internalip 192.168.0.1 cisco internal ip 192.168.1.1 both routers are bridge and have given x3 interface of sonicwall 192.168.1.254 and i can see and reach server on 1.x subnet and vice versa Except two servers 1.60 and 1.63 they can't able to ping or reach x3 interface on sonicwall... both servers are running windows server 2008 r2 and i have disabled firewall to thinking about thats the problem preventing them to see or reach 0.x subnet now everyother servers on 1.x is fine and can see and reach 0.x subnet servers except these two servers.. both server have same configuration as other servers on 1.x subnet... both have same gateway 192.168.1.1 (cisco) can't think of anything else

from the server type route print and post your outputDarshana Jayathilake

from the server type route print and post your outputDarshana Jayathilake

from the server type route print and post your outputDarshana Jayathilake

Thank You for your quick response Here is the output that you requested C:\Users\Administrator>route print =========================================================================== Interface List 14...00 00 00 00 00 01 ......Microsoft Virtual Machine Bus Network Adapter #2 1...........................Software Loopback Interface 1 12...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter 13...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface =========================================================================== IPv4 Route Table =========================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.60 261 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.60 261 192.168.1.60 255.255.255.255 On-link 192.168.1.60 261 192.168.1.255 255.255.255.255 On-link 192.168.1.60 261 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.60 261 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.60 261 =========================================================================== Persistent Routes: Network Address Netmask Gateway Address Metric 0.0.0.0 0.0.0.0 192.168.0.1 Default 0.0.0.0 0.0.0.0 192.168.1.1 Default =========================================================================== IPv6 Route Table =========================================================================== Active Routes: If Metric Network Destination Gateway 13 58 ::/0 On-link 1 306 ::1/128 On-link 13 58 2001::/32 On-link 13 306 2001:0:4137:9e76:2815:a64:3f57:fec3/128 On-link 14 261 fe80::/64 On-link 13 306 fe80::/64 On-link 14 261 fe80::11c1:4550:efe1:7452/128 On-link 13 306 fe80::2815:a64:3f57:fec3/128 On-link 1 306 ff00::/8 On-link 13 306 ff00::/8 On-link 14 261 ff00::/8 On-link =========================================================================== Persistent Routes: None

Thank You for your quick response Here is the output that you requested C:\Users\Administrator>route print =========================================================================== Interface List 14...00 00 00 00 00 01 ......Microsoft Virtual Machine Bus Network Adapter #2 1...........................Software Loopback Interface 1 12...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter 13...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface =========================================================================== IPv4 Route Table =========================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.60 261 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.60 261 192.168.1.60 255.255.255.255 On-link 192.168.1.60 261 192.168.1.255 255.255.255.255 On-link 192.168.1.60 261 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.60 261 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.60 261 =========================================================================== Persistent Routes: Network Address Netmask Gateway Address Metric 0.0.0.0 0.0.0.0 192.168.0.1 Default 0.0.0.0 0.0.0.0 192.168.1.1 Default =========================================================================== IPv6 Route Table =========================================================================== Active Routes: If Metric Network Destination Gateway 13 58 ::/0 On-link 1 306 ::1/128 On-link 13 58 2001::/32 On-link 13 306 2001:0:4137:9e76:2815:a64:3f57:fec3/128 On-link 14 261 fe80::/64 On-link 13 306 fe80::/64 On-link 14 261 fe80::11c1:4550:efe1:7452/128 On-link 13 306 fe80::2815:a64:3f57:fec3/128 On-link 1 306 ff00::/8 On-link 13 306 ff00::/8 On-link 14 261 ff00::/8 On-link =========================================================================== Persistent Routes: None

Thank You for your quick response Here is the output that you requested C:\Users\Administrator>route print =========================================================================== Interface List 14...00 00 00 00 00 01 ......Microsoft Virtual Machine Bus Network Adapter #2 1...........................Software Loopback Interface 1 12...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter 13...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface =========================================================================== IPv4 Route Table =========================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.60 261 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.60 261 192.168.1.60 255.255.255.255 On-link 192.168.1.60 261 192.168.1.255 255.255.255.255 On-link 192.168.1.60 261 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.60 261 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.60 261 =========================================================================== Persistent Routes: Network Address Netmask Gateway Address Metric 0.0.0.0 0.0.0.0 192.168.0.1 Default 0.0.0.0 0.0.0.0 192.168.1.1 Default =========================================================================== IPv6 Route Table =========================================================================== Active Routes: If Metric Network Destination Gateway 13 58 ::/0 On-link 1 306 ::1/128 On-link 13 58 2001::/32 On-link 13 306 2001:0:4137:9e76:2815:a64:3f57:fec3/128 On-link 14 261 fe80::/64 On-link 13 306 fe80::/64 On-link 14 261 fe80::11c1:4550:efe1:7452/128 On-link 13 306 fe80::2815:a64:3f57:fec3/128 On-link 1 306 ff00::/8 On-link 13 306 ff00::/8 On-link 14 261 ff00::/8 On-link =========================================================================== Persistent Routes: None

1.as youre not using ipv6 you can disalble ipv6 2.delete routing table using route -f 3.restart the server. 4.check the ipconfiguraiton(correct gateway) Darshana Jayathilake

I tried that but yet no success strange thing is i can see that arp entry but can't ping it both zone have different router as i mentioned 0.x has sonicwall and 1.x has cisco 871 i can ping through sonicwall from 0.x to 1.x other servers except this 1.60 vice versa

1.as youre not using ipv6 you can disalble ipv6 2.delete routing table using route -f 3.restart the server. 4.check the ipconfiguraiton(correct gateway) Darshana Jayathilake

Hi Shivang, Thank you for your post. As you configure server ip manually. please first check the hardware connectivity: replace new network cable and change server connected router/switch port. Afterwards, please do troubleshooting steps below on server 192.168.1.60: 1.Run "ipconfig /all" command, post its result to us. 2.Test ping 192.168.1.1, ping one computer in 1.x, ping one computer in 0.x. 3.Test tracert one computer in 1.x, tracert one computer in 0.x. If there are more inquiries on this issue, please feel free to let us know. Regards, Rick Tan

Hi Shivang, Thank you for your post. As you configure server ip manually. please first check the hardware connectivity: replace new network cable and change server connected router/switch port. Afterwards, please do troubleshooting steps below on server 192.168.1.60: 1.Run "ipconfig /all" command, post its result to us. 2.Test ping 192.168.1.1, ping one computer in 1.x, ping one computer in 0.x. 3.Test tracert one computer in 1.x, tracert one computer in 0.x. If there are more inquiries on this issue, please feel free to let us know. Regards, Rick Tan

Thank You everyone for your help guys... The problem was mac addresses of that vms....it was on static by the previous IT guy, IT was lil wierd MAC Address given by him all Zeros except the last digit...anyhow thats the reason sonicwall was not accepting anything from an unknown MAC Address or something but put that mac address from static to dynamic on vm host.... Solved my Problem Thank You once again all of your kind replies to help me out