I have a single server domain we use as our CRM server - running Server 2008 r2 SP1, SQL Server and coldfusion web sites. This acts as local DNS and domain controller, and runs active directory. Last night I realised it was invisible from the internet due to an error on the IPv4 setting on the NIC - the Defaul gateway was missing. The static IP settings were correct, but I was unable to save the default gateway successfully. Everytime the setting would be blanked on save, or in some circumstances a few seconds later. I followed various threads to correct this but none of them worked. I edited registry entries, ran netsh int ip reset c:\resetlog.txt. Then tried netsh winsock reset to restore winsock having determined the IPv4 entries were missing. This resulted in the server coming up but I can no longer log on as the server gives the error: "the security database on the server does not have a computer account for this workstation trust relationship". Tricky since the security database only exists on the server I am trying to log on to as the administrator... I can log on in Safe Mode, but dont know how to restore the OS - and under safe mode I still cannot reset the default gateway in the IPv4 settings for the network card. Any suggestions welcomed! Thanks.

Hi, Do you have more than one NIC on this server? Have you configure the NIC teaming on this server? If not, please try to use netsh command line to add the default gateway. Netsh interface ipv4 set address name=InterfaceName static addr=IPAddress mask=SubnetMask gateway=IPAddress If still no luck, please try to reset TCP/IP. How to reset Internet Protocol (TCP/IP) http://support.microsoft.com/kb/299357 Netsh commands for Interface IP http://technet.microsoft.com/en-us/library/cc738592(v=ws.10).aspx Best Regards, AidenAiden Cao TechNet Community Support

Hi, Do you have more than one NIC on this server? Have you configure the NIC teaming on this server? If not, please try to use netsh command line to add the default gateway. Netsh interface ipv4 set address name=InterfaceName static addr=IPAddress mask=SubnetMask gateway=IPAddress If still no luck, please try to reset TCP/IP. How to reset Internet Protocol (TCP/IP) http://support.microsoft.com/kb/299357 Netsh commands for Interface IP http://technet.microsoft.com/en-us/library/cc738592(v=ws.10).aspx Best Regards, AidenAiden Cao TechNet Community Support

1. I am very curious about the output from ipconfig /all 2. I would appreciate full info on your error. You have given fragment only. 3. Depending on detailed iinformation there are possible solutions here http://support.microsoft.com/kb/976494/en-us http://technet.microsoft.com/en-us/library/ee849847(v=ws.10).aspx http://www.kozeniauskas.com/itblog/2011/02/18/error-the-security-database-on-the-server-does-not-have-a-computer-account-for-this-workstation-trust-relationship/ http://virtualcurtis.wordpress.com/2011/03/02/fix-the-security-database-on-the-server-does-not-have-a-computer-account-for-this-workstation-trust-relationship/ http://blog.skybyte.com/blog/network-helpdesk/the-security-database-on-the-server-does-not-have-a-computer-account-for-this-workstation-trust-relationship-microsoft-server-support http://clintboessen.blogspot.cz/2011/06/security-database-on-server-does-not.html Regards milos

Hi In certain cases you can "re-add" your machine to domain to quick reslove problem, not cause of problem. User settings and profiles will stay unchanged. For fixing IP configuration problem I used before Winsock Fix. You can find it on Winsock Fix Website Best regards Dubravko Marak MCP Blog: Windows Server Administration Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Thanks for your comments - unfortunately we ran out of time over the weekend so I rebuilt from scratch, as I could not get into the machine other than under safe mode. The issue is now resolved. Interesting that the winsock issue was the cause of losing the machine from the domain however. that is one fix I would certainly not try again lightly! The gateway error turned out to be a conflict as i later found out -t he gateway I had been given was incorrectly written down (our server IP was 10.156.254.245, the gateway should have been 10.156.254.254 - an unfortunate reversal of the last 2 digits of the gateway meant I wasted an entire weekend trying to point the server NIC to itself as the gateway...