ok I know this thread may be something that came up before, but I did read the article on Linux networking two machines for n00bs and it did mention Samba when it came to crossing the Linux to XP divide.

Originally I thought this would be very simple - because at first I could see the other machines on my network - just not get to any access. Now I have become confused. I made some changes in configuration for networking that allowed me to select a default windows login and workgroup - this had me excited that things may be simple....

But they never are and afterwards I cannot even see the other machines - now clicking on the desktop icon for network brings up a konqueror window with services and all SLP services shown in it - but this does not seem to do me any good.

Also I cannot follow the guide article - I have no System Settings - server settings that I can find - is this a reference to Samba? And am I missing Samba in my distro, which is SuSE 9.1 from Novell?

I'll probably go google and download something Samba soon - tell me if I am wasting my time or any help you can offer though!

thanks!

The YaST management system that configures things for you in SUSE is a bit quirky. I suspect that when you OK'd the username and password YaST overwrote some other setting as well. You do need to have Samba installed, but if you could see the XP machines on the network from your Linux system then it's there.

The "System Settings" menu is for Red Hat and Fedora Core. As RH and Fedora have the most users, you have to assume that any tutorial that doesn't say otherwise is written for those systems...

With Samba it's important to take it one step at a time when troubleshooting - Windows networking is a complex multi-layered thing. I would start at the command-line: ping an XP machine, then use smbclient to connect to a share and a download a file, and then if that is successful look at the graphical tools.

If you get stuck the best thing to do is to either post to the Networking forum here with the contents of the configuration file /etc/samba/smb.conf, or to the SUSE forum if the command-line works but the graphical stuff doesn't.

OK - eventually from the YAST2 configuration under software I found I had some of the Samba I needed, but not all. I have installed a few extras from the DVD I burnt - enough that I get tux sitting on windows in my Konqueror window, and from there get to the workgroup and then see the computers on the network - I can get as far as the shares, but no further.

Again I am prompted for user and password - I have tried a few I know are there and they do not work, some end in permission denied and some end in system error dialog box.... My theory is that XP is not playing ball at the other end.

As you suggest - I shall transfer over to the networking thread (even though I am still a noob!)

An outside source (one I respect) has suggested maybe I need identical account name/password on the Linux and XP machines I wish to network - could anyone confirm or deny this?

Many thanks

The user/accounts thing can be tricky at first, but basically, you'll need three. You'll need a linux user/password, a samba user/password, and a windows user account/password that all match for access both ways. It's not too terrible to configure.
good luck.

thanks for confirming - unfortunately whilst this may be easy to set it gives me a royal headache because I wish to run a certain account with no password - fine on XP, but something I have yet to achieve on SuSE! Cannot find KUser... tried checking "alllow passwordless logins" to no avail, not sure where to go next (about to search and google it though)

If passwordless is what you need, good luck with it. I wouldn't suggest or approve of it for security reasons.
good luck.

I completely understand your concern. I was half expecting to get flamed for my intended goal, pleasantly surprised not to be.

I also believe (so far) that it is apparently IMPOSSIBLE to have a login with no password (something you maybe suspected).... However my personal perception is that this is a limit on the OS and there can be certain highly specialised situations where the absence of a password may be desirable. The only way I can see to address it for me is to have an "always on" Linux system, but this is less than ideal.

Thanks for wishing me luck - I do believe I may need a good deal of it to achieve this!

Again I don't recommend this, but, here is a search just the same.
good luck.