Erik Jakobsen wrote:
Now I have done the tests.
From the server to the ok suse box:
#traceroute traceroute 192.168.1.9 traceroute to 192.168.1.9 (192.168.1.9), 30 hops max, 38 byte packets 1 lajka3 (192.168.1.9) 0.290 ms 0.180 ms 0.121 ms
From the ok susebox to the server:
# traceroute 192.168.1.1 traceroute to 192.168.1.1 (192.168.1.1), 30 hops max, 40 byte packets 1 192.168.1.1 0.160 ms 0.106 ms 0.141 ms
From the ok suse to the ok suse:
# traceroute 192.168.1.9 traceroute to 192.168.1.9 (192.168.1.9), 30 hops max, 40 byte packets 1 lajka3.urbakken.dk (192.168.1.9) 0.000 ms 0.000 ms 0.000 ms
From the server to the not ok suse:
# traceroute 192.168.1.9 traceroute to 192.168.1.9 (192.168.1.9), 30 hops max, 38 byte packets 1 * * * 2 * * * 3 * * *
From the not ok suse to the server:
# traceroute 192.168.1.1 traceroute to 192.168.1.1 (192.168.1.1), 30 hops max, 40 byte packets 1 mail.urbakken.dk (192.168.1.1) 0.156 ms 0.103 ms 0.101 ms
From the not ok suse to the not ok suse:
# traceroute 192.168.1.9 traceroute to 192.168.1.9 (192.168.1.9), 30 hops max, 40 byte packets 1 lajka3.urbakken.dk (192.168.1.9) 0.000 ms 0.000 ms 0.000 ms
I hope that tells something.
Didn't tell me as much as I'd hoped :( But at least it confirms that the situation is not completely wacky. The only oddity I noticed is that "From the not ok suse to the server" shows a hostname (mail.urbakken.dk) whilst "From the ok susebox to the server" does not. I don't know what that means though. It seems to me that what you're observing is that everything works as long as you initiate the network traffic from the suse box (ping, mail, browser etc), whilst everything fails if the traffic initiates from outside the suse box (ping, scp etc). Is that so? In which case: (1) It does sound like the firewall is a possible culprit. I know you said it is off, but you have double-checked that, yes?! (2) Another possibility is the network service configuration. How do you cause daemons to be started? I run 9.3 so it might be different, but I use xinetd (from the Network Services page of YaST). Have you enabled that? If not, what method do you use? [that doesn't account for ping, AFAIK, but I don't know how that works] If neither of these ideas help to find the problem, can you post whatever network-related stuff there is from dmesg and /var/log/messages from both the working and non-working systems? Erik Jakobsen wrote:
Hans Krueger wrote:
just a thought have you tried knoppix on it ?
Hi Hans. No I haven't, and I'm not aware on how to test with Knoppix. Could you please explain it for me ?.
Knoppix is a Debian-based stand-alone system (runs from the CD). It's usually very good at figuring out the hardware configuration, so it's quite common to start that and then copy the configuration files it generates to fix problems. Cheers, Dave