12-05-2010
Remote Access using GUI from one Solaris to another one
hi gyus, i'm trying to login trough GUI (using login screen, instead to login to locahost I login to remote host) from on Solaris 10 to another one.
You know, I see the remote host in the host list, but It's not possible to login since the screen keeps black and after that get back to the former login screen.
I checked using Xmanager from one Windows PC to the remote one, and I did't, so it's not a issue related to security.
how I could login without using Windows PC?
Thanks!
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi
I need to access files from a specific folder of a Linux system from an another Linux System Remotely.
I know how to, Export a folder on One SCO System & can access the same by using Import via., NFS in the Sco Unix SVR4 System using the scoadmin utility.
Also, I know to use mount -t ... (2 Replies)
Discussion started by: S.Vishwanath
2 Replies
2. UNIX for Dummies Questions & Answers
i need to know how i would go about accessing my floppy disks, cd's and flash drives on my command prompt unix system (1 Reply)
Discussion started by: carlvernon
1 Replies
3. Shell Programming and Scripting
hey guys, i am on a box named pluto and i need to be able to log into another box named genesis. i need to be able to ssh into genesis as root and not get asked for the password. what file do i need to edit on genesis to make this happen? i searched for the .rhosts file it doesn't seem to exist.... (1 Reply)
Discussion started by: Terrible
1 Replies
4. Linux
Hello,
I need a tool for remote GUI connection to Linux machine ,something like remote Desktop in windows?????any help
Thanks in advance (4 Replies)
Discussion started by: mm00123
4 Replies
5. UNIX for Dummies Questions & Answers
Hey, how do I access the desktop gui for a remote fedora box?
$ ssh user@ip
$ xinit
Fatal server error:
Server is already active for display 0
If this server is no longer running, remove /tmp/.X0-lock
and start again.
Thanks (1 Reply)
Discussion started by: JustinT
1 Replies
6. UNIX for Dummies Questions & Answers
All,
I am looking for the easiest solution that will let me remote access from a Windows 2000 client into a Solaris 8 server. Any suggestions?
Thanks Kevin (3 Replies)
Discussion started by: Kevin1166
3 Replies
7. Debian
Hi,
I've been looking for a way to execute a console program (is in windows but by now I accept the linux way) from a linux machine, but this program has to be opened in the remote side. Linux machine acts only as a "signaling" host. My program has to open the camera in the remote side, but only... (7 Replies)
Discussion started by: zauberberg
7 Replies
8. Solaris
Hi all;
I'm looking for free access to the Solaris operating system. I have no way to install at home (even on a virtual machine).
I been developing BOINC project (OProject@Home: site: oproject.goldbach.pl). I would like to compile and test programs on Solaris.
Can someone provide a... (9 Replies)
Discussion started by: Rysiu
9 Replies
9. Red Hat
Greetings!
Theres an application in my RHEL 6 server that has a GUI (which we'd like to use). When I run the AppGui.sh is says it needs Server X11.
I know its gotta do something with X server (and I installed it).I found some tutorial for auto configuration and then I was supposed to access... (0 Replies)
Discussion started by: RedSpyder
0 Replies
10. Red Hat
Hi All,
I've been looking at various options at administering several servers remotely like:
- VNC (don't like the lax security of 8 characters max for a password) and
- NX (awesome piece of kit but still limited to a per desktop viewer)...
What I'm looking for is a GUI that... (7 Replies)
Discussion started by: ASGR
7 Replies
LEARN ABOUT NETBSD
hosts.equiv
HOSTS.EQUIV(5) BSD File Formats Manual HOSTS.EQUIV(5)
NAME
hosts.equiv, .rhosts -- trusted remote hosts and host-user pairs
DESCRIPTION
The hosts.equiv and .rhosts files list hosts and users which are ``trusted'' by the local host when a connection is made via rlogind(8),
rshd(8), or any other server that uses ruserok(3). This mechanism bypasses password checks, and is required for access via rsh(1).
Each line of these files has the format:
hostname [username]
The hostname may be specified as a host name (typically a fully qualified host name in a DNS environment) or address, ``+@netgroup'' (from
which only the host names are checked), or a ``+'' wildcard (allow all hosts).
The username, if specified, may be given as a user name on the remote host, ``+@netgroup'' (from which only the user names are checked), or a
``+'' wildcard (allow all remote users).
If a username is specified, only that user from the specified host may login to the local machine. If a username is not specified, any user
may login with the same user name.
EXAMPLES
somehost
A common usage: users on somehost may login to the local host as the same user name.
somehost username
The user username on somehost may login to the local host. If specified in /etc/hosts.equiv, the user may login with only the same
user name.
+@anetgroup username
The user username may login to the local host from any machine listed in the netgroup anetgroup.
+
+ +
Two severe security hazards. In the first case, allows a user on any machine to login to the local host as the same user name. In the
second case, allows any user on any machine to login to the local host (as any user, if in /etc/hosts.equiv).
WARNINGS
The username checks provided by this mechanism are not secure, as the remote user name is received by the server unchecked for validity.
Therefore this mechanism should only be used in an environment where all hosts are completely trusted.
A numeric host address instead of a host name can help security considerations somewhat; the address is then used directly by iruserok(3).
When a username (or netgroup, or +) is specified in /etc/hosts.equiv, that user (or group of users, or all users, respectively) may login to
the local host as any local user. Usernames in /etc/hosts.equiv should therefore be used with extreme caution, or not at all.
A .rhosts file must be owned by the user whose home directory it resides in, and must be writable only by that user.
Logins as root only check root's .rhosts file; the /etc/hosts.equiv file is not checked for security. Access permitted through root's
.rhosts file is typically only for rsh(1), as root must still login on the console for an interactive login such as rlogin(1).
FILES
/etc/hosts.equiv Global trusted host-user pairs list
~/.rhosts Per-user trusted host-user pairs list
SEE ALSO
rcp(1), rlogin(1), rsh(1), rcmd(3), ruserok(3), netgroup(5)
HISTORY
The .rhosts file format appeared in 4.2BSD.
BUGS
The ruserok(3) implementation currently skips negative entries (preceded with a ``-'' sign) and does not treat them as ``short-circuit'' neg-
ative entries.
BSD
November 26, 1997 BSD