Maybe you are right, that it is a Firewall problem. Here is a line from
my /var/log/boot.msg file: Dave Howorth
"Starting Firewall Initialization (phase 1 of 2) SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled." I take it that is from the problem system? I don't think you should be seeing this if the firewall is really turned off. Is that from a recent boot? I don't know anything about the firewall (I just make sure it is off :) Perhaps somebody else knows how to be sure it's turned off properly.
Yes its from the problem system. I agree with you about seeing/not seeing the firewall. Yes I just rebooted the problem system and could read the text, and after I could see the line in boot.msg. Did you read my website with the screendump?.
I'm writing this on my ok susebox, and here's there is no information on the Firewall in the boot.msg file.
That's what I'd expect, and none in the messages file either.
So its is here on the 10.0 eval -ok system-.
The xinetd is not started, and cannot be. I do the Firewall and xinetd start/stop from the Yast System System Services.
I take it these comments refer to the problem system? So you're saying that if you type Dave Howorth
ps -fe | grep xinetd
This is from the ok system: ps -fe | grep xinetd root 9177 9155 0 11:27 pts/3 00:00:00 grep xinetd
you don't see a line that mentions /usr/sbin/xinetd? But you do see that line on the system that works?
I did not test it on the problem system, but I'll do it.
What do you mean that it cannot be started? You can't find the page in YaST? (Network Services/Network Services (xinetd)) The buttons are disabled? You can click them but nothing happens? (look in the YaST logs if so)
In the Yast system you can switch on/off the firewall, and the xinetd as well, the ssh and so on. Right ?.
Erik also wrote:
I'm writing this on the ok susebox, so I cannot see if xinetd is enabled or not. I'll try to see it later on today. But I'm absolutely not sure how I cause daemons to be started. Its a darksite of my knowledge :-(
Don't worry about it. Let's just make sure xinetd is working.
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?
Sure I can, but I'll wait untill your reply to this has arrived.
I think now would be a good time to do this :)
As some of the files are huge, and I'm not the best to figure out what has relation to the problem, I'm afraid of sending the files here. What can I do then ?.
Cheers, Dave
-- Venlig hilsen - Best regards - Erik Jakobsen SuSE Linux 10.0 Eval.. Licensed HAM-RADIO with the callsign OZ4KK http://www.urbakken.dk Registered Linux user #114875 with http://counter.li.org