Since I don't know NT, I can't offer suggestions about how to check that
side of it. One thing, though: you don't mention anywhere trying to ping the
Linux host from the NT host. That makes me wonder if you've set up the NT
host with an IP address and such. If not, that's why it won't reply to a
Linux ping -- it doesn't know its "own" IP address.
So I think I'd begin, were I in your shoes, checking the NT host config --
are the right address/netmask/broadcast assigned? Can you ping, telnet,
http, whatever FROM it TO the Linux host? A Linux list might not be the best
place to get instructions on how do a basic TCP/IP setup on an NT host ... I
certainly don't know enough to provide it ... but surely there is a similar
source of advice for NT somewhere (or maybe someone else on this list knows
enough to help with the NT part?).
On the Linux side, here are a few things to check:
1. Does ifconfig report the eth0 port as correctly configured? Probably it
will, since you get outgoing traffic on the relevant port. (Or am I reading
this wrong? My hub, and all others I've used, has 2 lights per port -- one
that's on whenever an active NIC is connected to the port, the other only
when there's an actual transmission. My comments assume you're referring to
an equivalent to the second, which means that, for example, when you try to
ping from the Linux host to the NT host, the Linux host at least sends the
queries out to the LAN. If I've read this part of your message wrong, the
possibility that eth0 is misconfigured or routing is bad (see #4 below) gets
greater.)
2. In /proc/interrupts, what IRQ is assigned to the NIC (Ethernet card)?
Might it conflict with a serial port (i.e., does it use IRQ 3 or 4)? I've
seen situations where there was a port conflict, and as a result the NIC
could send outgoing packets but not receive incoming ones. A long shot, but
worth a moment to check.
3. Can you ping and telnet to localhost (that is, from the Linux host to the
Linux host)? If so, this pretty much eliminates kernel-related networking
problems.
4. Do you have routing set up correctly? I infer that you have 2 "real" IP
addresses for the two hosts, and since the hub light does come on, I'm
guessing that you have the right route set up for the LAN. But just in case,
what is the output of "route -n" (best checked when you have a dial-up
connection running as well as the LAN link)?
5. When you try to ping 23.7.19.64, does the cursor really "just gives a
blinking cursor", or do you first get a line that looks something like this:
PING 23.7.19.64 (23.7.19.64): 56 data bytes
? Assuming you do, then what happens when you terminate the ping (with
CTRL-C)? Do you get a response like:
5 packets transmitted, 0 packets received, 100% packet loss
? These are the forms of the standard messages an unsuccessful ping attempt
will generate. If you really aren't getting them, tell us more exactly what
you are seeing when you try to ping the NT host from the Linux host.
As to Samba, that is a Linux package that permits Linux hosts to provide
file and print services to NT (and Win9x) clients using the built-in
networking features of Windows. You'll want to get it running to do the
printer sharing, but you won't need it to share the dial-up access (that
only requires IP forwarding on the Linux host, plus whatever you use on it
to establish the dial-up connection).
At 07:31 PM 2/6/99 +0000, Pankil Richards wrote [excerpts only]:
>All I want to do is connect the Linux and NT machines together to share
>the printer and dial-up access (both connected to the Linux machine
>now).
>The Hub LED indicates that Port 2 (the Linux machine) is working. And I
>can "activate" eth0 from Network Configuration in RH 5.2. How can I
>know for sure if Linux is set up correctly. The Port 2 light is on but
>when I ping 23.7.19.64 (NT) it just gives a blinking cursor. No error
>messages.
>
>Under NT when I run the 3Com Diag. Tool and "Test" the NIC and Network,
>Port 1 (NT machine) LED light comes on saying the port is working. From
>here I get screwed up. I don't know what settings to use, i.e.
>Workgroup vs. Domain, IP/Subnet, etc. When I reboot NT, the P1 LED goes
>off and doesn't come back on.
>
>Do I need Samba for this to work? I've been reading all the HOWTO's and
>they're cofusing me even more. Help...
------------------------------------"Never tell me the odds!"---
Ray Olszewski -- Han Solo
762 Garland Drive
Palo Alto, CA 94303-3603
650.321.3561 voice 650.322.1209 fax [EMAIL PROTECTED]
----------------------------------------------------------------
