04-25-2012
Are both servers connected to the same switch. There is a feature on some switches where machines can ping the default router but not between each other... is called port protected.
Do you have a third machine to test on the same net?
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
i am running a linux redhat machine here and am interested in learning some deeper more sophisticated comands in solaris. can someone show me some free sites that allows people to telnet into their (solaris) machines to use for practice?? (1 Reply)
Discussion started by: TRUEST
1 Replies
2. Solaris
I have a solaris 10 x86 installed on a VMware server. It has been runing well for a couple weeks, but started to have network connectivity issue since last week. The network card seems to be up and down every one minute. So I got connection closed after I sshed to it for about one minute.
#... (2 Replies)
Discussion started by: fredao
2 Replies
3. AIX
Hello All,
I believe my NIM master is fine. lsnim and cat /etc/niminfo gives me the right output. While doing "lsnim" on a client machine, I get ksh:lsnim:"not found".
Please someone be nice enough to explain what are the steps to verify the master and client connectivity to do all the NIM... (3 Replies)
Discussion started by: solaix14
3 Replies
4. UNIX for Advanced & Expert Users
Hi guys,
I had two computer which is one with vista and other one with fedora and they are connected via one router.
from vista to fedora is fine.. I can ping or connect via putty using Ip address but I couldn't connect putty using hostname/domain.
If I typed in fedora the hostname,... (0 Replies)
Discussion started by: peac3
0 Replies
5. IP Networking
System: Dell Desktop w/ 2 SATA drives running Ubuntu 9.10 that uses 2 ethernet cards, 1 for internet connectivity and another to interface the machine with a high voltage power supply which supports ssh and EPICS controls. Second Ethernet card is connected to a NetGear WNR3500 router, the VME... (0 Replies)
Discussion started by: henslewm
0 Replies
6. UNIX for Advanced & Expert Users
Hi
I have two machines Mac1 and Mac2 logging in with same user id and same private key.
can anyone let me know how to connect these two machine using ssh .
or SCP files to other machine
:wall: (1 Reply)
Discussion started by: madankumar
1 Replies
7. UNIX for Dummies Questions & Answers
Hi,
I have two machines. M1 and M2 and having a generic id catadm, these two machines having common mount of /u/catadm directory.
with this setup, ssh autologin is failing for me and asking me to enter password when i try autologin using this generc id from M1 to M2
catadm-M1$ ssh... (3 Replies)
Discussion started by: rbalaj16
3 Replies
8. Solaris
:wall:
Hello Solaris Users. Although a fundamental skill I am still new to connecting computers together in order that they can see each other, ie. via ping-ing of IP's and/or hostnames.
I wish to install Oracle 10g database on Sun Blade 1500 and access this from Windows XP laptop (running... (5 Replies)
Discussion started by: patcom
5 Replies
9. AIX
Hello Everyone
We have purchased IBM Pureflex chassis with 5 P460 blades. We have configured each blade with dual vios and 4 vio clients. VIOS installation and vio client installation and configuration was completed successfully.
When we tried to connect the network cables from Pureflex... (2 Replies)
Discussion started by: yuvarakasil
2 Replies
LEARN ABOUT REDHAT
atalkd
ATALKD(8) System Manager's Manual ATALKD(8)
NAME
atalkd - AppleTalk RTMP, NBP, ZIP, and AEP manager
SYNOPSIS
/usr/sbin/atalkd [ -f configfile ] [ -1 | -2 ]
DESCRIPTION
atalkd is responsible for all user level AppleTalk network management. This includes routing, name registration and lookup, zone lookup,
and the AppleTalk Echo Protocol (similar to ping(8)). atalkd is typically started at boot time, out of /etc/rc. It first reads from its
configuration file, /etc/atalk//atalkd.conf. If there is no configuration file, atalkd will attempt to configure all available interfaces
and will create a configuration file. The file consists of a series of interfaces, one per line. Lines with `#' in the first column are
ignored, as are blank lines. The syntax is
interface [ -seed ] [ -phase number ] [ -net net-range ] [ -addr address ] [ -zone zonename ] ...
Note that all field except the interface are optional. The loopback interface is configured automatically. If -seed is specified, all
other fields must be present. Also, atalkd will exit during bootstrapping, if a router disagrees with its seed information. If -seed is
not given, all other information may be overriden during auto-configuration. If no -phase option is given, the default phase as given on
the command line is used (the default is 2). If -addr is given and -net is not, a net-range of one is assumed.
The first -zone directive for each interface is the ``default'' zone. Under Phase 1, there is only one zone. Under Phase 2, all routers
on the network are configured with the default zone and must agree. atalkd maps ``*'' to the default zone of the first interface. Note:
The default zone for a machine is determined by the configuration of the local routers; to appear in a non-default zone, each service, e.g.
afpd, must individually specify the desired zone. See also nbp_name(3).
ROUTING
If you are connecting a netatalk router to an existing AppleTalk internet, you should first contact your local network administrators to
obtain appropriate network addresses.
atalkd can provide routing between interfaces by configuring multiple interfaces. Each interface must be assigned a unique net-range
between 1 and 65279 (0 and 65535 are illegal, and addresses between 65280 and 65534 are reserved for startup). It is best to choose the
smallest useful net-range, i.e. if you have three machines on an Ethernet, don't chose a net-range of 1000-2000. Each net-range may have
an arbitrary list of zones associated with it.
EXAMPLE
Below is an example configuration file for a sun4/40. The machine has two interfaces, ``le0'' and ``le1''. The ``le0'' interface is con-
figured automatically from other routers on the network. The machine is the only router for the ``le1'' interface.
le0
le1 -seed -net 9461-9471 -zone netatalk -zone Argus
atalkd automatically acts as a router if there is more than one interface.
FILES
/etc/atalk//atalkd.conf configuration file
BUGS
On some systems, atalkd can not be restarted.
netatalk 1.3 17 Nov 1995 ATALKD(8)