I did the search and found at the following site: http://home.nyc.rr.com/computertaijutsu/samba.html use client driver = yes to smb.conf would get rid of that access denied error message. I tried it and it seems to be working. If I still have problems, I will send another message. Thanks for the help. On Thursday 29 April 2004 11:21, Adam Voigt wrote: > http://www.google.com/search?hl=en&ie=UTF-8&oe=UTF-8&q=samba+Access+Denied+ >unable+to+connect&btnG=Google+Search > > On Thu, 2004-04-29 at 10:46, Jon Shorie wrote: > > I have moved our primary file and print server over to fedora core 1 last > > night. We were previously using Redhat 6.2. In our system, we have > > several file servers who share out their files via nfs. The primary > > file/print server mounts these and then reshares them out using samba. > > > > We then have 40 95/98/Me/2k clients who access these files. Our 5 linux > > desktops directly mount the files from the original servers, but printing > > all goes through the primary server. > > > > The biggest issue that we ran into was configuring printing to work > > through samba. The only way that I could get it to run stable was to > > configure all print queues as raw and then set up the windoze machines to > > print to the samba server. > > > > I am still getting a message on most of the windoze machines that says > > "Access Denied unable to connect" when I click on one of the printers > > that is shared out from the fc1 box. The windows machine CAN print > > properly, but the error message is still there. > > > > Any suggestions?
