Sponsored Content
Operating Systems SCO Telnet connection to Sco Unixware from Windows 2000 taking longer !!! Post 47895 by malcom on Saturday 21st of February 2004 04:05:54 AM
Old 02-21-2004
Hi,

check the default syslogs if you see some strange messages of the telnet deamon.

Try telnet to localhost on the systems, to see if it only happens remotly, try a different system instead your win box to check if the problem is caused by this box.

We had a similar problem, the problem was a misconfiguration in our static arp config.

Regards
malcom
 

7 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Sco openserver and Windows 2000 server

Hi, i have 4 Unix Sco openservers, 4PCs running windows 2000, and 1 PC with windows server which i want to configure in the same network. During the configuration procedure, the wizard of Windows 2000 SERVER ask you if this is the only server in the network, now it will be the only WINDOWS... (2 Replies)
Discussion started by: BAM
2 Replies

2. UNIX for Dummies Questions & Answers

how to share printer installed on windows 2000 with SCO OpenServer 5.0.5

i have wipro netpower server with p4 and 256 ram. i want share dot matrix printer installed on windows 2000 prof. with sco openserver 5.0.5. plz help me to comeout from this trouble. (0 Replies)
Discussion started by: raj_shivage
0 Replies

3. SCO

windows connection to sco

I have a Sco box that runs an application. I currently have several connections open on terminals that connect via IP. How ever these are basically dumb terminals with a very basic configuration. I would like to connect to the Sco server from a windows pc. Now the questions. Will HyperTerminal... (2 Replies)
Discussion started by: rogueIT
2 Replies

4. SCO

Cannot type properly in telnet window (windows Xp & SCO Unix)

Hello friends, I am using telnet from windows xp to connect to SCO Unix. Since i am used to telnet environment given by linux from windows, this one is annoying. The cursor movements has no boundary, causing me to type control characters accidentally, which makes it difficult to navigate,... (1 Reply)
Discussion started by: frozensmilz
1 Replies

5. SCO

Printing to Windows 7 using Samba 2.0.3 via VPN connection to SCO 3.2v5.0.6

I would like to know if anyone has a way to PRINT TO a printer attached to a Windows 7 PC, from SCO, while logged in via a VPN connection. I am able to attach to a Samba share on the SCO server for files while attached to the VPN, so I know my Samba is workling - but my print jobs return: ... (2 Replies)
Discussion started by: tbb999
2 Replies

6. Solaris

Copy via samba on vmware workstation with Solaris taking much longer than usual

i have a vmware workstation with solaris 10 installed on this. i copying 2 gb data via samba from windows to this vmware workstation. copy speed is 24 kb/sec. how i can speed up this copy process ? (7 Replies)
Discussion started by: rehantayyab82
7 Replies

7. Shell Programming and Scripting

Daily script taking increasingly longer each day

Hello, I was wondering if anyone had an idea why a recurring script might take slightly longer each day. The intent of the script is to run on a dedicated VM and connect to several thousand remote servers to assay their operating status by running a series of commands and storing the results... (8 Replies)
Discussion started by: Threeze
8 Replies
XRLOGIN(1)						      General Commands Manual							XRLOGIN(1)

NAME
xrlogin - start an xterm that uses ssh (or optionally rlogin or telnet) to connect to a remote host SYNOPSIS
xrlogin [-l username] [-rlogin|-telnet] [xterm options] remote-host DESCRIPTION
Xrlogin opens an xterm window and runs ssh, rlogin or telnet to login to a remote host. Xrlogin automatically passes the -name argument to xterm with a value of "xterm-hostname" where hostname is the name of the remote host. This allows the user to specify resources in their server's resource manager which are specific to xterms from a given host. For example, this feature can be used to make all xterm windows to a given remote host be the same color or use a specific font or start up in a spe- cific place on the screen. Xrsh(1) passes the same string so they are compatible in this regard. Xrlogin specifies that the default title for the new xterm will be "hostname" where hostname is the name of the remote host. This and the -name argument above can be overridden with xterm-options on the command line. One could also use xrlogin's sister command xrsh(1) to open a window to a remote host. In the case of xrsh, the xterm would run on the remote host and use X as the connection protocol while xrlogin would run the xterm on the local host and use rlogin or telnet as the con- nection protocol. See xrsh(1) for a discussion of the merits of each scheme. OPTIONS
-l username When not using -telnet, use username as the id to login to the remote host. -rlogin Use the rlogin protocol to open the connection. In general rlogin is preferred because it can be configured to not prompt the user for a password. Rlogin also automatically propagates window size change signals (SIGWINCH) to the remote host so that applications running there will learn of a new window size. -telnet Use the -telnet protocol to open the connection. Use of telnet provided mostly for hosts that don't support rlogin. COMMON PROBLEMS
Make sure that the local host is specified in the .rhosts file on the remote host or in the remote hosts /etc/hosts.equiv file. See rlogin(1) for more information. EXAMPLES
xrlogin -bg red yoda Start a local red xterm which connects to the remote host yoda using rlogin. xrlogin -telnet c70 Open a local xterm which connects to the remote host c70 using telnet. SEE ALSO
xrsh(1), rlogin(1), telnet(1) AUTHOR
James J. Dempsey <jjd@jjd.com> and Stephen Gildea <gildea@intouchsys.com>. X Version 11 Release 6 XRLOGIN(1)
All times are GMT -4. The time now is 08:35 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy