clients lose connection to server for only a few seconds



Problem is that the server and workstations have a few second hiccup between
their connection. The workstations have three applications open that the
data is stored on the server but the applications are on the local machine.
We are only notified of the disconnect because the database application or
quickbooks will notify us of an error accessing the file (sometimes delay
write failure, file is not available, outlook shows error connecting to
exchange, etc.) When the 1st user notices the error (it varies on which
person notices it first) the other workstations also have the problem at the
same exact time. If the user closes the application and opens again, then
they can continue to work without problems until it happens again. If the
user tries to stay in the application without closing, they continue to get
errors and cannot work. The problem happens on all three workstations at the
same time, the server does not have any logs that I can find that is yelling
for help. The workstations have logs which show when the application fails
so I can see when it's happening but not why. The disconnect only lasts for
a few seconds and normally happens between 3-5 times per day. Also, this has
happened for the past couple of years and it normally would only start
happening after patch tuesday and after the server had been rebooted. In the
past, shutting down all of the equipment (computers, server, router) and
starting it back up would fix it until the following patch Tuesday. This
time nothing has resolved it.

During one of the lost connections, I immediately tried to ping the server
and the 1st ping failed but the 3 remaining were received. Each of the
workstations and server has static ip's.

I have tried updating the driver on the server nic, they had this problem
with an old router and new router. I have uninstalled the nic, reset the
tcp/ip stack and reset winsock.

I looked through the windows updates and for Dec. and Jan. different
hotfixes were installed.

Windows SBS 2003
1-XP Pro - member of domain
2-XP Home -members of workgroup
2 applications that are based upon MS ACCESS (data stored on server and
application is on the local machines)
1 quickbook application (data stored on the server and application is on the
local machines)



.



Relevant Pages

  • Re: Complicated Connection Problems bewteen ADP and SQL Server
    ... front end on the 5-8 workstations where the users happen to sit. ... expertise for getting the user workstations talking to the SQL Server. ... connection would fail and the adp wouldn't be able to talk to the server. ... thought that I should instead change my connection string to something ...
    (microsoft.public.access.adp.sqlserver)
  • Re: Complicated Connection Problems bewteen ADP and SQL Server
    ... If the workstation can see (connect to the SQL Server); ... If the user has appropriate permission to the database on that SQL ... front end on the 5-8 workstations where the users happen to sit. ... connection would fail and the adp wouldn't be able to talk to the server. ...
    (microsoft.public.access.adp.sqlserver)
  • Re: RWW connection to client computers
    ... I don't have a server here to compare, but the RRAS being on the same subnet ... workstations. ... My computer, r click, properties, remote... ... connections, as i have been using remote connection and connecting via ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 Misconfigured?
    ... up one of the workstations via remote web connection, ... but why are you looking at the server rather than the workstation? ... (this will show you the DHCP lease info). ... The Netgear, or whatever you use as your gateway to get out to the Internet. ...
    (microsoft.public.windows.server.sbs)
  • Re: In-Place Upgrade From Windows 2K Server
    ... I will try to set the DNS for the clients to be only from the DC. ... server so I fill up all 3/4 ports (2 workstations and server) on the router ... Ethernet adapter Local Area Connection 2: ...
    (microsoft.public.windows.server.active_directory)