Suse 9.2 - the network browser does not discover Win XP workgroup
Hi, I have a Win XP Pro machine on the network. And a fresh installed Suse 9.2. When I select the network icon on the desktop it opens konqueror and displays 2 icons, one of which is for Windows network. Clicking on it, it does not display the list of the workgroups as it is expected, so I can not browse to the XP machine. And in the link it shows "smb:/". Now, if I enter "smb:/192.168.0.1" which is the internal IP address of the XP box, it connects and displays the shared folders and they are accessible as expected. Not a big deal, but if someone knows what causes the problems, and which options to check, my wife will be very happy :), i.e. me too :) Cheers Sunny -- Get Firefox http://www.spreadfirefox.com/?q=affiliates&id=10745&t=85
It's not picking up the machine by name (browse list). You can always put in a
hostname in your /etc/hosts file so that name matches IP.
--
<<JAV>>
---------- Original Message -----------
From: Sunny
Hi, I have a Win XP Pro machine on the network. And a fresh installed Suse 9.2. When I select the network icon on the desktop it opens konqueror and displays 2 icons, one of which is for Windows network. Clicking on it, it does not display the list of the workgroups as it is expected, so I can not browse to the XP machine. And in the link it shows "smb:/".
Now, if I enter "smb:/192.168.0.1" which is the internal IP address of the XP box, it connects and displays the shared folders and they are accessible as expected.
Not a big deal, but if someone knows what causes the problems, and which options to check, my wife will be very happy :), i.e. me too :)
Cheers Sunny
-- Get Firefox http://www.spreadfirefox.com/?q=affiliates&id=10745&t=85
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com ------- End of Original Message -------
Joe Polk wrote:
It's not picking up the machine by name (browse list). You can always put in a hostname in your /etc/hosts file so that name matches IP.
--
If you want a browse list, turn off the firewall, or use a wins server - check the release notes about SuSEfirewall breaking SMB browsing
Joe Polk wrote:
It's not picking up the machine by name (browse list). You can always put in a hostname in your /etc/hosts file so that name matches IP.
Joe, thanks for the input. One way or another this is not the way you convice win users to migrate. They have habits, and as far as the functionality is
On Friday 03 December 2004 03:34, Hamish wrote: there, just my unknowledge should not stop the progress :) So I really want to make it behave as expected.
--
If you want a browse list, turn off the firewall, or use a wins server - check the release notes about SuSEfirewall breaking SMB browsing
Hamish, thanks. After you showed me the way :), I took a look at at the notes. And therethey say that the firewall just makes it impossible for network browsing by default. But you can fine-tune it with yast. So, now the question goes to -- what fine-tuning :). Sunny -- Get Firefox http://www.spreadfirefox.com/?q=affiliates&id=10745&t=85
After you showed me the way :), I took a look at at the notes. And therethey say that the firewall just makes it impossible for network browsing by default. But you can fine-tune it with yast. So, now the question goes to -- what fine-tuning :).
Sunny
As far as I know, there is no way to do this, because the broadcast method for smb is eaten (As a windows client starts, it will broadcast its name and look for a master browser etc - SuSEfirewall stops these packets). One way you could do it is by setting up a wins (samba) server and using this for browse lists.
On Friday 03 December 2004 08:27, Hamish wrote:
After you showed me the way :), I took a look at at the notes. And therethey say that the firewall just makes it impossible for network browsing by default. But you can fine-tune it with yast. So, now the question goes to -- what fine-tuning :).
Sunny
As far as I know, there is no way to do this, because the broadcast method for smb is eaten (As a windows client starts, it will broadcast its name and look for a master browser etc - SuSEfirewall stops these packets). One way you could do it is by setting up a wins (samba) server and using this for browse lists.
Ok, thanks. I'll take a look around for which ports wins is using for broadcasts, etc. And maybe samba server is not so bad idea anyway :) Cheers Sunny -- Get Firefox http://www.spreadfirefox.com/?q=affiliates&id=10745&t=85
Ok, thanks. I'll take a look around for which ports wins is using for broadcasts, etc. And maybe samba server is not so bad idea anyway :)
Cheers Sunny
Wins is not broadcast - that is why it works. Broadcast of any kind dies at SuSEFirewall. ;)
Hamish wrote:
Wins is not broadcast - that is why it works. Broadcast of any kind dies at SuSEFirewall. ;)
Only if it is configured that way, i.e., # 22.) # Allow IP Broadcasts? # # If set to yes, the firewall will not filter broadcasts by default. # This is needed e.g. for Netbios/Samba, RIP, OSPF where the broadcast # option is used. # If you do not want to allow them however ignore the annoying log entries, # set FW_IGNORE_FW_BROADCAST to yes. # # Choice: "yes" or "no", if not set defaults to "no" # FW_ALLOW_FW_BROADCAST="int" ## Type: string(yes,no,int,ext,dmz) ## Default: ext # # set to yes to suppress log messages for dropped broadcast packets # FW_IGNORE_FW_BROADCAST="no" ## Type: yesno ## Default: no # -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
On Fri, 03 Dec 2004 13:27:54 -0600, Joe Morris (NTM)
Hamish wrote:
Wins is not broadcast - that is why it works. Broadcast of any kind dies at SuSEFirewall. ;)
Only if it is configured that way, i.e., # 22.) # Allow IP Broadcasts? # # If set to yes, the firewall will not filter broadcasts by default. # This is needed e.g. for Netbios/Samba, RIP, OSPF where the broadcast # option is used. # If you do not want to allow them however ignore the annoying log entries, # set FW_IGNORE_FW_BROADCAST to yes. # # Choice: "yes" or "no", if not set defaults to "no" # FW_ALLOW_FW_BROADCAST="int"
## Type: string(yes,no,int,ext,dmz) ## Default: ext # # set to yes to suppress log messages for dropped broadcast packets # FW_IGNORE_FW_BROADCAST="no"
## Type: yesno ## Default: no #
-- Joe Morris
Thanks Joe. I'll try to see what will happen. Sunny -- Get Firefox http://www.spreadfirefox.com/?q=affiliates&id=10745&t=85
participants (4)
-
Hamish -
Joe Morris (NTM) -
Joe Polk -
Sunny