Sponsored Content
Operating Systems SCO Telnet connection to Sco Unixware from Windows 2000 taking longer !!! Post 47932 by kbiswas on Monday 23rd of February 2004 03:18:01 AM
Old 02-23-2004
Thanx Perderabo . Nice to hear from you .

I think something is wrong with the DNS configuration .
When I added the IP of the source (Win 2k workstation) in the
/etc/inet/hosts of the Sun Server , the telnet problem got
resolved. Then we added the entry of this Sun Server in our
DNS server .

But still, the telnet problem persists for all other sources except
this Win 2k whose entry is there in the hosts file of the Sun server .

I need to access this server from anywhere and
will surely not req to add the IP of all the workstations in the server !!!

I am sure we are very close to the resolution and definate
to be there soon !!

Thanx for any help hereafter .
 

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
rexecd(8c)																rexecd(8c)

Name
       rexecd - remote execution server

Syntax
       /etc/rexecd

Description
       The  command  is  the  server  for the routine.	The server provides remote execution facilities with authentication based on usernames and
       encrypted passwords.

       The command is invoked by when it receives a connection on the port indicated in the ``exec'' service specification.  For further  informa-
       tion, see When a service request is received the following protocol is initiated:

       1) The server reads characters from the socket up to a null (`') byte.  The resultant string is interpreted as an ASCII number, base 10.

       2) If  the  number received in step 1 is non-zero, it is interpreted as the port number of a secondary stream to be used for the stderr.  A
	  second connection is then created to the specified port on the client's machine.

       3) A null terminated username of at most 16 characters is retrieved on the initial socket.

       4) A null terminated password of at most 16 characters is retrieved on the initial socket.

       5) A null terminated command to be passed to a shell is retrieved on the initial socket.  The length of the command is limited by the upper
	  bound on the size of the system's argument list.

       6) The  command	then  validates  the  user  as is done at login time and, if the authentication was successful, changes to the user's home
	  directory, and establishes the user and group protections of the user.  If any of these steps fail the  connection  is  aborted  with  a
	  diagnostic message returned.

       7) A  null  byte  is  returned on the connection associated with the stderr and the command line is passed to the normal login shell of the
	  user.  The shell inherits the network connections established by

Diagnostics
       All diagnostic messages are returned on the connection associated with the stderr, after which any  network  connections  are  closed.	An
       error  is indicated by a leading byte with a value of 1 (0 is returned in step 7 above upon successful completion of all the steps prior to
       the command execution).

       username too long
       The name is longer than 16 characters.

       password too long
       The password is longer than 16 characters.

       command too long
       The command line passed exceeds the size of the argument list (as configured into the system).

       Login incorrect
       No password file entry for the username existed.

       Password incorrect
       The wrong was password supplied.

       No remote directory
       The command to the home directory failed.

       Try again
       A fork by the server failed.

       /bin/sh: ...
       The user's login shell could not be started.

Restrictions
       Indicating ``Login incorrect'' as opposed to ``Password incorrect'' is a security breach which allows people to probe a	system	for  users
       with null passwords.

See Also
       inetd(8c)

																	rexecd(8c)
All times are GMT -4. The time now is 02:30 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy