I found this for event ID 1053
Event ID 1053 - Userenv

Symptoms: your w2k/xp clients may receive this Event ID 1053 - Windows cannot determine the user or computer name. (<error description>). Group Policy processing aborted.  Or error: "The specified user does not exist."

Resolutions: 1. Make sure that your internal DNS server is the server for the domain you are logging in to.
2. Verify the DNS Settings. This will occur if your DNS server is unable to resolve information about your domain.
3. Delete the problem computer from DNS records and re-create it.

This is most often caused when a compter that is a member of a domain cannot get an IP adress for a domain controller.  Is this computer a laptop or has it been moved to a remote location that is not connected to the domain?

No it hasn't, but I figured it had something to do with name resolution.  What I ended up doing is unjoining the domain.  Removed the computer account from AD and the host record from DNS.  Then I rejoined the domain and everything seems to be working correctly.  

yep sounds about right too. Cheers
Merete

The problem has come back.

Maybe related to these..
WSAECONNABORTED 10053 Software caused connection abort.
An established connection was aborted by the software in your host computer, possibly due to a data transmission time-out or protocol error.  

The error is raised by window
sockets and it is called a WSAENOBUFS (errorcode 10055)
error. There are solutions suggested by Microsoft and
others (do a google search on WSAENOBUFS) which involve
editing registry tcpip parameters.

10053 ptConnectionAborted Software caused connection abort. An established connection was aborted by the software in your host machine, possibly due to a data transmission timeout or protocol error. FATAL.


relevent articals.
FIX: Socket initialization does not succeed if your computer has more than 50 network bound protocols
http://support.microsoft.com/default.aspx?scid=kb;%5BLN%5D;826757

http://support.microsoft.com/default.aspx?scid=kb;en-us;815209
CAUSE
When you install a protocol or a network adapter on your computer, the operating system creates a protocol binding between the network adapters and the protocols that are installed on your computer. Typically, a computer can store up to 50 protocol binding details. Therefore, if the number of protocol bindings exceeds 50, and you use the IPAddress class directly or indirectly (such as when you try to add a Web reference or when you call a Web service method), you receive the error messages that are mentioned in the "Symptoms" section of this article.

Notes• The operating system creates a protocol binding even for "phantom" ("ghosted") adapters on your computer.

For additional information about phantom devices, click the following article number to view the article in the Microsoft Knowledge Base:
241257 (http://support.microsoft.com/kb/241257/) Device Manager Does Not Display Devices Not Currently Present in Windows 2000  
• To determine the number of protocol bindings on your computer, run the enum.exe file.

The following file is available for download from the Microsoft Download Center:
 
Download the enum.exe package now. (http://download.microsoft.com/download/9/3/0/930e1ecb-a6c6-445f-bd79-82fc3e66f009/enum.exe) For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge

RESOLUTION
To resolve this problem, you must reduce the number of protocol bindings on your computer to less than 50. To do this, use one of the following methods: • To remove unnecessary protocols from your computer, follow these steps: 1. Click Start, point to Settings, point to Network and Dial-up Connections, and then right-click any existing connection.

For example, you may right-click Local Area Connection.
2. Click Properties, select an unused protocol, and then click Uninstall.
3. Click Yes when you are prompted for confirmation.
4. Repeat step 1 to step 3 to remove any other unused protocols.
- or -
• To remove any unnecessary network adapters on your computer, follow these steps.

Note Before you follow these steps, make sure that Device Manager displays phantom devices also.

For additional information about displaying phantom devices, click the following article number to view the article in the Microsoft Knowledge Base:
241257 (http://support.microsoft.com/kb/241257/) Device Manager Does Not Display Devices Not Currently Present in Windows 2000
1. On the Windows desktop, right-click My Computer, and then click Properties.
2. Click Hardware, and then click Device Manager.
3. Expand Network adapters.
4. Right-click any unnecessary network adapters, and then click Uninstall.
5. Click OK when you are prompted for confirmation.
6. Repeat step 4 and step 5 to remove any other unnecessary network adapters.
 
Steps to Reproduce the Problem
1. Start Visual Studio .NET 2003.
2. Use either Microsoft Visual Basic .NET or Microsoft Visual C# .NET to create an ASP.NET Web Service project named TimeoutDemo. By default, the Service1.asmx file is created.
3. On the View menu, click Code.
4. Locate and then uncomment the HelloWorld Web service method.
5. On the Build menu, click Build TimeoutDemo.
6. Use either Visual Basic .NET or Visual C# .NET to add a new Console Application project named MyClient to the TimeoutDemo solution.
7. On the Project menu, click Add Web Reference. The Add Web Reference dialog box appears.
8. In the URL box, type the URL of the TimeoutDemo Web service, and then press ENTER. You may notice the following error message:


There was an error downloading 'http://WebServerName/WebServicePath/TimeoutDemo'. The operation has timed-out.
9. At a Visual Studio .NET 2003 command prompt, run the following command:

wsdl http://WebServerName/WebServicePath/TimeoutDemo/Service1.asmx

You may notice the following error message:


Unhandled Exception: System.TypeInitializationException: The type initializer for "System.Net.Sockets.Socket" threw an exception. ---> System.Net.Sockets.SocketException: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full at System.Net.Sockets.Socket.InitializeSockets() at System.Net.Sockets.Socket..cctor()

See if this covers it for you.
Merete

I fixed this issue by editing the registry and modifying these two keys:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\TcpTimedWaitDelay to 120 seconds

and

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\MaxUserPorts to 50000

Did a reboot almost two weeks ago and have not had the problem come back yet.

This is the article I found:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/randz/protocol/tcp_time-wait_delay.asp