/etc/nsswitch.conf determines the order that various datasources that map names and IPs are used. If you don't have any uncommented entries in that, I suppose that means that whatever the system default happens to be is in use. Often, the commented entries show you what that default is.
I would try editing nsswitch.conf to have a line like this:
That should cause /etc/hosts to be used before a DNS lookup is performed.
I can ping other computers in my office. I can telnet other users in my office but i cannot get out of the office network. If i try to go out side of my network it cannot find host.
Any ideas? (5 Replies)
Hi,
Can anybody help me out why l can't not ping my server with Openserver 5.0.4 with my windows machine from a remote site.
The machine could see the local LAN with the Router however, i can't ping or telnet unto the server from another site on the WAN. The default gateway was configure on the... (0 Replies)
Hi All,
We are not able to ping to a AIX box...Network is ok..when we give ping from that AIX box..it is giving 0821-067 ping: The socket creation call failed.there is no enough buffer space for the requested socket operation.
refresh -s inetd is also giving socket error.
Please help to... (1 Reply)
I have one problem and it is giving me hard time
I can ping my windows machine
root@x1ChXpress:/sbin
>ping 192.168.129.66
192.168.129.66 is alive
root@x1ChXpress:/sbin
>netstat -rn
Routing Table:
Destination Gateway Flags Ref Use Interface... (3 Replies)
We have a Sun Solaris Netra 20 server. Our O&M Server gets Alarm Processor
not responding. When Alarm occurs, you can ping the sun server but cannot telnet it. We keep getting Interrupt level not serviced. var/adm/message log is
> tail -f messages
Apr 12 20:09:56 cama pcisch: PCI-device:... (9 Replies)
Hello for all!
This is the situation:
I must create many users that only can execute telnet and ping.
Create users is not a problem, but I donīt know how limit the users privileges, to only execute telnet and ping.
I hope you can help me.
Thank's for all.
Bye :)
PD: Sorry for my... (4 Replies)
Hi,
After a crash of our older AIX server it happend as it is in the title:
ping is ok, but telnet:
What it can be this strange thing?
Franci (2 Replies)
Hello,
I need help, I have the following which save in the result file ping and telnet:port test.
Basically the script works but I should implement a check on ping and telnet command so that ping has 5 seconds threshold and telnet (more important) 10 seconds. Over that threshold ping and... (0 Replies)
I put this thread to shell and bsd, because I want to resolve this matter on bsd.
May somebody can explain to me how to ping a remote server, in unix. BTW the following code examples were tried on a linux system as well, with the same output, nothing. But on my bsd are not installed nmap neither... (4 Replies)
Discussion started by: 1in10
4 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)