01-18-2012
You need to clear your fundamentals in UNIX first . I will suggent you study the PATH variable (what, why and how to set ) . The path is like where you search your exe or commands. You can check in wikipedia also.
The PATH Variable in UNIX
This User Gave Thanks to amitranjansahu For This Post:
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi, dear all, I am rather new to Unix and have this problem where I cant seem to ping from 1 host to another. The scenerio is as follows: -
1 QNX host->Eth->1 SCO host
the SCO host is configured with it's IP
the QNX host is configured with another IP
both in the same domain, ie, 172.20.3.XX... (3 Replies)
Discussion started by: gavon
3 Replies
2. UNIX for Dummies Questions & Answers
I have Sco openserver 5.0. It had a 125. ip. I changed it to a 192. ip. was unable to ping the 192. I was told to change it in the
etc/tcp
etc/hosts
files which i did. still unable to ping.
i am getting a message unable to route to host.
I also have an error in my etc/tcp file on line... (1 Reply)
Discussion started by: pdoug76
1 Replies
3. UNIX for Dummies Questions & Answers
DEar all
i am receiving this error on start and then unable to ping
(dlpid): unable to open network adapter driver (/dev/mdi/e3h0)
what to do ? (2 Replies)
Discussion started by: sak900354
2 Replies
4. IP Networking
We are unable to bring one of our linux boxes into the network once it was restarted. But once we stop and start the network service. We are able to ping the gateway and get into network. After a minute or two we get the following reponse for the ping command
64 bytes from 124.168.215.40:... (6 Replies)
Discussion started by: chrisanto_2000
6 Replies
5. Solaris
hi,
I setup a Solaris machine in my server room and my client cannot access it. Can anyone advise?
Test that i have done:
-My client pc cannot ping the server.
-My solaris server cannot ping client
-My solaris server can ping it's gateway
-Another NT machine 1 (10.179.30.26) in the server... (2 Replies)
Discussion started by: skiturn
2 Replies
6. IP Networking
hi,
I setup a Solaris machine in my server room and my client cannot access it. Can anyone advise?
Test that i have done:
-My client pc cannot ping the server.
-My solaris server cannot ping client
-My solaris server can ping it's gateway
-Another NT machine 1 (10.179.30.26) in the... (8 Replies)
Discussion started by: skiturn
8 Replies
7. Solaris
Hi ALL,
I Have installed NEW v240 server through hyper terminal, After installation i unable to ping the server from out side server... i can see no entry in resolve.conf file.. but the server has DNS.. willl that issue.. please guide me ping the server from outside within the same network
bk (1 Reply)
Discussion started by: suresh_krish
1 Replies
8. UNIX for Dummies Questions & Answers
Hi all,
I have a VM on Solaris 10 setup on a windows vista host machine.
1) Vista host i configure
VMnet 1: 10.1.1.10
Mask : 255.255.255.0
Subnet : 10.1.1.2
DNS : 10.1.1.100
2) Solaris on VM
Network device is on Custom(VMNET1)
IP : 10.1.1.4
Mask : 255.255.255.0
... (8 Replies)
Discussion started by: JuveZzZ
8 Replies
9. Windows & DOS: Issues & Discussions
Hello All,
I have searched and searched, but I am not finding any answers. Any help would be very welcome.
I have a home LAN centered around an Untangle gateway (up to date).
I have a Windows 7 PC and a Snow Leopard Mac
I also have two virtualized instances of windows (xp and 7) running... (1 Reply)
Discussion started by: toadtilley
1 Replies
10. AIX
Hi all,
I have gone through many posts related to this issue,but my issue wasn't resolved hence creating new thread.
I am unable to ping localhost.
ping localhost tries to ping localhost which is defined in DNS.
My /etc/hosts has entry for localhost as
127.0.0.1 loopback localhost.
... (8 Replies)
Discussion started by: chpsam
8 Replies
LEARN ABOUT OPENSOLARIS
ad
ad(5) Standards, Environments, and Macros ad(5)
NAME
ad - Active Directory as a naming repository
DESCRIPTION
Solaris clients can obtain naming information from Active Directory (AD) servers.
The Solaris system must first join an AD domain and then add the ad keyword to the appropriate entries in the nsswitch.conf(4) file. The
Solaris system joins the AD domain by using the kclient(1M) utility. The AD name service only supports the naming databases for passwd and
group.
Windows users are not able to log in. The user_attr(4) database has no entries for Windows users, and the passwd(1) command does not sup-
port the synchronization of user passwords with AD.
The Solaris AD client uses auto-discovery techniques to find AD directory servers, such as domain controllers and global catalog servers.
The client also uses the LDAP v3 protocol to access naming information from AD servers. The AD server schema requires no modification
because the AD client works with native AD schema. The Solaris AD client uses the idmap(1M) service to map between Windows security identi-
fiers (SIDs) and Solaris user identifiers (UIDs) and group identifiers (GIDs). User names and group names are taken from the sAMAccountName
attribute of the AD user and group objects and then tagged with the domain where the objects reside. The domain name is separated from the
user name or group name by the @ character.
The client uses the SASL/GSSAPI/KRB5 security model. The kclient utility is used to join the client to AD. During the join operation,
kclient configures Kerberos v5 on the client. See kclient(1M).
FILES
/etc/nsswitch.conf Configuration file for the name-service switch.
/etc/nsswitch.ad Sample configuration file for the name-service switch configured with ad, dns and files.
/usr/lib/nss_ad.so.1 Name service switch module for AD.
SEE ALSO
passwd(1), svcs(1), idmap(1M), idmapd(1M), kclient(1M), svcadm(1M), svccfg(1M), svccfg(1M), nsswitch.conf(4), user_attr(4), smf(5)
SunOS 5.11 22 Oct 2008 ad(5)