Telnet Server (tlntsvr) on Windows XP Professional: WSAGetLastError() returned error

  • Thread starter Thread starter Melvin \(clever alias\)
  • Start date Start date
M

Melvin \(clever alias\)

Hi,

I have Windows XP Professional. I recently enabled the built-in Telnet
Server via the Services applet in Administrative Tools (change startup type
from Manual to Automatic).

Now, I find the following error message in the Application Event Log:

---Begin Snip---
Soure: TlntSvr
Category: None
Type: Error
Event ID: 4053
User: N/A

Description:
WSAGetLastError() returned error: An address incompatible with the requested
protocol was used.


For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

---End Snip---

When I go to the Help & Support Center at the specified address, there is no
additional information.

The error always occurs at system startup and immediately after Information
Event #1000 stating that the Telnet Service was started successfully.

The Telnet Service does work nonetheless; I can telnet in to the machine
from another machine on my network and there are no issues.

My Windows O/S is unspoilt - it is basically Windows XP Professional
out-of-the-box with only the Windows Update patches applied.

Would anybody know why this is happening / how to resolve?

Thanks,
"Melvin"
 
I can spot two google threads on this error and nothing at eventid.net

One of the google threads is similar to your message--no followup.

The other points to this trojan-related article:

http://vil.nai.com/vil/content/v_99378.htm

Let me know if the trojan article helps you out with this one--I can see
that this trojan uses the telnet service, but not the relationship to the
error.
 
Bill,

Thanks for the reference to the http://EventID.Net site.

Event ID 4053 isn't currently documented in the main portion of the EventID
site but it is queued up to be documented in their EventID.Net Processing
Queue.

Somebody has dutifully copied in a response from a Microsoft Technical
Support person saying that the Telnet Service initially tries to open a
socket port using new IPv6 protocol stack; failing that (IPv6 not
installed), it will fall back to use IPv4 instead.

The bottom line is that the error message can safely be ignored. Wouldn't
it be nice if they'd just release a quick update to the O/S that would
convert the error message to an informational & change the text to something
more informational? That way we'd have one less thing on our "error
messages that can safely be ignored" lists. Well in a perfect world
anyway...

"Melvin"

Here's a link to the processing queue that I mentioned:

http://www.eventid.net/displayqueue.asp?eventid=4053
 
Thanks!

That might explain both the relationship of the message to SP1 (some details
about IPV6 changed with SP1, not sure what), and also why I haven't seen
it--I routinely install IPV6 on all machines.

I doubt that I've enabled Telnet Server, though :)

I believe I saw a message stating that the EVENTID folks were offering MVP's
free membership benefits, but I haven't taken them up on it.
 
Back
Top