It seems that the card itself does not support auto-nego.
It your card is a 100BaseT card, try to connect to 100BaseT switch,
it that is 10BaseT card, try to connect to 10BaseT Switch....
Or set the "other end" to auto-nego.
Anyone could help me too?
Quote:> Server is AlphaServer 1200. I can ping my IP address, but nothing
> else. Networking was working before the install of 7.2. Switch port is
> set for 10BaseT, half duplex. Windows NT onnected to same switch port
> works fine.
Andrew Schultz | The views expressed might
http://www4.ncsu.edu/~ajschult/ | They are however, correct.
The tulip module works better for me. de4x5 doesn't really want to doQuote:> you might try the de4x5 module instead of the tulip one. It's getting
> the job done on our machines with tulip cards.
>> you might try the de4x5 module instead of the tulip one. It's getting
>> the job done on our machines with tulip cards.
> The tulip module works better for me. de4x5 doesn't really want to do
> full duplex. This is with 21143 and 21040 chips.
I am sort of in the same boat. On my local network I have some "real
DEC tulip" NICs, both on Alpha and x86, which worked fine with a 'tulip'
driver in 2.2 series of kernels. OTOH 'de4x5' driver had troubles
and some other tulip cards (PNIC series in particular) refused to work
at all. Drivers in 2.4 series fixed these problems for many users
and networks but in my particular setup they refuse to pass through
a single ethernet packet. Still 'de4x5' started to work rather nicely
instead. Shrug! Just experiment a bit what works best in your situation.
tar xfvz netdrivers.tgz
There is also a Tulip Mailing List available from the website above.
We just got a dedicated server that for now is running fine for
all our purposes except for the e-mail. The machine has RedHat 7.2
For the purpose of this message, I'm going to use www.example.com
as the name of that server (not being sure if sendmail is properly
configured, I don't want to write an open invitation to hackers
into our machine :-))
So, the web hosters (the guys that have the machine and did the
setup) already created the MX record in their DNS -- in fact,
if I do ping mail.example.com, the machine responds, and the
IP is the same IP as www.example.com
I followed the RedHat-ISP-Setup-HOWTO on www.linux.org; they
suggest that sendmail and the popper (I'm using the one they
recommend, Qualcomm's popper -- current version is 4.0.4) be
run via xinetd, instead of directly through the init scripts
I did the changes in the sendmail.cf file, also in sendmail.cw,
where I put:
Then I restart xinetd (running /etc/init.d/xinetd restart), but
no effect: I can't connect, neither to port 25, nor port 110.
I tried from the same host, from other hosts, all of these
telnet mail.example.com 25
telnet example.com 25
telnet www.example.com 25
(and same thing for port 110), but nothing -- I get connection
refused in every single case.
Any kind sould could point out what I'm missing, or what I
may be doing wrong? Any pointers to "easy-to-understand"
documentation would also be appreciated (I know easy-to-understand
is a relative term... Let's say that I found that section of
the ISP-Setup-RedHat-HOWTO very easy to understand... Well,
maybe I did *not* understand it? :-))
Thanks in advance !!!