Time to bring in the experts, I'm stumped. I have a windows 2012 R2 server on VMware 5.1.0 with a SonicWALL NSA4500. On the SonicWALL we have and internal and DMZ network, same with the vCenter 5.1.0 The 2012 server was built on the internal network with an IP of 172.16.1.79. The server is supposed to replace an old 2003 server in the DMZ. When on the internal network it pings fine and behaves normally. I shut down the 2003 server in the DMZ (it pings, gets out to the net and does a normal arp -a) and duplicate the IP it uses 172.31.0.3 on the 2012 server. On the VMware side I switch the network from INT to DMZ. I can ping the server OK, get out to the net and do a normal arp -a, but the Websphere app it runs doesn't behave as expected. If I do an arp -a on the 2012 or 2003 server it shows the default gateway 172.31.0.1
So I want to put it up on another IP in the DMZ and run the 2 servers in parallel. I duplicate the SonicWALL rules and bring it up on IP 172.31.0.6. I can't ping or get out to the net. I try an arp -a and have no have default gateway. Monitor sniffs from the SonicWALL show no traffic. OK I think I messed up the rules. I bring down another server using IP 172.31.0.4 in the DMZ which can ping, do an arp -a and get out to the net on. I assign the same IP 172.31.0.4 to the 2012 server and I still get no connectivity. It only works if I bring it up on 172.31.0.3. I flushed the arp cache on the SonicWALL each time I changed IP's. What could be configed in the network on the 2012 server which could cause this behavior? It works on the internal side 172.16.1.79 (or any other internal IP) or with a 172.31.0.3 address in the DMZ but no other DMZ IP will work on the 2012 server. Scott Schneider Senior Network and System Administrator Inscape T 905 952 4001 | C 705 716 4540 | Skype sschnei...@inscapesolutions.com<mailto:sschnei...@inscapesolutions.com> inscapesolutions.com
