Ray Olszewski wrote:
> Jim -- Hard to say what you've missed because you don't say much about what
> you hit. So some of what I suggest below may be things you've already
> covered but didn't mention here.
>
> First, before we get to real services ... can the Windows hosts ping the
> Linux host? Can the Linux host ping itself (as 127.0.0.1 and as
> 192.168.0.5)? I assume the Windows hosts can communicate among themselves
> all right. If you cannot ping, what lights do you see flashing when you try
> (on the hub or switch, assuming this is a UTP setup, and on the NICs
> themselves)?
Each machine can ping all of the other machines, including the Linux box.
The Linux box can ping itself at either address.
>
> Second, what are the network setting on all the hosts? Not just the
> addresses; the netmasks and gateway addresses as well. ("netstat -nr" on the
> Linux host; I think versions of Windows vary on the command.)
netstat -nr says:
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
192.168.0.0 0.0.0.0 255.255.255.0 U 40 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 40 0 0 lo
0.0.0.0 192.168.0.1 0.0.0.0 UG 40 0 0 eth0
On the "primary" Windows machine, winipcfg shows for the PPP adapter:
IP Address: 208.135.239.133
Subnet Mask: 255.255.255.0
Default Gateway: 208.135.239.133
and for the nic:
IP Address: 192.168.0.1
Subnet Mask: 255.255.255.0
Default Gateway: (blank)
>
> Third, are you running telnet and ftp servers on the Linux host? They
> probably run through inetd. Check first to see that you are running inetd
> ("ps ax | grep inet"). If you are, then see that there are entries for
> telnet and ftp in /etc/inetd.conf, and that the programs they point to are
> present on the system.
shows xinetd is running.
/etc/inetd.conf contains:
ftp stream tcp nowait root /usr/sbin/tcpd /usr/sbin/in.ftpd
telnet stream tcp nowait root /usr/sbin/tcpd /usr/sbin/in.telnetd
>
> Fourth, are you sure the physical connection between the Linux host and the
> LAN is working? The NIC itself is OK (oehtewise the 192.168.0.5 address
> wouldn't work at all), but the fact that the Linux host can connect to its
> http server, but the Windows clients cannot, makes me wonder about the
> physical layer.
Well, ping works. Lights on the hub blink. I had doubts about the nic that
I put in the Linux box, but when I installed RH7.1 it didn't gripe about it.
If ping works, is there still room for doubt?
I don't know if this is a clue or not, but I have an ftp server running on
192.168.0.1 - when I try to log in from the Linux box, it prompts for user
name, but never gets to asking for a password.
>
> Fifth, might there be an IRQ conflict, say with a serial port? What does
> "ifconfig -a" report about the NIC's IRQ and I/O settings? If it uses IRQ 3
> or 4, it will conflict with a serial port (even an *unused* serial port).
Uses IRQ 10.
>
> Finally, are you running any firewalling on the Linux host? What does
> "ipchains -L -n" report? ("ipchains -L -n -v" is more informative but way
> harder to read.)
No firewall (that I know of).
ipchains -L -n -v says:
Chain input (policy ACCEPT):
target prot opt source destination ports
ACCEPT udp ------ 192.168.0.1 0.0.0.0/0 53 -> *
ACCEPT all ------ 0.0.0.0/0 0.0.0.0/0 n/a
REJECT tcp -y---- 0.0.0.0/0 0.0.0.0/0 * -> 0:1023
REJECT tcp -y---- 0.0.0.0/0 0.0.0.0/0 * -> 2049
REJECT udp ------ 0.0.0.0/0 0.0.0.0/0 * -> 0:1023
REJECT udp ------ 0.0.0.0/0 0.0.0.0/0 * -> 2049
REJECT tcp -y---- 0.0.0.0/0 0.0.0.0/0 * -> 6000:6009
REJECT tcp -y---- 0.0.0.0/0 0.0.0.0/0 * -> 7100
Chain forward (policy ACCEPT):
Chain output (policy ACCEPT):
>
> I haven't said much about actual possible problems, because there are too
> many possibilities to list short of writing a book. The diagnostics I
> suggested will help you narrow things down, though.
>
> At 06:00 PM 6/30/01 -0500, Jim Reimer wrote:
>
>>Finally got around to putting a network card in my Linux machine, and I'm
>>having trouble. It's on a LAN with three Windows machines, and from Linux
>>I can ping each of the Windows machines, and vice versa. But that's all
>>I can do. Running RH7.1.
>>
>>IP addresses are 192.168.0.1, 2, and 3 for the Windows machines, and
>>192.168.0.5 for the Linux machine.
>>
>>Telnet and ftp from a Windows box to the Linux box time out (no connection).
>>
>>Telnet and ftp on the Linux box to 127.0.0.1 or 192.163.0.5 all say
>>"connection refused."
>>
>>On the Linux box, http to 192.163.0.5 works ok, but from a Windows machine
>>to 192.163.0.5 it times out.
>>
>>What have I missed / where do I start looking?
>>
>
>
>
> --
> ------------------------------------"Never tell me the odds!"---
> Ray Olszewski -- Han Solo
> Palo Alto, CA [EMAIL PROTECTED]
> ----------------------------------------------------------------
>
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs
