Annoying Newbie, back again.
After looking around the smb.conf in SUSE 9.1 I finally descovered the problem behind the error "Network unreachable" when trying to browse the LAN in konquorer.
After the workgroup name is changed from "TUX-NET" to the one that the rest of the LAN uses "MSHOME" (in YAST samba server setup) the problem occurs. When the name is changed back to "TUX-NET" browsing in konquorer is ok again.
Although I have found this out I am still no closer than I was to sorting out my network.
I think that I have been asking the wrong questions.
What I am trying to achieve is this;
I am running SUSE 9.1 on a peer to peer network along with seven WINXP machines.
I want to share one folder called "My network share" and its sub folders and files. Allow others on the network to see it and read/write to it.
"My network share" is in /home.
I still want to be able to browse the network with my Linux box and read/write to the WINXP shares.
This should be as simple as setting things up in YAST2 but as I said above, every time I change the workgroup in YAST or smb.conf I loose my ability to browse the network.
Please somebody put me out of my misery one way or another as I'm still the laughing stock of this WINXP crowd.
Is this a samba problem or is it KDE or SUSE or just ME?!
Where am I going wrong? What am I missing? Why is this not simple?
Hope someone can help.
I had better go now, they mostly come at night......mostly:-)
___________________________________________________________ Moving house? Beach bar in Thailand? New Wardrobe? Win £10k with Yahoo! Mail to make your dream a reality. Get Yahoo! Mail www.yahoo.co.uk/10k
On Tue, 23 Nov 2004 14:43:33 +0000 (GMT), RICHARD FLETCHER roofletch@yahoo.com wrote:
Annoying Newbie, back again.
After looking around the smb.conf in SUSE 9.1 I finally descovered the problem behind the error "Network unreachable" when trying to browse the LAN in konquorer.
I am running SUSE 9.1 on a peer to peer network along with seven WINXP machines.
I want to share one folder called "My network share" and its sub folders and files. Allow others on the network to see it and read/write to it.
"My network share" is in /home.
You want to create the share for this in your smb.conf file. There will be entries in there you can follow, but it will be something like:
[Richard] comment = Richard's home share for underpriviledged XP users path = /home/richard/shared_thing read only = No locking = No browseable = yes
Then you restart Samba. Typing "testparm" will sort of parse the file to check your syntax is ok. You can then connect from a windows box on the network with \192.168.10.56\Richard Where 192.168.10.56 is your IP and Richard it the name you gave your share in the square braces.
I still want to be able to browse the network with my Linux box and read/write to the WINXP shares.
This should be as simple as setting things up in YAST2 but as I said above, every time I change the workgroup in YAST or smb.conf I loose my ability to browse the network.
I don't think I'm qualified to comment on this. Does your computer know which is the WINS server and router on your local network?
Please somebody put me out of my misery one way or another as I'm still the laughing stock of this WINXP crowd.
Don't worry, "tables" and "turning" come to mind. And "laugh" and "face". :-)))
Is this a samba problem or is it KDE or SUSE or just ME?!
Where am I going wrong? What am I missing? Why is this not simple?
Hope someone can help.
I had better go now, they mostly come at night......mostly:-)
On Tue, Nov 23, 2004 at 04:13:48PM +0000, Jenny Hopkins wrote:
You want to create the share for this in your smb.conf file. There will be entries in there you can follow, but it will be something like:
[Richard] comment = Richard's home share for underpriviledged XP users path = /home/richard/shared_thing read only = No locking = No browseable = yes
Then you restart Samba. Typing "testparm" will sort of parse the file to check your syntax is ok.
You don't actually need to restart I don't think, doesn't Samba (the smb process) respond to the usual 'kill -1 <pid>'?
-
Chris Green -
Jenny Hopkins -
RICHARD FLETCHER