I have several problem with my windows XP clients
Some times i can't acess my outside email .... many times a reboot will work
but...
Here's what i found in the event viewer
Event Type: Warning
Event Source: WinSock Proxy Client
Event Category: None
Event ID: 3
Date: 02-03-2006
Time: 17:12:06
User: N/A
Computer: SANDRINEX1
Description:
Application [svchost.exe]. The application was started while the service
manager was locked and NtLmSsp wasn't running. If the application will try to
remote via WinSock Proxy it can cause a deadlock with the service manager.
For this reason the remoting is disabled. If the application is a service,
and you want it to be able to remote, make it dependent on NtLmSsp.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Event Type: Warning
Event Source: WinSock Proxy Client
Event Category: None
Event ID: 3
Date: 02-03-2006
Time: 17:12:13
User: N/A
Computer: SANDRINEX1
Description:
Application [lsass.exe]. The application was started while the service
manager was locked and NtLmSsp wasn't running. If the application will try to
remote via WinSock Proxy it can cause a deadlock with the service manager.
For this reason the remoting is disabled. If the application is a service,
and you want it to be able to remote, make it dependent on NtLmSsp.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Event Type: Warning
Event Source: WinSock Proxy Client
Event Category: None
Event ID: 3
Date: 02-03-2006
Time: 17:12:14
User: N/A
Computer: SANDRINEX1
Description:
Application [svchost.exe]. The application was started while the service
manager was locked and NtLmSsp wasn't running. If the application will try to
remote via WinSock Proxy it can cause a deadlock with the service manager.
For this reason the remoting is disabled. If the application is a service,
and you want it to be able to remote, make it dependent on NtLmSsp.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Event Type: Warning
Event Source: WinSock Proxy Client
Event Category: None
Event ID: 3
Date: 02-03-2006
Time: 17:12:17
User: N/A
Computer: SANDRINEX1
Description:
Application [svchost.exe]. The application was started while the service
manager was locked and NtLmSsp wasn't running. If the application will try to
remote via WinSock Proxy it can cause a deadlock with the service manager.
For this reason the remoting is disabled. If the application is a service,
and you want it to be able to remote, make it dependent on NtLmSsp.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Event Type: Warning
Event Source: WinSock Proxy Client
Event Category: None
Event ID: 3
Date: 02-03-2006
Time: 17:12:27
User: N/A
Computer: SANDRINEX1
Description:
Application [Pagent.exe]. The application was started while the service
manager was locked and NtLmSsp wasn't running. If the application will try to
remote via WinSock Proxy it can cause a deadlock with the service manager.
For this reason the remoting is disabled. If the application is a service,
and you want it to be able to remote, make it dependent on NtLmSsp.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Event Type: Warning
Event Source: WinSock Proxy Client
Event Category: None
Event ID: 3
Date: 02-03-2006
Time: 17:12:31
User: N/A
Computer: SANDRINEX1
Description:
Application [spoolsv.exe]. The application was started while the service
manager was locked and NtLmSsp wasn't running. If the application will try to
remote via WinSock Proxy it can cause a deadlock with the service manager.
For this reason the remoting is disabled. If the application is a service,
and you want it to be able to remote, make it dependent on NtLmSsp.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.´
Event Type: Warning
Event Source: WinSock Proxy Client
Event Category: None
Event ID: 3
Date: 02-03-2006
Time: 17:12:32
User: N/A
Computer: SANDRINEX1
Description:
Application [spoolsv.exe]. The application was started while the service
manager was locked and NtLmSsp wasn't running. If the application will try to
remote via WinSock Proxy it can cause a deadlock with the service manager.
For this reason the remoting is disabled. If the application is a service,
and you want it to be able to remote, make it dependent on NtLmSsp.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Event Type: Warning
Event Source: WinSock Proxy Client
Event Category: None
Event ID: 3
Date: 02-03-2006
Time: 17:12:37
User: N/A
Computer: SANDRINEX1
Description:
Application [PSKMsSvc.exe]. The application was started while the service
manager was locked and NtLmSsp wasn't running. If the application will try to
remote via WinSock Proxy it can cause a deadlock with the service manager.
For this reason the remoting is disabled. If the application is a service,
and you want it to be able to remote, make it dependent on NtLmSsp.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Event Type: Warning
Event Source: WinSock Proxy Client
Event Category: None
Event ID: 3
Date: 02-03-2006
Time: 17:12:37
User: N/A
Computer: SANDRINEX1
Description:
Application [svchost.exe]. The application was started while the service
manager was locked and NtLmSsp wasn't running. If the application will try to
remote via WinSock Proxy it can cause a deadlock with the service manager.
For this reason the remoting is disabled. If the application is a service,
and you want it to be able to remote, make it dependent on NtLmSsp.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
--
Francisco Ribeiro
Portugal
