8 reputation
4
bio website
location
age 34
visits member for 2 years, 1 month
seen Nov 6 '13 at 17:26

May
14
comment Internet Explorer issues with wpad.dat
I have the "Automatic configuration script" setting enabled and set correctly and have verified that my machine is pulling down the wpad.dat file using Wireshark. However if the first condition in the wpad.dat file is not met then it doesn't bother checking for anything else it needs to for the site.
May
14
asked Internet Explorer issues with wpad.dat
Sep
17
awarded  Scholar
Sep
17
accepted Weird routing issue
Sep
17
comment Weird routing issue
I wiped out the routing table using route -f (really hard for me to re-configure the VM, my user doesn't have permission to), then rebuilt it starting on the Admin network and its persistent routes. Then I added the default gateway to the production network and it works great now. Thanks for your help.
Sep
15
awarded  Commentator
Sep
15
awarded  Student
Sep
14
comment Weird routing issue
Firewall is completely disabled on the servers (no Internet access). The 3 VMs cannot talk to each other, even with the production NICs disabled. Also, the ESXi server is 172.28.56.210 and I can access it just fine. So traffic is able to get to the ESXi host. And I am seeing traffic hit the administrative interface in Wireshark. I just cannot get traffic to go out over the network unless it came in on that network and I didn't specify it.
Sep
14
comment Weird routing issue
August, Cannot vMotion the VMs, my user does not have permission for that. I have compared the vSwitch mappings on a working and non-working VM, same. I have also looked at the uplinks between a host w/ working VMs and the one not working, they are the same. I don't have physical access to the systems, nor can my user make any major changes (power on & off VMs & mount ISOs is all I can do).
Sep
14
comment Weird routing issue
According to Wireshark, I have traffic going across the administrative interface on the non-working servers. But I cannot connect to them VIA RDP, or ping them. I cannot ping between the 3 VMs on the same host, and they all stopped responding at around the same time.
Sep
14
comment Weird routing issue
i tried disabling the production nic on one of the servers & setting a default gw on the admin again, still cannot ping anything (even the esxi host)
Sep
14
comment Weird routing issue
i tried disabling the production nic on one of the servers & setting a default gw on the admin again, still cannot ping anything (even the esxi host)
Sep
14
comment Weird routing issue
Just removed that. Still the same issue. Basically, all traffic is attempting to go out over 172.28.58.0 no matter what.
Sep
14
comment Weird routing issue
Just tried that, no change. Also, all non-working servers are on the same ESXi host. They cannot ping each other as well. Could it be the v-switch?
Sep
14
awarded  Editor
Sep
14
comment Weird routing issue
op edited, at end.
Sep
14
revised Weird routing issue
added 6062 characters in body
Sep
14
asked Weird routing issue