So I got message_topic.aspx?topic=568736 issue done. Works great. Now have a problem with the network I bridged it to on the new link.Its server 2k8, setup as in an AD environ as the DC, DNS, WINS, RAS, and a few other things server. Its got the main network port when I ping out of it reporting a general failure. Google reports this is a bad NIC. a loopback ping works fine, diagnostics report a DNS server failure. Port shows up/up. No traffic that I can tell is passed. Because this is a virtual port (VMWare) and i tested the network on another VM with no failure/issue its a config problem somewhere. Also google reported firewall issue. Ive no 3rd party stuff on it. windows firewall on is it. Network works fine if its on a different port/network. Im at a loss. Its just this port/network thats having issues. aldo flipped it to dhcp, same problem. id rather not start messing in vmware network config and flip all the ports/networks around. so effectively ive a complete network block on one port and one port only caused by a config issue somewhere.
6/17/2009 9:55:13 AM
6/17/2009 10:30:25 AM
Then why would it work on one network but not another. RAS is only enabled, not configured. And I know what you are talking about, its off (static packet filter), as if it was on, everything would be blocked. Ill disable it and report back just to be sure. Also, I know yesterday when this first poped up, it shut down the WINS DNS and AD services. Hasnt as I set up a secondary interface thats NATd to a different network. For a correction, WINS, AD, and DNS are the really only configured things.Also I checked, it works great in safe mode, so its not a VMWare issue.
6/17/2009 11:54:29 AM
Evan, you were right. It was RRAS. I dont know if it was the static packet filter or what. I just wiped the whole feature and the system came back up fine. Thx!
6/17/2009 1:18:30 PM