Exceed or X-Manager for login


 
Thread Tools Search this Thread
Operating Systems HP-UX Exceed or X-Manager for login
# 1  
Old 06-22-2006
Exceed or X-Manager for login

Hi,

I have a HP-UX 11.11 server right now we are using putty for login by SSH now we want to the upgrade the Oracle of this server for that we need the connectivity through (Exceed or X-Manager) for GUI.

Somebody please help me how can we connect this server by Exceed or X-Manager


Thanks

Bhupal
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. Solaris

Help with Exceed

Hi, I need help with operating exceed from a local computer to a solaris machine using putty. putty - version 60 Hummingbird Xserver for win 32 version 7.1.0.0 Communication mode is set to 'passive' in exceed Following are the steps that I followed Start 'Exceed' Opened putty... (7 Replies)
Discussion started by: Jaguar_eyes
7 Replies

2. Solaris

exceed display

PC: WinXP professional 2002, sp2 when i tried to use XDMCP Brodcast, it's not displaying any ip's and when i used XDMCP Query by giving the ip address, i couldn't see any display. In the task manager it's showing the exe as running. what could be the problem? (3 Replies)
Discussion started by: satish@123
3 Replies

3. Solaris

Exceed on Vista ?

Hi there, I have a copy of Exceed 7.0, which I use on my Win XP pro machine to get access to the Solaris CDE, but this version will not run on my Vista laptop. Do I need to get the very latest version of Exceed to run on Vista ? or is there an interim version which I might find on Ebay ? ... (2 Replies)
Discussion started by: Freddo_21
2 Replies

4. UNIX for Advanced & Expert Users

Problem with using Exceed

Hi Gurus I am facing problem in using Exceed to connect to one HP Ux server. I used Exceed (XDMCP-Broadcast) but can't see the IP address of the server I want to connect to. What could be the reason for this ? (Network Connectivity is fine as I can connect using telnet) Then I used Client... (2 Replies)
Discussion started by: Amardeep
2 Replies

5. HP-UX

Exceed Login

I have a number of systems running 11i and 10.2. I need to log in using Exceed V8.0. On all systems, except one, I get the HP CDE screen asking for USER name and password. Upon entering the information, the screen goes away and comes back with the same HP CDE screen, asking again. I have one... (0 Replies)
Discussion started by: old_tex
0 Replies

6. UNIX for Dummies Questions & Answers

Telnet/Exceed

I wanted to know difference between Telnet/Hummingbird- Exceed/FTP. THe reason why i asked the question b'coz i have three cad systems & two are in windows environment & one in unix I wanted to put all three into network & share the data. Which software you wanted to purchase & how could i... (1 Reply)
Discussion started by: kar1
1 Replies

7. Linux

Login Manager

I do not wish to use the Gnome Login Manager anymore, how can I swtich to the KDE login manager? I can already edit the KDE manager in Control Center for KDE, but it doesnt use it. BTW i use KDE 3.1 window manager. One last thing, How can I log into my computer remotly? (2 Replies)
Discussion started by: erhan_j
2 Replies

8. UNIX for Advanced & Expert Users

Exceed

Does anyone know how to get exceed to bring up the CDE in Windows. I have been trying and only get the telnet to come up. (2 Replies)
Discussion started by: aojmoj
2 Replies

9. UNIX for Dummies Questions & Answers

Exceed subsitutions?

Does anyone know if there any application perform better than Exceed? It seems some video card doesn't support Exceed. thx (1 Reply)
Discussion started by: E-Quality
1 Replies
Login or Register to Ask a Question
RLOGIND(8)						      System Manager's Manual							RLOGIND(8)

NAME
rlogind, in.rld - remote login server SYNOPSIS
login stream tcp nowait root /usr/sbin/in.rld in.rld tcpd login /usr/sbin/in.rld DESCRIPTION
Rlogind is the server for the rlogin(1) program. The server provides a remote login facility with authentication based on privileged port numbers from trusted hosts. Rlogind listens for service requests at the port indicated in the ``login'' service specification; see services(5). When a service request is received the following protocol is initiated: 1) The server checks the client's source port. If the port is not in the range 0-1023, the server aborts the connection. 2) The server checks the client's source address and requests the corresponding host name (see gethostbyaddr(3), hosts(5) and named(8)). If the hostname cannot be determined, the dot-notation representation of the host address is used. Once the source port and address have been checked, rlogind allocates a pseudo terminal (see tty(4)), and manipulates file descriptors so that the slave half of the pseudo terminal becomes the stdin , stdout , and stderr for a login process. The login process is an instance of the login(1) program, invoked with the -r option. The login process then proceeds with the authentication process as described in rshd(8), but if automatic authentication fails, it reprompts the user to login as one finds on a standard terminal line. The parent of the login process manipulates the master side of the pseduo terminal, operating as an intermediary between the login process and the client instance of the rlogin program. In normal operation, the packet protocol described in tty(4) is invoked to provide ^S/^Q type facilities and propagate interrupt signals to the remote programs. The login process propagates the client terminal's baud rate and terminal type, as found in the environment variable, ``TERM''; see environ(7). The screen or window size of the terminal is requested from the client, and window size changes from the client are propagated to the pseudo terminal. SEE ALSO
rlogin(1). 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. ``Try again.'' A fork by the server failed. ``/bin/sh: ...'' The user's login shell could not be started. BUGS
The authentication procedure used here assumes the integrity of each client machine and the connecting medium. This is insecure, but is useful in an ``open'' environment. A facility to allow all data exchanges to be encrypted should be present. A more extensible protocol should be used. 4.2 Berkeley Distribution May 24, 1986 RLOGIND(8)