Thanks for your help.  Cool product... But confirmed my fear.  Nothing had
port 23.  As I was working on this, I also found a slew of other serious
problems regarding my network config...  IE. Spooler not functioning,
network browsing not functioning, mapped drives not functioning, other port
assignments failing...

Could it be time to backup, fdisk, and start over?  Hmm.... I am thinking
yes.  (oh the pain of a re-load...)

Thanks again,

-----Original Message-----
Behalf Of Ken Wallis
Sent: Wednesday, April 28, 2004 7:35 PM
To: 'U2 Users Discussion List'
Subject: RE: UniVerse Personal Edition Telnet Service

Glenn W. Paschal wrote:

> I am getting the following errors trying to start the Telnet Service.
>     UniVerse error: Unable to bind socket to telnet port 23. It may be 
> used by other application. WSA error: 10038.
>     UniVerse error: Unable to bind socket to uvrpc port. WSA
> error: 10038.
> Ok, I realize what this is telling me...  Obviously, I
> installed something
> or configured something that is running conflict.  My question is...
> How do I find out what is running in conflict or what has
> grabbed port 23?

Go to and download tcpview.exe.  This tool will show
you in real(ish) time what netstat shows you whenever you run it, except it
also shows the name of the executable associated with each connection.



PS.  Sorry Robert, I couldn't think of a CALLC that would help Glenn on
this! ;^)

u2-users mailing list

u2-users mailing list

Reply via email to