01-01-2007
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 ?
Last edited by sak900354; 01-01-2007 at 09:35 AM..
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
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. 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. Solaris
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
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. UNIX for Advanced & Expert Users
I have setup a Linux machine on my server but for some reason Im unable to reach my default gateway. This is causing me to not communicate with the outside world (unable to connect to CentOS repos)
# ifconfig
enp0s3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet... (3 Replies)
Discussion started by: Junaid Subhani
3 Replies
xna(4) Kernel Interfaces Manual xna(4)
Name
xna - DEBNI and DEMNA Ethernet interfaces
Syntax
device xna0 at vaxbi? node? vector xnaintr (DEBNI)
device xna0 at xmi? node? vector xnaintr (DEMNA)
Description
The driver provides access to a 10 Mbytes Ethernet network through the DEBNI and DEMNA adapters. The DEBNI is an Ethernet to BI bus. The
DEMNA is an Ethernet to XMI adapter.
The host's Internet address is specified at boot time with an SIOCSIFADDR ioctl. The driver employs the Address Resolution Protocol, as
described in to map dynamically between Internet and Ethernet addresses on the local network.
The driver normally tries to use a trailer encapsulation to minimize copying data on input and output. This can be disabled for an inter-
face by setting the IFF_NOTRAILERS flag with an SIOCSIFFLAGS ioctl. Trailers are used only for packets destined for Internet hosts.
The SIOCSPHYSADDR ioctl can be used to change the physical address of the adapter and SIOCRPHYSADDR can be used to read its physical
address. SIOCADDMULTI and SIOCDELMULTI can be used to add or delete multicast addresses. The driver supports a maximum of 12 multicast
addresses. The argument to the latter ioctls is a pointer to an ``ifreq'' structure found in
SIOCRDCTRS and SIOCRDZCTRS ioctls can be used to read or read and clear network counters. The argument to the latter two ioctls is a
pointer to a counter structure ``ctrreq'' found in
The ioctls SIOCENABLBACK and SIOCDISABLBACK can be used to enable and disable the interface loopback mode.
Restrictions
The PUP protocol family is not supported.
Diagnostics
xna%d: port self-test failed:<register list>
Adapter did not pass the power-up self-test during autoconfiguration time. The port attachment fails.
xna%d: couldn't allocate...
The driver was unable to allocate memory for adapter data structures. The port attachment fails.
xna%d: port probe failed:<register list>
The driver was unable to bring the adapter into the initialized state. The port attachment fails.
xna%d: port init failed:<register list>
The driver failed to prepare the adapter for runtime use.
xna%d: port state changed, resetting:<register list>
The adapter issued a port state change interrupt. The port state is reset.
xna%d: port reset failed
The driver was unable to bring the adapter into the initialized state during a port reset.
xna%d: command failed, error code:<error code>
The adapter port command failed. The error code gives reason for failure.
xna%d: couldn't handle af%d
A packet with an undefined protocol type has been sent to the adapter.
xna%d: addmulti failed, multicast list full
Too many multicast requests have been made.
See Also
arp(4p), inet(4f), intro(4n)
xna(4)