Allow NetBIOS lookup with firewalld
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I just upgraded OpenSUSE from Leap 42.3 to Leap 15.0, and with this upgrade, OpenSUSE moved its default firewall application from SuSEfirewall2 to Firewalld. I opted not to use the susefirewall2-to-firewalld
script for migration, but to rebuild my rules from scratch. However, I cannot seem to allow NetBIOS queries to return successfully on my client machine. I have enabled both the samba
and samba-client
services in Firewalld.
For a host hostname
, which I can ping because of DNS or access by IP address, and from which I can access my OpenSUSE machine via Samba, I try:
> nmblookup hostname
name_query failed to find name hostname
What else do I need to do to allow a NetBIOS query to succeed?
opensuse firewalld
add a comment |Â
up vote
0
down vote
favorite
I just upgraded OpenSUSE from Leap 42.3 to Leap 15.0, and with this upgrade, OpenSUSE moved its default firewall application from SuSEfirewall2 to Firewalld. I opted not to use the susefirewall2-to-firewalld
script for migration, but to rebuild my rules from scratch. However, I cannot seem to allow NetBIOS queries to return successfully on my client machine. I have enabled both the samba
and samba-client
services in Firewalld.
For a host hostname
, which I can ping because of DNS or access by IP address, and from which I can access my OpenSUSE machine via Samba, I try:
> nmblookup hostname
name_query failed to find name hostname
What else do I need to do to allow a NetBIOS query to succeed?
opensuse firewalld
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I just upgraded OpenSUSE from Leap 42.3 to Leap 15.0, and with this upgrade, OpenSUSE moved its default firewall application from SuSEfirewall2 to Firewalld. I opted not to use the susefirewall2-to-firewalld
script for migration, but to rebuild my rules from scratch. However, I cannot seem to allow NetBIOS queries to return successfully on my client machine. I have enabled both the samba
and samba-client
services in Firewalld.
For a host hostname
, which I can ping because of DNS or access by IP address, and from which I can access my OpenSUSE machine via Samba, I try:
> nmblookup hostname
name_query failed to find name hostname
What else do I need to do to allow a NetBIOS query to succeed?
opensuse firewalld
I just upgraded OpenSUSE from Leap 42.3 to Leap 15.0, and with this upgrade, OpenSUSE moved its default firewall application from SuSEfirewall2 to Firewalld. I opted not to use the susefirewall2-to-firewalld
script for migration, but to rebuild my rules from scratch. However, I cannot seem to allow NetBIOS queries to return successfully on my client machine. I have enabled both the samba
and samba-client
services in Firewalld.
For a host hostname
, which I can ping because of DNS or access by IP address, and from which I can access my OpenSUSE machine via Samba, I try:
> nmblookup hostname
name_query failed to find name hostname
What else do I need to do to allow a NetBIOS query to succeed?
opensuse firewalld
opensuse firewalld
asked 11 mins ago
palswim
1,29611629
1,29611629
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
0
down vote
As a result of a discussion about this issue from the Fedora Mailing-Lists, I added port 137 UDP to the Source Port list for the samba-client
Service in Firewalld (with the firewall-config
tool), which enabled the nmblookup
call to succeed.
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
As a result of a discussion about this issue from the Fedora Mailing-Lists, I added port 137 UDP to the Source Port list for the samba-client
Service in Firewalld (with the firewall-config
tool), which enabled the nmblookup
call to succeed.
add a comment |Â
up vote
0
down vote
As a result of a discussion about this issue from the Fedora Mailing-Lists, I added port 137 UDP to the Source Port list for the samba-client
Service in Firewalld (with the firewall-config
tool), which enabled the nmblookup
call to succeed.
add a comment |Â
up vote
0
down vote
up vote
0
down vote
As a result of a discussion about this issue from the Fedora Mailing-Lists, I added port 137 UDP to the Source Port list for the samba-client
Service in Firewalld (with the firewall-config
tool), which enabled the nmblookup
call to succeed.
As a result of a discussion about this issue from the Fedora Mailing-Lists, I added port 137 UDP to the Source Port list for the samba-client
Service in Firewalld (with the firewall-config
tool), which enabled the nmblookup
call to succeed.
answered 11 mins ago
palswim
1,29611629
1,29611629
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f477883%2fallow-netbios-lookup-with-firewalld%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password