Sponsored Content
Full Discussion: Sco Unix network issues
Operating Systems SCO Sco Unix network issues Post 53176 by RTM on Wednesday 7th of July 2004 10:40:14 AM
Old 07-07-2004
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

SCO Unix and Two Network Cards

Our shops server runs SCO Openserver 5 release 5. It has two network cards in it (one on 10.0.0.6 and one on 90.0.0.99). When I run scoadmin and look at the network settings it show both my 3com network cards and a loop back driver http://theentertainer.com/james/untitled.jpg Can anyone tell... (1 Reply)
Discussion started by: potter
1 Replies

2. SCO

Tape drive issues with SCO 5.0.5!!!

Hi Don't know if anyone will be able to help, but we're currently having problems with our external tape drive on our SCO server. If I try the following command for instance, "tar cvf /dev/rStp0", the tape drive jumps into action for a while, then comes back with the error "tar: cannot open:... (3 Replies)
Discussion started by: mattingg
3 Replies

3. SCO

SCO Unix Network Configuration

Hello Guys, We have an old PC running on SCO Unix V. Is there any sites where i can get manual/procedures on how to install and configure Network. Thanks (2 Replies)
Discussion started by: nrcuevas
2 Replies

4. UNIX for Dummies Questions & Answers

Network printer issues

Hello, I have been having a problem with printing to a network printer on my LAN, I am able to ping all ports from the server and the printer. Print request just stay in the print que the only way to print is from the parallel line to the server. Any ideas on what can be going wrong?? Lp sched is... (1 Reply)
Discussion started by: ostac
1 Replies

5. UNIX for Dummies Questions & Answers

Check for network issues

Hi all, How do i check for network issues on a server (solaris & linux) - interms of connectivity, collision, congestion, whatever that's impacting the connection to/from the server? Please advise. Thanks. :confused: (4 Replies)
Discussion started by: greencored
4 Replies

6. HP-UX

Network Connectivity Issues

Newbie with UNIX here. Currently troubleshooting a UNIX terminal we have. I determined it to be bad and swapped it out with a known good terminal. I went in and changed the IP address and host name to reflect the old terminal. Although now there is no connectivity. I swapped out the NIC... (1 Reply)
Discussion started by: kevinlord190
1 Replies

7. SCO

Configuare Network SCO UNIX 5.0.7 on Vmware

hi i installed sco unix open server 5.0.7 on virtual machine vmware and runing it, its work perfect and good. now how i can configuare network at scoadmin that i able to access nework ? ---------- Post updated at 08:56 AM ---------- Previous update was at 01:47 AM ---------- nobody can... (2 Replies)
Discussion started by: farzad226
2 Replies

8. SCO

Can not recognize network adapter SCO UNIX in HP z400

hi .I've installed an operating system SCO in HP Z400 and network cards ZyXEL model FN312 with Chipset RTL8139D put it on .network card installed but do not display network card with command ifconfig -a in list and just show loopback. show message : dlpid:unable to open network adapter driver... (14 Replies)
Discussion started by: moein.mojtaba
14 Replies

9. Emergency UNIX and Linux Support

Network related issues

Oflate we are finding a few servers experiencing severe slowness. What would be the commands that I need to try to postmortem the situation? (3 Replies)
Discussion started by: ggayathri
3 Replies
XHOST(1)						      General Commands Manual							  XHOST(1)

NAME
xhost - server access control program for X SYNOPSIS
xhost [[+-]name ...] DESCRIPTION
The xhost program is used to add and delete host names or user names to the list allowed to make connections to the X server. In the case of hosts, this provides a rudimentary form of privacy control and security. It is only sufficient for a workstation (single user) environ- ment, although it does limit the worst abuses. Environments which require more sophisticated measures should implement the user-based mechanism or use the hooks in the protocol for passing other authentication data to the server. OPTIONS
Xhost accepts the following command line options described below. For security, the options that affect access control may only be run from the "controlling host". For workstations, this is the same machine as the server. For X terminals, it is the login host. -help Prints a usage message. [+]name The given name (the plus sign is optional) is added to the list allowed to connect to the X server. The name can be a host name or a user name. -name The given name is removed from the list of allowed to connect to the server. The name can be a host name or a user name. Existing connections are not broken, but new connection attempts will be denied. Note that the current machine is allowed to be removed; however, further connections (including attempts to add it back) will not be permitted. Resetting the server (thereby breaking all connections) is the only way to allow local connections again. + Access is granted to everyone, even if they aren't on the list (i.e., access control is turned off). - Access is restricted to only those on the list (i.e., access control is turned on). nothing If no command line arguments are given, a message indicating whether or not access control is currently enabled is printed, fol- lowed by the list of those allowed to connect. This is the only option that may be used from machines other than the controlling host. NAMES
A complete name has the syntax ``family:name'' where the families are as follows: inet Internet host (IPv4) inet6 Internet host (IPv6) dnet DECnet host nis Secure RPC network name krb Kerberos V5 principal local contains only one name, the empty string si Server Interpreted The family is case insensitive. The format of the name varies with the family. When Secure RPC is being used, the network independent netname (e.g., "nis:unix.uid@domainname") can be specified, or a local user can be specified with just the username and a trailing at-sign (e.g., "nis:pat@"). For backward compatibility with pre-R6 xhost, names that contain an at-sign (@) are assumed to be in the nis family. Otherwise they are assumed to be Internet addresses. If compiled to support IPv6, then all IPv4 and IPv6 addresses returned by getaddrinfo(3) are added to the access list in the appropriate inet or inet6 family. Server interpreted addresses consist of a case-sensitive type tag and a string representing a given value, separated by a colon. For exam- ple, "si:hostname:almas" is a server interpreted address of type hostname, with a value of almas. For more information on the available forms of server interpreted addresses, see the Xsecurity(7) manual page. DIAGNOSTICS
For each name added to the access control list, a line of the form "name being added to access control list" is printed. For each name removed from the access control list, a line of the form "name being removed from access control list" is printed. FILES
/etc/X*.hosts SEE ALSO
X(7), Xsecurity(7), Xserver(1), xdm(1), xauth(1), getaddrinfo(3) ENVIRONMENT
DISPLAY to get the default host and display to use. BUGS
You can't specify a display on the command line because -display is a valid command line argument (indicating that you want to remove the machine named ``display'' from the access list). The X server stores network addresses, not host names, unless you use the server-interpreted hostname type address. If somehow you change a host's network address while the server is still running, and you are using a network-address based form of authentication, xhost must be used to add the new address and/or remove the old address. AUTHORS
Bob Scheifler, MIT Laboratory for Computer Science, Jim Gettys, MIT Project Athena (DEC). X Version 11 xhost 1.0.3 XHOST(1)
All times are GMT -4. The time now is 03:02 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy