[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 397
  • Last Modified:

All Clients disconnecting from SBS Server 2003 several times a day

I recently replaced a Windows 2000 server with a SBS 2003 server.  I did a complete swap only transferring data.  The new server is a dual processor, dual hd with raid, 2GB memory.  The server has dual NICs with one connected to
Charter cable and the other connected to the LAN.

The server worked perfect until I installed Symantec AntiVirus 10.0 SMB.  Within days I began having the server tell the clients that there was not enough storage space on their shared drives.  There was over 200GB left on each shared drive.  This would happen at the same time every single day.  I found the solution on EE and fixed that problem.  It was a Symantec issue.   Everything rolled along smoothly for several weeks until 3 days ago.  Nothing should have changed unless there was an automatic update from Symantec or Microsoft via the internet.

 Now, I am suddenly having all internal users lose connection to the server several times a day.  All they get is that they have lost the connection and are now working offline.  When this occurs, the clients cannot ping the server and the server cannot ping the clients.  The server cannot even ping our DVR recorder that has a static ip.  The server will still function normally at the console, connect to the internet, and can even be controlled remotely from the internet with no problem.  The only symptom is the internal users cannot access the server.  The only solution is to reboot the server.  I have changed the NICs just to make sure that they were not the problem.    Since this problem began, I am getting the following error messages in my Server Performance Report.  Not sure if they are related.  I have researched each error and tried the fixes located here on EE and I still keep losing my clients connection.  This is not good, since the warehouse cannot ship orders if the office cannot process them! :)  I am getting much heat from this!

  Windows SharePoint Services 2.0 1000 6/2/2006 1:16 PM 2 *
#50070: Unable to connect to the database STS_Config on TSDSERVER\SharePoint. Check the database connection information and make sure that the database server is running.  
 
 MSExchangeAL 8026 6/2/2006 7:02 AM 6 *
LDAP Bind was unsuccessful on directory tsdserver.TristateDistributors.local for distinguished name ''. Directory returned error:[0x51] Server Down. For more information, click http://www.microsoft.com/contentredirect.asp.  
 

 MSExchangeAL 8250 6/2/2006 7:02 AM 3 *
The Win32 API call 'DsGetDCNameW' returned error code [0x862] The specified component could not be found in the configuration information. The service could not be initialized. Make sure that the operating system was installed properly. For more information, click http://www.microsoft.com/contentredirect.asp.  
 

  MSExchangeDSAccess 2102 6/2/2006 7:02 AM 1
Process MAD.EXE (PID=2728). All Domain Controller Servers in use are not responding: tsdserver.TristateDistributors.local For more information, click http://www.microsoft.com/contentredirect.asp.  
 
0
eagleswings
Asked:
eagleswings
  • 10
  • 8
  • 7
  • +1
1 Solution
 
dhoustonieCommented:
This could be a cable or a port issue on your hub/switch. Why don't you try plugging in the server to another port on the hub, if that doesn't work try a different network cable.
If that does not resolve the issue see if there is a new driver or firnware available for the network card.
Once you've tried that rerun the ceiwz Internet connection wizard just to make sure sbs acknowledges any changes.

Hope this helps,

David Houston
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Please post an IPCONFIG /ALL from both the server and one of the workstations.  Also, please advise how you joined your workstations to the network... did you use http://<servername>/connectcomputer?

Jeff
TechSoEasy
0
 
eagleswingsAuthor Commented:
dhoustonie - I am having to connect remotely this weekend, so I cannot try your suggestions until Monday.

TechSoEasy - Here goes - I blocked out some of the IP address for security.  Yes I did use connectcomputer.  This is the server IPCONFIG - I am connecting remotely and all workstations have been turned off, so it will be Monday before I can get a WS IPCONFIG.

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : tsdserver
   Primary Dns Suffix  . . . . . . . : TristateDistributors.local
   Node Type . . . . . . . . . . . . : Unknown
   IP Routing Enabled. . . . . . . . : Yes
   WINS Proxy Enabled. . . . . . . . : Yes
   DNS Suffix Search List. . . . . . : TristateDistributors.local

Ethernet adapter Network Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : NVIDIA nForce Networking Controller #2
   Physical Address. . . . . . . . . : 00-E0-81-5B-17-FE
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IP Address. . . . . . . . . . . . : 66.168.***.**
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 66.168.234.1
   DHCP Server . . . . . . . . . . . : 68.114.39.11
   DNS Servers . . . . . . . . . . . : 192.168.16.2
   Primary WINS Server . . . . . . . : 192.168.16.2
   NetBIOS over Tcpip. . . . . . . . : Disabled
   Lease Obtained. . . . . . . . . . : Saturday, June 03, 2006 5:38:32 PM
   Lease Expires . . . . . . . . . . : Sunday, June 04, 2006 1:38:32 AM

Ethernet adapter Local Area Connection 5:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast Ethernet
NIC #2
   Physical Address. . . . . . . . . : 00-40-F4-D0-14-11
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : 192.168.16.2
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :
   DNS Servers . . . . . . . . . . . : 192.168.16.2

0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
dhoustonieCommented:
Just the last part to TechSoEasy's question, how where the computers connected to the domain, through http://servername/connectcomputer ?
0
 
dhoustonieCommented:
What is your network switch?
David
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
You have your WINS server configured on the wrong NIC.  It should be on your Internal one, not the External one.

Also, since it seems as though you've added and removed the adapter settings a number of times (the "connection 5" gave it away... :-)  ) you should check to make sure that the Internal NIC is binding first.  Open Network Connections > Advanced > Advanced Settings... and make sure that your Internal NIC is listed on top.  Also, while you're there remove File & Print sharing for Microsoft Networks from the EXTERNAL NIC if it's enabled. (this doesn't have anything to do with your connectivity problem... just a security measure).

Once you've gotten that straightened out rerun the Configure Email and Internet Connection Wizard.  Reboot your workstations and you should be good to go.

Jeff
TechSoEasy

0
 
eagleswingsAuthor Commented:
Tried your suggestions.  I think that I did the WINS right, but maybe not.  It is now showing on both NIC cards though,  is this right?

The internal was binding first.  I changed the WINS stuff and then reran the Email and Internet Connection Wizard and this is what I now have.  


Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : tsdserver
   Primary Dns Suffix  . . . . . . . : TristateDistributors.local
   Node Type . . . . . . . . . . . . : Unknown
   IP Routing Enabled. . . . . . . . : Yes
   WINS Proxy Enabled. . . . . . . . : Yes
   DNS Suffix Search List. . . . . . : TristateDistributors.local

Ethernet adapter Network Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : NVIDIA nForce Networking Controller #2
   Physical Address. . . . . . . . . : 00-E0-81-5B-17-FE
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IP Address. . . . . . . . . . . . : 66.168.***.**
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 66.168.234.1
   DHCP Server . . . . . . . . . . . : 68.114.39.11
   DNS Servers . . . . . . . . . . . : 192.168.16.2
   Primary WINS Server . . . . . . . : 192.168.16.2
   NetBIOS over Tcpip. . . . . . . . : Disabled
   Lease Obtained. . . . . . . . . . : Monday, June 05, 2006 10:49:05 AM
   Lease Expires . . . . . . . . . . : Monday, June 05, 2006 6:03:17 PM

Ethernet adapter Local Area Connection 5:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast Ethernet
NIC #2
   Physical Address. . . . . . . . . : 00-40-F4-D0-14-11
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : 192.168.16.2
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :
   DNS Servers . . . . . . . . . . . : 192.168.16.2
   Primary WINS Server . . . . . . . : 192.168.16.2

C:\Documents and Settings\Administrator>
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
No, you don't want WINS on the external NIC.  Remove it and rerun the CEICW.  Then your issue should be resolved.

Jeff
TechSoEasy
0
 
eagleswingsAuthor Commented:
Ok.  Will this work?  


Windows IP Configuration

   Host Name . . . . . . . . . . . . : tsdserver
   Primary Dns Suffix  . . . . . . . : TristateDistributors.local
   Node Type . . . . . . . . . . . . : Unknown
   IP Routing Enabled. . . . . . . . : Yes
   WINS Proxy Enabled. . . . . . . . : Yes
   DNS Suffix Search List. . . . . . : TristateDistributors.local

Ethernet adapter Network Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : NVIDIA nForce Networking Controller #2
   Physical Address. . . . . . . . . : 00-E0-81-5B-17-FE
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IP Address. . . . . . . . . . . . : 66.168.234.61
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 66.168.234.1
   DHCP Server . . . . . . . . . . . : 68.114.39.11
   DNS Servers . . . . . . . . . . . : 192.168.16.2
   NetBIOS over Tcpip. . . . . . . . : Disabled
   Lease Obtained. . . . . . . . . . : Monday, June 05, 2006 6:38:11 PM
   Lease Expires . . . . . . . . . . : Tuesday, June 06, 2006 2:36:46 AM

Ethernet adapter Local Area Connection 5:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast Ethernet
NIC #2
   Physical Address. . . . . . . . . : 00-40-F4-D0-14-11
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : 192.168.16.2
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :
   DNS Servers . . . . . . . . . . . : 192.168.16.2
   Primary WINS Server . . . . . . . : 192.168.16.2

C:\Documents and Settings\Administrator>
0
 
eagleswingsAuthor Commented:
Did not work.  Did everything except change the network switch and it still lose connection to all computers.  The above post is the IPCONFIG /all for the server.

Any other ideas?  I am desperate! :)
0
 
dhoustonieCommented:
What is the network switch?
What version of driver is installed for the nic?
David
0
 
eagleswingsAuthor Commented:
The driver for the nic is - 5.398.613.2003
The switch is a 24 port 3Com switch.
0
 
