I've been messing with setting up Samba, but had a major problem that is not covered in most Samba tutorials and books, because it is not really a 'Samba' issue... it is a TCP/IP issue... but one that I suspect a lot ow Windows refugees, moving over to Linux, will miss (I sure did), so I am posting it here.
On my Linux machines, I have IP addresses in the 192.168.0.x range assigned. On my Windows machines, I had Microsoft Networking automatically assigning IP addresses. This is the default, of course. I was unable to ping my Linux server from whatever IP addy Microsoft Networking assigned (I know they have a reserved block, but don't know the numbers). What I did, was I right clicked on the Icon for the Microsoft Networking setup (on one of my Win2k workstations) I had created previously, that worked fine between my Windows machines, and in the 'Properties' tables, I manually assigned it an IP in the 192.168.0.x range, and voila, I could ping the Linux server, and the 'localhost' (Linux server) icon appeared in the 'wittig' workgroup. I still haven't got Samba working properly... it demands a login that does not accept any identities at all on the Windows workstation, and 'smbclient' while it is running, also fails when I enter any and all passwords... but I figure that now, with the TCP/IP issue resolved, and me being able to ftp into the Windows workstation, and ping back and forth, I am most of the way there. -- -wittig http://www.robertwittig.com/ . To unsubscribe from this list, please email [EMAIL PROTECTED] & you will be removed. Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/LINUX_Newbies/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
