[QUOTE=hcp_dk;36994]Firewall:rcSuSEfirewall2 stop
iptables --flush INPUT
iptables --flush FORWARD
iptables --flush OUTPUTThis commands removed the error massage. But when I’m reboot, the error massage come again. I can so type commands again and the error message disappear[/QUOTE]
I am doing some more research on this issue. I will update this thread when I have more information.
thanks so far. I think we got quite far. I can open a service request and try get support from there. It seems to be a more difficult issue as a bug or so?
thanks so far. I think we got quite far. I can open a service request and try get support from there. It seems to be a more difficult issue as a bug or so?[/QUOTE]
I have already asked someone from SUSE tech support to have a look at this. I should have a response later this week.
You also were unable to print from your SLES system.
[LIST]
[]Have you tried to correct your SLES firewall configuration, doing the same as you did on SLED?
[]Can you now print from SLES?
[*]Is your SLES system something you need or was it just setup to see if you could print from it?
[/LIST]
Hi Kevin,
I have not tried SLES further. It’s a PC and firewall is internal zone. I’m not traveling for some days but can try later.
However, if we not can solve the issue on SLED with LAN and print it’s the same on SLES:
Firewall messages I wrote.
I get the failure message about 2 firewalls acting.
I can flush input, output as done and the message disappear. As soon I reboot, the message comes again.
I tried now the same on SLES.
Firewall internal: no print possible
Firewall exteral and open ports as done on SLED: no print possible.
I tried printing from Libre[/color]
I suspected there were other issues with SLES. Is this a test system or
one that you intend to keep?
Can you print if you stop the firewall AND flush iptables?
If you still cant print, can you please post the contents of
/etc/sysconfig/SuSEfirewall2?
–
Kevin Boyle - Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below this post.
Thank you.
Print don’t get done, don’t get processed.[/color]
There are some minor differences between your SLES firewall and your
SLED firewall configuration but, for now, don’t worry about it.
Something is preventing communication with your printer even when the
firewall is disabled.
Can you ping your HP printer from SLED?
Can you ping your HP printer from SLES?
Please run ifconfig on your SLES system and post the results.
–
Kevin Boyle - Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below this post.
Thank you.
yes, i can ping the printer from SLES and SLED.
I had to set the SLES firewall (stationary PC) to internal since I otherwise do not can search in the Active Directory, the LAN system.
[QUOTE=hcp_dk;37196]Hi Kevin,
I had to set the SLES firewall (stationary PC) to internal since I otherwise do not can search in the Active Directory, the LAN system.
[/QUOTE]
As I mentioned in an earlier post regarding your SLED…
You were able to print from SLED after your firewall was correctly configured. While you still may have additional printing issues on SLES, let’s try to get your SLES firewall working first.
In the mean time, until we get the firewall working, you can allow all traffic between SLES and your Windows Server.
Using YaST Firewall:
[LIST]
[]Ensure all interfaces are assigned to the External zone.
[]Setup 2 Custom Rules to allow all traffic between SLES and Windows Server.
[LIST]
[]Source Network is your Windows Server (10.0.25.4?); Protocol is TCP; Other fields left blank.
[]Source Network is your Windows Server (10.0.25.4?); Protocol is UDP; Other fields left blank.
[/LIST]
[]Restart your firewall
[]Verify you can “search in the Active Directory”.
[/LIST]
SLED: actually I can’t print from SLED at all. Not with or without firewall. I have no clue why. The data not even reach the printer. Maybe due to updates?
SLES: I did as mentioned above.
Actually I can access the windows network.
Try printing a 4MB large PDF. Data arrive the printer. But no printing happen.
Starting Nmap 6.47 ( http://nmap.org ) at 2017-03-29 22:10 CEST
Nmap scan report for 10.0.25.143
Host is up (0.000011s latency).
Not shown: 65531 closed ports
PORT STATE SERVICE
22/tcp open ssh
139/tcp open netbios-ssn
445/tcp open microsoft-ds
3689/tcp open rendezvous
Nmap done: 1 IP address (1 host up) scanned in 5.88 seconds
linuxSLES:/home/hans-christoph #
[/CODE]
Starting Nmap 6.47 ( http://nmap.org ) at 2017-03-29 22:12 CEST
Nmap scan report for 10.0.25.143
Host is up (0.0000090s latency).
Not shown: 65531 closed ports
PORT STATE SERVICE
22/tcp open ssh
139/tcp open netbios-ssn
445/tcp open microsoft-ds
3689/tcp open rendezvous
Nmap done: 1 IP address (1 host up) scanned in 5.81 seconds
linuxSLES:/home/hans-christoph #
[/CODE]
Your previous post shows you opened ports in the External Zone for the 10.0.25.0/24 network:
[LIST]
[]Did you restart your firewall after configuring it?
[]Did you run the nmap port scan from an IP address in the 10.0.25.0/24 network?
[/LIST]
If you expect printing and other services to work, you have to ensure the appropriate ports are open. You can use nmap from another device on your network to verify that the ports are open. If they are not open, then you have to determine why.
There is still the message about “Another Firewall Active”. It appears that message is displayed when starting YaST Firewall if there are entries in iptables. I have not been able to determine why entries remain in iptables after stopping your firewall but they can be removed by flushing iptables as described previously.
Try this to see what you can learn:
[LIST]
[]Ensure interfaces are assigned to the Firerwall’s External Zone
[]Restart your firewall
[]Run nmap and make a note of the open ports.
[]Stop the firewall.
[]Run nmap a second time and make a note of the open ports.
[]Flush iptables.
[*]Run nmap a third time and make a note of the open ports.
[/LIST]
If the necessary ports still remain closed, then you will need additional troubleshooting that is beyond what can be provided via the forums. I suggest you open a Service Request for this issue. You may want to refer the support person to this lengthy thread so they see what has already been tried.
You stated previously that you installed packages from unsupported (non SLE) repositories. There may be incompatibilities between those unsupported packages you installed and the SLE packages already installed on your system that could be responsible for this behavior. If that is so, then you may be on your own to find a solution.
SLED: actually I can’t print from SLED at all. Not with or without firewall. I have no clue why. The data not even reach the printer. Maybe due to updates?[/QUOTE]
That is unfortunate.
[LIST]
[]What did you change?
[]Can you run an nmap port scan from your SLES server to see what ports are open on your SLED laptop?
[*]
[/LIST]
[QUOTE]SLES: I did as mentioned above.
Actually I can access the windows network. [/QUOTE]
I thought that might help.
That may be related to a port issue or perhaps a driver issue. I don’t remember if you were ever able to print to the HP printer from SLES. To verify that the driver is installed correctly, are you able to print from SLES via a USB connection?
I did these nmap from SLES (inside). I can do it from outside too - later, with both setups (external open ports and internal)
Firewall is restarted every time. but i can reboot each time
The modules I installed have nothing todo with firewall. It’s codecs and FreeCad, Shutter (try that - very good program)
But there is something myth with this firewall.
SUSE service has been a half a day on SLES tried a lot (remote). Now they opened a bug. But as you said, there is a point regarding firewall.
Let’s collect data.
I’m now off for a week - in Denver CO.
I have my SLED laptop with me.
