Telnet Errors and Events

Updated: March 29, 2010

Applies To: Windows 7, Windows Server 2008, Windows Server 2008 R2, Windows Vista

Telnet Server can log the following events in the Event Viewer Application log.

 

Source Event ID Type Description and corrective action

Telnet Server

1000

Information

Telnet Service was started successfully.

No corrective action required.

Telnet Server

1001

Information

Telnet Service was stopped successfully.

No corrective action required.

Telnet Server

4006

Error

Telnet did not open the log file specified in the LogFile registry setting. A second event generated at about the same time might have more details about why the file did not open.

Ensure that the correct path is specified, and that the Telnet service account has permissions to write to that path.

Telnet Server

4049

Error

Telnet was not able to start the command processor specified in the DefaultShell registry entry.

Ensure that the correct path is specified. The default path is %systemroot%\system32\cmd.exe.

Telnet Server

4053

Error

The number of processes that can simultaneously use Winsock has been exceeded.

No corrective action required. Try again later when other network resources have completed their use of Winsock resources.

Telnet can generate the following errors.

 

Error ID Description

1058

This error is reported when you attempt to start the Telnet server while the service is set to Disabled.

Set the Startup Type of the Telnet Server service to something other than Disabled (Automatic or Manual). For instructions about how to change the Startup Type, see Enable the Telnet Server Service (http://go.microsoft.com/fwlink/?LinkId=108365) in the Telnet Operations Guide.

See Also

Community Additions

ADD
Show: