At 11:50 PM 5/31/1999 +0200, Joop Boonen wrote:
Dear Samy, Can you please describe your situation. I mean what is your server is it a the Linux samba server? Are there also windowNT servers in it? Are the windows machines clients? Do you also want to print trough the samba machine? If yes can you already print directly form your samba machine? I think it's about it.
Three pcs , one is set up as a samba server . I just rolled it back to 6.0 2.03 kernal and samba 1.9 after formating the drive , reinstalling 6.0 and restroing a couple of data directorys. Few hour work. The samba server has no printer and I have been using the hp5L on the win 98 machine for printing ( this broke when I went to 6.1/2.2.5 kernal and samba 2.0.3) Now all is smoth and working. the samba server comes up in entwork nioeborhood , and doing the smb mounts and smbclients all work on the samba server , no errors , no failed connections. real sweet. It is a little slowere , due to the 2.0 kernal I believe but it now works. The other two pcs are a windows 98 machine that shares its drive and printer. the third machine is a win 95 machine as well that shares its drive and printer. a quick summery of problems, bothe win95/8 amchines could not see any thing in network nieborhood. you could map a drive to the samba server shared dirs either by right clicking Network Nieborhood and mapping it ort using the dos net use e: \\linux\shared. Once there was a drive mapped , on an intermitten basses , sometimes the linuc samba serveer would show in network nioeborhood , but only after doing a search and searching throught the workgroup to get to the server. This worked most of the time. If I turn off file and print sharing on the win98 machine , saved and reboot , the shared linux server magicaly apears. Turn it back on , presto m, gone. Now on the samba server , it will not print to the win98 machine at all. Some timee it will print to the win95 machine , but this would only work 70 0f the time. I could not get a smbclient -L windows machine to go through successfuly. kept getting errors, failed connections ( I think). If I passed it the ip address then it would go throgh and display the machine. Now with smbmount I keep getting failed connections (this I am sure about) . agoein if I pass the ip address it would go through.
I will try to answer the question tomorrow. I have to go to sleep now. it's night over here now.
Regards,
Joop Boonen.
Samy Elashmawy wrote:
joop , I have been workingg for two weeks trying to get 6.1 /2.2.5 w samba 2.0.4 to work with the windows 95/8machines. NOTHING but trouble so far.
The samba machine cannot see the windows macnines unless I pass the ip address , nor will the samba server wint to the win95/8 machine printers( it has no printer)
nor will the smba server come ip in network nieborhood unless fist mapped to a drive letter.
Real krazzy . I just rolled the whole dserver back to 6.0 and samba 1.9 and it works real nice , no troubls.
Any way , I cant figure if its the samba 2.0.3 package thats giving trouble or if its the 6.1 / 2.2.5 keranl/system that is causing trouble.
At 11:25 PM 5/31/1999 +0200, you wrote:
Samy Elashmawy wrote:
Have any of you successfuly upgraded 6.0 to kernal 2.2.5/7 and
successfully
running samba 2.0.3 on this setup ???
I have just given up on 6.1 2.2.5 and Samba 2.0.3 and fromatted and rolled back to 6.0 and 1.9 , that at least will work.
I am wondering the follwoingt senarios ,
1/ have any of you gone from 6.0 to the 2.2.5/7 kernal and samba 1.9 Does this work ?
Yes it works perfectly. The new command is: smbmount "\\server\tmp" -c 'mount /mnt -u 123 -g 456' This information can be found in the man page. man smbmount
2/ have any of you ran 6.0 2.0 kernal with the samba 2.0.3 rmp
upgrade for
6.0?
I didn't i ran 6.0 with kernel 2.2.x I had to recompile samba 2.0.x myself after that it worked fine. I have one disadvantage which is that it wasn't a rpm file that makes it very difficult to have control over the installed packages. Now i'm happy that i while using suse 6.1 i can install and deinstall the packages very easily.
3/ have any of you gone from 6.0 to the 2.2.5 kernal and samba 2.2.5/7 upgrade/update , not a complete 6.0 to 6.1 upgrade. I have been
unable to
get either an upgraded 6.0 -> 6.1 w Samba 2.0.3 to work properly nor a CLEAN new install of 6.1 w samba 2.0.3 to work.
I did both i first upgraded. Everything worked fine. But i prefer a clean setup so i removed everything expert for /home/* . This gives me a system that i can control very easily. There won't be any surprises.
Anyway i'm very happy with suse 6.1 even tough it gets upgraded in the meanwhile. I think it's quite logical as Linux is a fast evolving operating system that needs fixes. But i prefer that these fixes will also be available for users of older suse 6.1 versions. Btw the way there is a update directory for suse 6.1 i hope all update packages are in it. I saw for instance the last yast version.
thanks
All
-- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archive at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>
-- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archive at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>