On Oct 1, 2005, at 3:00 PM, Dale Farnsworth wrote: > 'apt-get remove' leaves config files, as you found. If you want > to remove config files as well, do 'apt-get --purge remove'. Of > course, that no longer works after you have done 'apt-get remove'. > > So to clear everything out, you can do: > apt-get install samba > apt-get --purge remove samba > > It is also safe to just manually delete the files. > > -Dale Thanks. I was able to remove everything and reinstall. I think it worked. I can use swat to configure everything, and I can connect to the server using smbclient. I still have a problem. I have two Macs on this network (OS X 10.4). Clicking 'Network' in the Finder shows the server. Clicking 'Connect', which usually shows the list of available shares and mounts the one selected, crashes the Finder every single time. I think this must be something wrong with the Finder, since I'm now getting the same errors when trying to connect to another Samba server which I used to use with no issues at all. (I recently upgraded from 10.3 to 10.4, so I'm now thinking that's the issue.) Here's a snippet of /var/log/samba/log.alex. (The client machine trying to connect is 'alex'). [2005/10/01 14:42:59, 0] rpc_parse/parse_prs.c:prs_mem_get(537) prs_mem_get: reading data of size 2 would overrun buffer. [2005/10/01 14:42:59, 0] rpc_server/srv_pipe.c:api_pipe_bind_req(919) api_pipe_bind_req: unable to unmarshall RPC_HDR_RB struct. [2005/10/01 14:46:42, 0] rpc_parse/parse_prs.c:prs_mem_get(537) prs_mem_get: reading data of size 2 would overrun buffer. [2005/10/01 14:46:42, 0] rpc_server/srv_pipe.c:api_pipe_bind_req(919) api_pipe_bind_req: unable to unmarshall RPC_HDR_RB struct. [2005/10/01 15:18:36, 1] smbd/service.c:make_connection_snum(642) alex (192.168.0.102) connect to service tmp initially as user alex (uid=1000, gid=1000) (pid 30907) [2005/10/01 15:19:16, 1] smbd/service.c:close_cnum(830) alex (192.168.0.102) closed connection to service tmp That last entry is a successful connection using 'smbclient' from the command line. The rest of the failure messages seem to be the Finder's fault. There's a lot more of this, but it seems to be the same messages over and over. I don't know what to make of this... Look familiar to anyone? thanks, alex --------------------------------------------------- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change you mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss