Good Luck Nick.
That's actually a good idea, let me give that a try, thanks!
Good Luck Nick.
Thats odd - I had the same thing happen on my exchange box on svr 08 this afternoon too. The only difference was mine was a physical not a virtual box. Same behavior tho - can get out of it to other devices, but not to it from others. Firewall showing as off. Attempting to shut the box down crashed it, so needed hard off (which always bothers me esp with exchange!!)
After a very long boot up and services start - it eventually came back online, but something funny is goin on....
Now that sheds some daunting light onto the situation.
We had this problem with a few of our servers a couple of weeks ago... But they were 2003.... but to solve it we uninstalled TCPIP...
Start - Run - CMD -
You may want to try this..Code:netsh int ip reset c:\resetlog.txt
In case any of you are interested, this is the response from Microsoft so far (which haven't fixed the problem) but may help some of you if you have the same problem:
Code:Please run the following commands, one at a time, from an Administrative Command Prompt: reg delete "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\StandardProfile" /f reg delete "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\DomainProfile" /f rundll32.exe setupapi,InstallHinfSection Ndi-Steelhead 132 %windir%\inf\netrass.inf netsh.exe firewall reset
This is the 2nd Email from Microsoft, also didn't help solve the problem:
Code:The network connectivity issue could also be caused by Scalable Network Pack Features (Task Offloading, Receive Side Scaling, etc). Please do the following on the server to disable the SNP features, and increase the number of available ports: 1.) Select and Copy the text in the block below: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters] "EnableWsd"=dword:00000000 "DisableTaskOffload"=dword:00000001 "DisableLargeSendOffload"=dword:00000001 "EnableTCPChimney"=dword:00000000 "EnableRSS"=dword:00000000 "EnableTCPA"=dword:00000000 "TcpTimedWaitDelay"=dword:0000001e "MaxUserPort"=dword:0000fffe "SackOpts"=dword:00000001 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters] "MaxFreeConnections"=dword:00000064 "MinFreeConnections"=dword:00000020 2.) Open Notepad (Start->All Programs->Accessories->Notepad). 3.) In Notepad, click Edit, click Paste. 4.) Click File, click Save As, type in DisableSNP.reg as the Filename, select All Files (*.*) as the File Type, select Desktop as the Destination, click Save. Exit Notepad. 5.) Double-click the DisableSNP.reg file to merge the changes and update the registry. 6.) Restart the server for the changes to take effect.
Have you tried changing the network adapter from the Hyper V one to a Legacy Network Adapter and see if that makes any difference? encase there's a problem between the driver for the NIC and the updates?
Just as an aside have you tried running a virus scan on the server? A lot of them muck around with network/firewall settings these days.
Next update from Microsoft:
Obviously I am unable to ping the NetBIOS name or IP address.Code:Have you tried to ping the NetBIOS name and the IP of the server from another computer? What is the response you get from the ping? (time-out, host cannot be found, etc) Please run netstat -ano > netstat.txt && netstat.txt from an Administrative Command Prompt, and then save and attach the text file that opens in Notepad, back to me for analysis.
I did the netstat -ano command and sent them the results.
The next update was:
1. Yes I did, F-Secure is running as AV only, not firewall, but tried anywayCode:Please also let me know the following: - Have you tried disabling F-Secure Anti-Virus and test? - When was the last time you were successfully able to ping DCSERVER-01 from another computer? - What is the output when you run net view \\DCSERVER-01 from Command Prompt on another machine?
2. Before it restarted to finish installing updates
3. The Network Path was not found.
Not that it will help much in fixing it but if you use IPv6 can you connect to the Machine? therefore isolating it to the IP stack?
There are currently 1 users browsing this thread. (0 members and 1 guests)