Sponsored Content
Operating Systems Linux Red Hat Nslookup working but ping not working at windows client Post 302890702 by rbatte1 on Friday 28th of February 2014 06:21:07 AM
Old 02-28-2014
Please put your output in CODE tags. It makes it far easier to read. You might need to write the :D in [NOPARSE]:D[/NOPARSE] tags to avoid it putting in the big grin as part of a MAC address.

You haven't given us the output of a ping. It would be good to know if you can ping 10.20.203.1 too.



Thanks,
Robin
 

10 More Discussions You Might Find Interesting

1. Solaris

ping -s not working

I have a multipath system with 2 physicals, a virtual and a failsafe. All network connectivity is working fine to and from all of the interfaces and the virtual. The one thing that is not working is 'ping -s'. From this machine, I cannot send and receive packets using ping -s. ping without the... (1 Reply)
Discussion started by: tjlst15
1 Replies

2. Solaris

dns client not working

Hi All, I have configured linux server as local dns server (practice level). I have given the IP and hostname details in /etc/hosts -bash-3.00# cat /etc/hosts # # Internet host table # ::1 localhost 127.0.0.1 localhost 192.168.1.78 dummy.set.com loghost 192.168.1.57 cent.set.com #... (3 Replies)
Discussion started by: vaibhav.kanchan
3 Replies

3. UNIX Desktop Questions & Answers

X windows not working

Hi all, Fedora 10 workstation is not able to login to X windows (GUI).But works fine on command line. Below are command outputs from two workstations: one with problem and another working fine (both are identical in h/w and run fedora core 10). Please help me in this. Thanks in advance! ... (3 Replies)
Discussion started by: lramsb4u
3 Replies

4. UNIX for Advanced & Expert Users

ping by hostname not working

anyone ever seen this problem: I can ping the server by IP address but I can't by hostname. nslookup is working and dns query is ok. # nslookup mwxnsb24 Server: 10.11.49.206 Address: 10.11.49.206#53 Name: mwxnsb24 Address: 10.10.58.175 # ping... (8 Replies)
Discussion started by: linuxgeek
8 Replies

5. Solaris

my sun solaris 10 cannot ping and nslookup other server using hostname.

hi.... i have sun solaris 10 server, fedora 10, and Windows Server.. i cant ping my sun solaris 10, fedora 10 and Windows Server using hostname (etc: ping winserver.bengkel2.com), but i can ping all using IPV4 and IPV6 address.. can u give some suggestion to solve my problem or some idea to... (3 Replies)
Discussion started by: izuan_7657
3 Replies

6. HP-UX

nslookup/ping resolve problem 11i v3

I am having a problem with a new server build that has got me completely baffled. This server has a private back end network so the way it is supposed to work is that the server thinks its ip address is 10.131.0.48 but the rest of the world knows it as 199.68.100.100 per DNS. It has to be this way... (2 Replies)
Discussion started by: keelba
2 Replies

7. Shell Programming and Scripting

Perl : ping for multiple IPs not working

I have written perl ping program to ping list of IPs one by one and print the status.But each and every time it is showing the status as Pass for all IPs even though the IP is wrong. multipleip.pl use Net::Ping; $p = Net::Ping->new(); $ifile="inventory.txt"; ... (2 Replies)
Discussion started by: scriptscript
2 Replies

8. UNIX for Dummies Questions & Answers

Yum not working on client while able to do the ftp

1)check vsftpd service is running service vsftpd status 2)mkdir -p /var/ftp/pub/Packages Packages will contain all rpm packages 3)copy the xml file to Packages folder #cp -arf /mnt/hgfs/share/RHEL_DVD/Packages /var/ftp/pub/Packages 4)install the 3 required rpm rpm --nodeps -ivh... (0 Replies)
Discussion started by: joj123
0 Replies

9. Solaris

Sudo not working on LDAP client machine

Hi, I have configured ldap manually on solaris 10/11 machine with below entries: # ldapclient list |grep sudo NS_LDAP_SERVICE_SEARCH_DESC= sudoers:ou=SUDOers,dc=exm,dc=ple,dc=com # cat /etc/nsswitch.conf |grep -i sudo sudoers: files ldap # But groups available in LDAP server... (8 Replies)
Discussion started by: Sridaran
8 Replies

10. Shell Programming and Scripting

Nslookup on a variable inside script not working

I am new at scripting. I have a file that each line is the shortname for a server. ie - Server1 Server2 Server3 I want to read in that file, do a nslookup and print the FQDN to a file. I added an echo statement to make sure my variable was being read and changing. But the nslookup... (5 Replies)
Discussion started by: kellyhkc
5 Replies
ypbind(8)						      System Manager's Manual							 ypbind(8)

