Nick_Parker

I've been trying to setup OCS 2007 R2, holy hell it's complicated! And all I really want from it is a basic IM server

Interesting twist... I added a 2nd network card to the VM, assigned it an IP and left my laptop pinging the IP of the new network card. No connection, just like the 1st network card and the network card in the other broken server. I'm sitting there talking to somebody when suddenly the 2nd network card starts responding the ping, nothing had happened, nothing had changed, just out of the blue, starts responding.... And then 1 minute later, it stops responding again... and about 5 minutes later, it responds again for another minutes and then stops... This keeps happening, the whole time the original network card and IP hasn't responded once.

I've tried running the VM image on another host, same issues. I'm busy creating new VMs as we speak so I can at least start the recovery process to a new VM if I can't find a solution in the next few hours.

Just tried installing the Server 2008 Service Pack 2 RC, still nothing

All the same as our other 3 host boxes

I can't remove either of them from the Domain, one of the servers is a Domain Controller and the 2nd is an Exchange Server I've tried changing it over to DHCP, it works, picks up a new address, but still isn't connectable on the new address.

Hi guys, Thanks for everyone who has been following my previous thread, http://www.edugeek.net/forums/windows-server-2008/33724-microsoft-update-kills-firewall-network.html While I still live in hope that solution will be found, if I am unable to get our Exchange Server connectable by the end of the day, I need to look at a different solution. So, quick summary: The Exchange Server works, everything runs, all the services are running, I can open Exchange Management etc etc & I can connect to the network from the Exchange Box. I CANNOT connect TO the Exchange Server from anywhere on the network (I can, however, save something to a folder on the network from the Exchange Server, and then open it on another computer, just so long as that shared folder isn't on the Exchange Server) So, bearing that in mind, how would you go about creating a new Exchange Server and exporting all the mailboxes/settings/users from the old one? Any help or suggestions would be greatly appreciated, if I'm lucky, I may be able to squeeze in a little Easter holiday somewhere

Just a quick note to say that I do appreciate everyones help and suggestions, please keep them coming!

I have checked and removed the last few updates that were installed, it seems they caused problems for other people too, but in different ways: KB960225 or KB958690 General Discussion Vista Updates KB958690 and KB960225 cause network problem - Windows Update Vista Updates KB958690 and KB960225 cause network problems However, uninstallling them and performing the steps in the above sites didn't help. I check for the an update rollup (Those have caused problem for me in the past as well!) but there hasn't been one for a while and one of the 2 servers with the problem, is a DC server, not an exchange server.

I've tried fixing the problems with the IPSec policy, the problem is I don't really know what's causing it. I'm obviously going to keep on trying tho But, as slipbye said, I have the same problem in Safe Mode AND it's only on 2 of the servers, while all the of them have the same config & setup and have been recieving the same error in the logs.

Hi Slipbye, I did run dcgopofix (yes, I'm desperate) and without any luck

Just another update to keep you all posted - I moved the VM onto another Hyper-V server, exactly the same symptoms. I also had a look at some of our other Servers and I see many of the also have the Windows Firewall Service stopped and can't be started again - it's very worrying

Thanks for your input Slipbye, If I boot it into safe mode, it's still exactly the same situation, can send but not receive, firewall won't start. Regarding if the packets are being received, how would your recommend I check that? There is an error in event logs regarding IPSec: Windows failed to apply the IP Security settings. IP Security settings might have its own log file. Please click on the "More Information" link. Although all of our servers have this in their logs and it's something we've had for months after one of the Group Policies was deleted.

2 of the VMs on the Hyper-V are the ones with the problem, the 3rd VM is still fine, and just for the sake of testing, I did a full windows update on it and rebooted it, and it's still fine...?

It's not looking good... latest reply from Microsoft:

Haha, 2 of my other servers are also waiting for a restart, I'm definately holding off until I've solved the current 2!

Not a bad idea, I'll give it a try, although I don't think the problem is anything to do with the HW, I think its a software issue, something, somewhere, has been changed when the computer last restarted. Whether or not it's a coincidence this happens to coincide with updates, I'll never know.

good suggestion k-strider, no luck tho: Pinging fe80::da1:d8bb:e899:265c%10 with 32 bytes of data: PING: transmit failed, error code 1231. PING: transmit failed, error code 1231. PING: transmit failed, error code 1231. PING: transmit failed, error code 1231. Ping statistics for fe80::da1:d8bb:e899:265c%10: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)

Next update from Microsoft: 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. Obviously I am unable to ping the NetBIOS name or IP address. I did the netstat -ano command and sent them the results. The next update was: 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? 1. Yes I did, F-Secure is running as AV only, not firewall, but tried anyway 2. Before it restarted to finish installing updates 3. The Network Path was not found.

thanks flyinghaggis, I've got F-Secure running on it and it's up to date, I also did a conficker test when this started. Is there any others you would recommend testing for?

Thanks k-strider, I've tried removing the adapters, adding new ones, both legacy and the standard, same thing

This is the 2nd Email from Microsoft, also didn't help solve the problem: 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.

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: 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

Thanks Linkazoid, I gave it a try, still the same problem tho

Thanks for the suggestion, I've tried rebooting and shutting down the Virtual Servers, as well as the Host Server