Jim Lawrence
accessd at shaw.ca
Thu Nov 21 14:40:18 CST 2013
Thanks for the help Jim. The trouble is that the appropriate service may have started, appeared to be still started but is locked. Just like the IIS server...a good restart always clears its brains. As there is a possible sixty(?) services that may or may not need to be started or restarted it is difficult to guess and of course the naming is not always apparent. The client ended up offline to their main databases for fours hours but in the interim, I set it so the emails could be received and send...so they were reasonably happy. I did a dump using tasklist and tasklist/svc when the network was locked and again when it was restarted and now I will carefully go through the lists. If that doesn't work the next step is to install the ProcessExplorer and crawl through the system as what ever process it is it is hidden within the infamous svchost process. The interesting question was why remote access was still working fine (hamachi/rdp)? Note: the server has Vipre running on it so the run away process should not be malware. 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