Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Setting Up UWIN

Status
Not open for further replies.

jamie2

Programmer
Jul 26, 2005
1,127
US
Okay, I got a new PC and I am trying to setup UWIN on it. Had it installed on old PC many moons ago.

The problem I am having is when I connected via telnet (127.0.0.1), I can receive the LOGIN: prompt, but then the telnet port closes before I can input the username.

KSH is working.
UWIN is working, I can see the Port opened-Telnet.

Any suggestions?
 
I have had the exact same issue and could not resolve it. If you figure it out or someone else does please post.

I tried uninstalling and reinstalling etc. I googled the issue but there wasn't much available. I telnet to one of our Signaling Servers and then Rlogin to the PBX I want to connect to as a work around for now.
 
telecomPA, UWIN (Unix for Windows) is an open source software that allows you to create rlogin tunnel from your desktop to your PBX, and use telnet via the tunnel. When UWIN is running and connected via Rlogin, then you are able to run Procomm.

I usually use ZOC now, but like to have Procomm and UWIN ready for a backup or to run scripts with large GUI interfaces.

When you telnet to 127.0.0.1, you are essentially doing telnet 'localhost' and coming back into your local PC.
 
Okay, I have got a little farther. I set the TELNET service to automatic and rebooted my PC. Now when I telnet to 127.0.0.1 stay connected and I am able to put in my login name and password, but I do not get the $ prompt.

Instead I see:

*=====================================================
Welcome to Microsoft Telnet Server.
*=====================================================
C:\Documents and Settings\jamie>


Any suggestions?
 
guycable2, I tried starting the Telnet service, but this enables Microsoft Telnet Server, and you will not connect to the UWIN Service. ie... UWIN-XP 4.1.0/5.1 (COMPUTERNAME) (ttyp0)

If I figure this out I will let you know, but I am sure it was a recent AD migration that our network guys did something to change our environment.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top