dhoustonieCommented:
Do you have a part number for the switch?

Is the version number for the Nic the built in Microsoft driver?

David
0
 
eagleswingsAuthor Commented:
No I do not have part number for the switch right now.  

The version number for the NIC is the built in Microsoft driver.
0
 
dhoustonieCommented:
What was the other nic that you installed? Same make?
David
0
 
dhoustonieCommented:
There is an updated driver on the realtek website:
http://www.realtek.com.tw/downloads/downloads1-3.aspx?lineid=1&famid=3&series=16&Software=True

I'd use the first one on the list, I can't gaurantee that iot works as it does not specify 2003 but it is upto version 641. Its a possible option.

David
0
 
dhoustonieCommented:
When you swapped nics did you remove them completely using the uninstall option?
When you have the problem are you finding any processes have taken large portions of resourses?
Are the times that the server hangs consistent, ie at the same time daily?

David
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
David, that's a good path to investigate... I'd also assume that a 24-port 3-com switch is a managed switch... (I try to stay away from managed switches with SBS's)... and if it is, it needs to be managed.  :-)

Jeff
TechSoEasy
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
eagleswings,

Please also post an IPCONFIG /ALL from one of the workstations that is having problems staying connected so we can see it from that end.

Thanks.

Jeff
TechSoEasy
0
 
eagleswingsAuthor Commented:
OK.  I have updated the driver for the NIC and still having the same problem.  I completely uninstalled the NIC and reinstalled it with the new driver.  Cannot fin processess taking up large portions or resources (I don't think anyway!)  
Seems to lose connection to clients anywhere from 30 min to 3 or 4 hours.  No specific time it seems.   When it started, it was once a day at the same time, but now it is happening all through the day randomly.  

What is weird, when the clients lose connection, I can still connect remotely through the internet and the server works fine either remotely or at the console.  Just loses connection with the clients and cannot ping any local ip.

Once again I will mention this to see if it jogs any memory.  We have had the server up for a few months and had no problem.  The very first time we had a problem was the day after we installed Symantec Corporate edition 10.0.  I found a fix for what seems to be a common problem with this and it seemed to work for about a week, then this.  Our new problem seems to get worse every day.


Here is one of the WinXP clients IPCONFIG.

Windows IP Configuration

        Host Name . . . . . . . . . . . . : glenda
        Primary Dns Suffix  . . . . . . . : TristateDistributors.local
        Node Type . . . . . . . . . . . . : Hybrid
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No
        DNS Suffix Search List. . . . . . : TristateDistributors.local
                                            TristateDistributors.local

Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix  . : TristateDistributors.local
        Description . . . . . . . . . . . : Intel 21143-Based PCI Fast Ethernet
Adapter (Generic)
        Physical Address. . . . . . . . . : 00-48-54-13-0A-E9
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : 192.168.16.25
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.16.2
        DHCP Server . . . . . . . . . . . : 192.168.16.2
        DNS Servers . . . . . . . . . . . : 192.168.16.2
        Primary WINS Server . . . . . . . : 192.168.16.2
        Lease Obtained. . . . . . . . . . : Monday, June 05, 2006 4:16:48 PM
        Lease Expires . . . . . . . . . . : Tuesday, June 13, 2006 4:16:48 PM

E:\Documents and Settings\TSD USER>
0
 
dhoustonieCommented:
From what you have said, to me, it looks related to the physical internal network, but I would usully expect some other kind of error messages too.
Are there any errors on the client computers event logs relating to network problems?
Is the switch new or old?
Managed or unmanaged?
It is a possibility that the switch could need a reset or firmware update.The switch has been power cycled? It could also be that there is an incompatability with the realteck card and that you need to set the speed on the card for your network rather then use auto negotiation.
What was the other network card you put into the server?
Is the server beside the switch, if so try just connecting it directly to the switch with a single known reliable cable. You have tried other ports on the switch?


David
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
If it's the clients just losing their connection I would put some good money on the switch being faulty.  If you can get a new one, that is not managed, I'd go for that.

Jeff
TechSoEasy
0
 
eagleswingsAuthor Commented:
OK.  Not real sure what the solution was.....    Symantec had definately corrupted some system files, but a clean install of SBS Server 2003 did not correct the entire problem.  I changed the switch, the mainboard on the server, and did a fresh install.  Now everything is working.
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
You changed too many things at once... but I'd guess that it was still the switch... try using it somewhere else and see if it fails.

Jeff
TechSoEasy
0
 
dhoustonieCommented:
I agree with Jeff on the switch being the most likely culporate, a bad port or some such. Glad you got it resolved.


David
0
 
CetusMODCommented:
PAQed with points refunded (500)

CetusMOD
Community Support Moderator
0

Featured Post

Upgrade your Question Security!

Add Premium security features to your question to ensure its privacy or anonymity. Learn more about your ability to control Question Security today.

  • 10
  • 8
  • 7
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now