Sponsored Content
Full Discussion: Unable to ping New server
Operating Systems Solaris Unable to ping New server Post 302467394 by suresh_krish on Friday 29th of October 2010 07:38:35 AM
Old 10-29-2010
Unable to ping New server

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
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Unable to ping host

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

unable ping ipaddress

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

UNable to find ping command

HI, I am new to unix. I have used some basic commands and written some simple shell scripts in teh past. Currently, I am supposed to write a script to continuosly check if a couple of machines are up and if not to start a script. I am using a bash - 2.03. I have tryying to use the ping command... (3 Replies)
Discussion started by: swepaul
3 Replies

4. UNIX for Dummies Questions & Answers

unable to ping

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

5. IP Networking

Unable to ping the gateway IP itself

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

6. Solaris

unable to ping server

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

7. IP Networking

unable to ping to my server

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

8. Solaris

Unable to ping Windows

Hello, Am unable to ping the Windows Box, from my Solaris Box. They both are in same LAN, have the same IP Segments. Windows IP :: 10.141.14.120 Solaris IP :: 10.141.14.11 Unable to get why isnt working out.... When using the command 'ping 10.141.14.120', it gives the error as 'ping:... (4 Replies)
Discussion started by: jayanto
4 Replies

9. AIX

Unable to ping localhost

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

10. Solaris

Solaris 9 - Unable to ping a particular server, traceroute also displays * * *

Hi All, I am new to solaris environment and we are using Solaris 9 The problem is am unable to ping a particular server from from one of the solaris server The traceroute also shows only * * * for all the 30 hops I tried to check all the settings like 1) /etc/hosts -> contains the... (17 Replies)
Discussion started by: Sanjay255
17 Replies
YPBIND(8)							     ypbind-mt								 YPBIND(8)

NAME
ypbind - NIS binding process SYNOPSIS
ypbind [-c] [-d | -debug] [-verbose] [-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/binding 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 syslog(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 loopback. -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 standard error. -verbose Causes ypbind to syslog(2) any and all changes in the server its bound to. -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 reacheable, is 20 seconds. With this options another frequency in seconds can be specified. -no-dbus Disables DBUS support if compiled in. --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@thkukuk.de>. ypbind-mt 06/19/2009 YPBIND(8)
All times are GMT -4. The time now is 02:37 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy