[SOLVED] shorewall blocks access to server by name

[SOLVED] shorewall blocks access to server by name

Postby pernel » Jan 27th, '25, 13:30

I am configuring a new server with mageia 9. I used the tool in MCC to setup the personal firewall and enabled samba access there. Unfortunately the host name is not visible on my network and i can't access the samba shares from my windows computers by using the host name, only by using the ip-address. If I switch off the firewall complely (by allowing everything in the MCC firewall tool) the server and share becomes accessable by the host name.
I have tried to compare the configuration with another Mageia 9 server on my network but I can't find any differences that can explain why this happens.

Similar phenomenon with the ssh server, webserver, webmin server. All set to be accepted by the personal firewall. They can only be accessed by the ip-address if the firewall is activated.

Would appreciate any hints how this can be solved before I expose the server to internet.

Per
Last edited by pernel on Feb 15th, '25, 12:53, edited 1 time in total.
pernel
 
Posts: 66
Joined: Mar 21st, '12, 20:13

Re: shorewall blocks access to server using it's host name

Postby doktor5000 » Jan 27th, '25, 19:31

Hi there, you're missing some actual details. You should add some actual outputs from one client and the server in question,
and also some relevant detail on your network, especially in regards what you use for name resolution.

Apart from that personal firewall itself has nothing to do with name resolution.
Also a hostname is not "visible" on a network, it can either be resolved on a given client to an IP adress or not, that's not a matter of firewall.
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 18013
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: shorewall blocks access to server using it's host name

Postby pernel » Feb 15th, '25, 12:50

Sorry for the confusion in my first post. My observations there were not correct and had nothing to do with shorewall. Could not access the server by name even when shorewall was disabled. Finally after crosschecking between the old server and the new, I understood that the nmbd service was for some reason never switched on at boot. After correcting this, the new server is visible on the network by name!
Per
pernel
 
Posts: 66
Joined: Mar 21st, '12, 20:13


Return to Networking

Who is online

Users browsing this forum: No registered users and 1 guest