[AccessD] Restart network services on a server

Jim Lawrence accessd at shaw.ca
Fri Nov 22 11:27:15 CST 2013


Jim

I do think there is something more going on and it may require a re-install. The problems keep happening even though the apparent offending APIs and DDLs have been removed and re-installed. Something must be corrupt with some core component...and it difficult locating it.

Jim

----- Original Message -----
From: "Jim Dettman" <jimdettman at verizon.net>
To: "Access Developers discussion and problem solving" <accessd at databaseadvisors.com>
Sent: Friday, November 22, 2013 5:05:47 AM
Subject: Re: [AccessD] Restart network services on a server

Jim,

<<I would suspect that lanmanserver and lanmanworkstation are the key to the
problems.>>

 I would agree and probably lanmanserver, which is takes care of making
shares available.   You said RDP was working, so the TCP/IP stack was still
functional as was the NIC. 

<<The only question now is why this group got into this condition
considering that nothing has been added to the system but Microsoft's
updates? >>

 Check the event log and see if something faulted.  It also could have been
something unrelated because of svchost bundling as you mentioned.

<<And we know MS would never screw up their servers.>>

  I do have to say this is something Microsoft has improved upon over the
last few years.   As long as your not on the bleeding edge with the latest
and greatest, it's not too often now that I find an update stops a server.

 Stations a little less so, but even that patch process has gotten better.
The issue with stations though is the wide range of applications that may be
installed on them, so the chances of running into a conflict are far
greater.

Jim.

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence
Sent: Thursday, November 21, 2013 06:20 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Restart network services on a server

Followup:

It seemed that a group of services had to be restarted. They all showed that
they were running but apparently not. One Svchost process locked causing all
the following services to stop functioning. I have never liked the Svchost
bundling and now I like it even less.

The services that were stopped can not seen when checking the servers 
WinHttpAutoProxySvc, AudioSrv, Browser, dmserver, HidServ, lanmanserver,
lanmanworkstation,          seclogon, TrkWks and wuauserv,

I would suspect that lanmanserver and lanmanworkstation are the key to the
problems. Anyway I restarted all of the above and everything is working. The
only question now is why this group got into this condition considering that
nothing has been added to the system but Microsoft's updates? And we know MS
would never screw up their servers.

Jim                                       

----- Original Message -----
From: "Jim Dettman" <jimdettman at verizon.net>
To: "Access Developers discussion and problem solving"
<accessd at databaseadvisors.com>
Sent: Wednesday, November 20, 2013 1:05:24 PM
Subject: Re: [AccessD] Restart network services on a server


 Not sure if this will help at this point, but open service from the admin
tools, click on the startup type column and look for all that are
"Automatic" or "Automatic Delayed start".  All those services should have a
status of "Started".

 I would probably "repair" the network connection as well (or disable it and
then enable it).

Jim. 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence
Sent: Wednesday, November 20, 2013 01:54 PM
To: Access Developers discussion and problem solving
Subject: [AccessD] Restart network services on a server

Hi All:

I am at a client's site and running a full rebuild of their database server
and then became aware that no one on the network can connect in. 

It appears that the networking service has to be restarted but the server
can not be rebooted until the database is rebuilt. I have run the basic "net
stop and start" but it doesn't work. 

Would anyone know off hand what service(s) that would need restarting?

MTIA
Jim

 
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com


More information about the AccessD mailing list