NAME
ypbind - NIS binding process SYNOPSIS
ypbind [ -c ] [ -d|-debug ] [ -broadcast ] [ -broken-server ] [ -ypset ] [ -ypsetme ] [ -no-ping ] [ -f configfile ] [ -local-only ] [ -ping-interval ping-interval ] [ -no-dbus ] ypbind --version DESCRIPTION
ypbind finds the server for NIS domains and maintains the NIS binding information. The client (normally the NIS routines in the standard C library) could get the information over RPC from ypbind or read the binding files. The binding files resides in the directory /var/yp/bind- ing and are conventionally named [domainname].[version]. The supported versions are 1 and 2. There could be several such files since it is possible for an NIS client to be bound to more than one domain. After a binding has been established, ypbind will send YPPROC_DOMAIN requests to the current NIS server at 20 seconds intervals. If it doesn't get an response or the NIS server reports that he doesn't have this domain any longer, ypbind will search for a new NIS server. All 15 minutes ypbind will check to see if the current NIS server is the fastest. If it find a server which answers faster, it will switch to this server. You could tell ypbind to use network broadcasts to find a new server, what is insecure, or you could give it a list of known secure servers. In this case ypbind will send a ping to all servers and binds to first one which answers. Unless the option -debug is used, ypbind detaches itself from the controlling terminal and puts itself into background. ypbind uses sys- log(3) for logging errors and warnings. At startup or when receiving signal SIGHUP, ypbind parses the file /etc/yp.conf and tries to use the entries for its initial binding. A broadcast entry in the configuration file will overwrite a ypserver/server entry and a ypserver/server entry broadcast. If all given server are down, ypbind will not switch to use broadcast. ypbind will try at first /etc/hosts and then DNS for resolving the hosts names from /etc/yp.conf. If ypbind couldn't reconfigure the search order, it will use only DNS. If DNS isn't available, you could only use IP- addresses in /etc/hosts. ypbind could only reconfigure the search order with glibc 2.x. If the -broadcast option is specified, ypbind will ignore the configuration file. If the file does not exist or if there are no valid entries, ypbind exit. This ypbind version listens for DBUS messages from NetworkManager. If no NetworkManager is running at startup, ypbind will behave as usual and assumes there is a working network connection. If NetworkManager is running on the system, ypbind will only search and provide NIS informations, if NetworkManager tells that a network connection is available. If NetworkManager establishes a connection, ypbind will reread all configuration files, registers at the local portmapper and try to search NIS servers. If NetworkManager drops a connection, ypbind will unregister from portmapper. OPTIONS
-broadcast Send a broadcast to request the information needed to bind to a specific NIS server. With this option, /etc/yp.conf will be ignored. -ypset Allow root from any remote machine to change the binding for a domain via the ypset(8) command. By default, no one can change the binding. This option is really insecure. If you change a binding for a domain, all the current known servers for this domain will be forgotten. If the new server goes down, ypbind will use the old searchlist. -ypsetme The same as -ypset, but only root on the local machine is allowed to change the binding. Such requests are only allowed from loop- back. -c ypbind only checks if the config file has syntax errors and exits. -debug starts ypbind in debug mode. ypbind will not put itself into background, and error messages and debug output are written to stan- dard error. -broken-server lets ypbind accept answers from servers running on an illegal port number. This should usually be avoided, but is required by some ypserv(8) versions. -no-ping ypbind will not check if the binding is alive. This option is for use with dialup connections to prevent ypbind from keeping the connection unnecessarily open or causing autodials. -f configfile ypbind will use configfile and not /etc/yp.conf -local-only ypbind will only bind to the loopback device and is not reachable from a remote network. -ping-interval ping-interval The default value for ypbind to check, if a NIS server is still reachable, is 20 seconds. With this options another frequency in seconds can be specified. -no-dbus Disables DBUS support if compiled int. --version Prints the version number FILES
/etc/yp.conf configuration file. /var/yp/binding/[domainname].[version] binding file containing information about each NIS domain. /var/run/ypbind.pid contains the process id of the currently running ypbind master process. SEE ALSO
syslog(3), domainname(1), yp.conf(5), ypdomainname(8), ypwhich(1), ypserv(8), ypset(8) AUTHOR
ypbind-mt was written by Thorsten Kukuk <kukuk@suse.de>. ypbind-mt Version 1.20.1 August 2006 ypbind(8)
All times are GMT -4. The time now is 07:06 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy