Hi, I'm reluctant to jump into this for obvious reasons (that I'm still in the baffled newbie class myself re: Linux) but maybe here are a few of things that could help you because I've had some experience with Microsoft and Novell networks: 1. workgroup name is very important in MS networking. very important that each machine be given *the same* workgroup name. Example: my home LAN is named HOME. So on the Toshiba laptop running Win98, I have workgroup HOME. On the Athlon machine running xp, I have workgroup HOME. On the Linux machines, I have workgroup HOME. I'm behind a Linksys router and each machine is assigned a number in the 192.168.1.x range where x is 1 to 253. 2. The machine name is different for each machine on the MS network (same goes for the Linux boxes as well). For example the Toshiba laptop is named TOSH. The SuSE linux box is named Athena, the xp machine is Venus. You can use uname -a to show you the box name in Linux. On the MS machines, net name should show the machine name 3. If you have your LAN set up as above, then you should be able to see the other MS machine(s) in the Network Neighborhood (regardless of whether smb stuff is working or not on the Linux box.) If not, try pinging from one MS machine to another in an MSDOS box (command window) and just use the numeric IP addresses. Example: ping 192.168.1.5 where .5 would represent the address assigned to one of the MS machines. No answer back means could mean networking not configured correctly, cable problems (physical wire) or hub/switch/router problems. 4. Verify that you have all machines on the LAN using the same network numbers. By that I mean they should all start with 192.168.1.x for example. There can't be one that's 192.168.2.4 and another that's 192.168.1.5. They'll be seen as being on different networks (and that's what routing's all about) and won't see each other the way you want them to. 5. For test purposes, you might abandon DHCP till things are sorted out and just assign each machine an IP in the 192.168.1.x range if that's feasible. It could make pinging and identification easier while testing. Tom
On Saturday 23 March 2002 22:01, you wrote:
If you want to see a Windows share from your Linux machine (see above subject :-) ), you can type on a command line (i.e. xterm) smbclient -L (computer name) -You fill in the name.
I have had no luck with this. I suspect, for the same reason that LinNeighborhood hasn't worked.
If you want to print, you will use lprold, lprng, or cups. I would recommend CUPS to print to your Windows served printer, and your printing program will use samba_print to actually print through the network to your Windows printer.
OK, I see now that printing and smb shares are two very different kettle of fish in Linux. Let's stick to trying to get the smb shares to appear for now, if you are up to it ;-) If we can get it to work without LinNeighborhood, then I will accept this, but it has been about 15 yrs. since I used DOS. I feel totally blind in the command line after having used Macintosh for so long 8-) That is why I have been trying to stick to Art's instructions.
Again, miscommunication. As you noted above, it is control center in KDE. I thought you were talking about the Windows machine, which does have control panel>network.
Not my error, I was quoting from the original e-mail instructions.
The default user name is exactly that. If you set up your Windows (in Windows) to share based on password, then this setting would give it that username and password. If you set up your Windows HD for full access (meaning no password is needed), this is not even needed. BTW, user name is user name, not computer name. This is to authenticate your Linux machine (using Samba) to your password protected Windows shares. I hope that is now clear. ;-)
I believe so. However, if you are using a Win machine and browse your "network neighborhood", you are doing this using the computer name to identify the other computers. As the DHCP/DNS issue has had me so confused, I would just like to verify that my SuSE computer name is what I think it is.
If you are not sharing resources with Windows via Samba (which you would put it in smb.conf), then putting it in Control center for Windows shares will basically allow you to skip the workgroup level (since this would be done by the setting for workgroup) in (I believe) Konquerer (the KDE default file browser).
And "user name" only needs to be filled out in the KDE control center for Win shares if the Win HD is set up for limited access, correct?
No. Do you have Cups installed (it is several different rpms)? Kups is the program I was refering to, because on my network (Windows shared Canon Multipass c-5500), Yast2 could not set it up. Kups did it quite impressively, IMHO.
OK, let's just leave this issue with printing until I am able to see the smb shares with the smb client.
Cheers,
Brian
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com