Our Windows 2008 64 server network locks up over time. If we reboot the server the network works fine for about a day, then if we go on the server and try to connect externally to the server (local Lan or Internet) it says we have a network issue and runs a network check and fix wizard which end up saying that the issue cannot be corrected. The interesting part to this is that we can still access the server from another local machine or the internet but we cannot connect to anything outsidefrom withinthe server. Also when we look at the Resource Monitor - network section, the system (PID 4) has over 298 entries to various internet addresses (Example: System 4 75.143.178.88 1500 150 ) One error we sometime get when we try to connect outside the server is that it cannot locate a DNS. The DNS entries are static and the same for all of the other 5 servers (windows 2003 r2) which have been working properly since day one. Another stange thing is that although we cannot see or connect to local PC's, we can ping the local network but not the internet from this Windows 2008 server. If we try to disable the network card and re-enable the network card we get a service error # 2505 could not bind to the transport \Device\NetbiosSmb because another computer on the network has the same name. I can assure you that is not the case. I presume that it is not clearing some cache and seeing itself when it tries to reconnect. We then get the following error: 1) Event 4199 - The SBSD Security Center Service service depends the following service: wscsvc. This service might not be installed. 2) Event 7026 - The following boot-start or system-start driver(s) failed to load: storflt Once the network connection is re-activated. The server can still be reached externally (local LAN and Internet) but it cannot access the local Lan or Internet. To fix the issue we must re-boot. If we leave it longer (several hours) the server locks up and we cannot logon or access it (no Keyboard or Mouse activity). We have re-installed Windows 2008 and replaced the network card with another make and model with no correction to the issue. Suggestion would be appreciated. Configuration: AMD Quad Core CPU8GB Ram1.5 GB storage space with 1.2 GB FreeDlink -DGE-530T -V.B-1 Gigabit Windows 2008 64 SP2IIS 7SQL 2008 Workgroup environmentWindows 2008 Firewall is on with port 80 open for our web sites and it is behind our primary firewall) -- cjbcjb

Hello,please post an unedited ipconfig /all so we can exclude DNS as a problem and multihoming. So your complete network is a workgroup, if i understand you correct? Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.

Here is the config/all unedited, it includes the original network card which is disabled but still in the system. Yes our complete network of 6 servers and4 workstations is a workgroup.Microsoft Windows [Version 6.0.6002]Copyright (c) 2006 Microsoft Corporation. All rights reserved. C:\Users\Administrator>ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : Accraserver5 Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No Ethernet adapter Local Area Connection 2: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : D-Link DGE-530T V.B1 Gigabit Ethernet Adapter Physical Address. . . . . . . . . : 00-22-B0-61-7C-1C DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::641d:7bf:747b:79c2%12(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.20.15(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.20.1 DHCPv6 IAID . . . . . . . . . . . : 285221552 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-11-B8-C5-9D-00-24-8C-15-07-F2 DNS Servers . . . . . . . . . . . : 198.164.30.2 198.168.4.2 NetBIOS over Tcpip. . . . . . . . : Enabled Ethernet adapter Local Area Connection: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : NVIDIA nForce 10/100/1000 Mbps Ethernet Physical Address. . . . . . . . . : 00-24-8C-15-07-F2 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Tunnel adapter Local Area Connection* 8: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : isatap.{09BE2300-DCFB-460D-9288-A848D0ED25A9} Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Tunnel adapter Local Area Connection* 9: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface Physical Address. . . . . . . . . : 02-00-54-55-4E-01 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e50:1cee:2006:3f57:ebf0(Preferred) Link-local IPv6 Address . . . . . : fe80::1cee:2006:3f57:ebf0%11(Preferred) Default Gateway . . . . . . . . . : :: NetBIOS over Tcpip. . . . . . . . : Disabled Tunnel adapter Local Area Connection* 11: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : isatap.{69C19BBC-DA8B-4C28-B9EB-33EF88AA228E} Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes C:\Users\Administrator>cjb

Hello,if you don't use IPv6 you should disable it complete, it doesn't work correct. See here how to:http://blogs.dirteam.com/blogs/paulbergson/archive/2009/03/19/disabling-ipv6-on-windows-2008.aspxIn the workgroup you haveone internal DNS server and the external, that creates your problems. Sometimes the internal will be used and then the external and the connection fails.So configure a FORWARDER on the internal used DNS server properties in the DNS management console and remove the external one from the workgroup machine NICs.See also:http://support.microsoft.com/kb/323380Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.

Thanks for the info, we have done the changes suggested and will monitor. One item we did not understand and do is: In the workgroup you haveone internal DNS server and the external, that creates your problems. Sometimes the internal will be used and then the external and the connection fails.So configure a FORWARDER on the internal used DNS server properties in the DNS management console and remove the external one from the workgroup machine NICs. Both DNS are external to our organization since in practice 99.9% of the time the server is a web server. The two DNS are from the largest national ISP. We do not understand the issue you are raising. Some additional explanation would be appreciated. Should we only have one of the DNS listed in the NIC? Thanks Charlescjb