RE: Samba problem

Try IP address of "\\C". If it works then your problem is with browse
lists. Is it a domain or workgroup?

CT

-----Original Message-----
From: owner-linux@slg.org [mailto:owner-linux@slg.org] On Behalf Of
Keith Brown
Sent: Thursday, January 17, 2008 3:15 PM
To: linux@slg.org
Subject: Samba problem

   Hi folks. I've got a weird little samba problem that I thought I'd
share
with you for your pleasure.

   At work I have three Linux machines each running Slackware 12.0, each

using exactly the same kernel ... let's call them A, B and C. There is
virtually no difference between them other than minor hardware
differences. Computer C, however has two ethernet ports, one leading to
the external campus network and the other to a private internal network.

   I've used the samba config file from A on computers B and C with the
appropriate alterations. Essentially, each samba config file is the same

except for the netbios name and the names and location of the shares.
I have forced machine C to use the external ethernet port but other than

that, no changes from machine to machine.

   So, here's the thing. I can log on to a windoze computer on the usask

domain and get to computers A and B no problem. Just type "\\A" or "\\B"

in the address bar of a window and I'm there. Not so for computer C
however. If I do the same for C I get "\\C is not accessible ... The
account is not accessible from this station"

   Microsoft and everyone else on the network says that this is an
encryption problem with the fix being to turn off password encryption in

the windoze registry but this is completely impractical here .. there
are
lots of people in various locations on campus that need to access the
machine, some of whom barely understand that you are allowed lift the
mouse at the edge of the mousepad, let alone mess with the registry.

   I *can* connect if I log on to the windoze computer as the
administrator but again, this is impractical as most users that need
access to these samba shares don't have that level of access on their
lab
machines.

   What's really bothering me is why do things work fine on computers A
and
B but not on C? As I said, they're all set up virtually the same with
only
the most minor differences. As far as I can tell, C should work but it
absolutely refuses to respond to normal users. Colour me puzzled.

Dr. Keith Brown
Department of Chemistry/
Saskatchewan Structural Sciences Center
University of Saskatchewan
Saskatoon, Saskatchewan
306-966-1725
http://chem4823.usask.ca/kbrown.html

-----------------------------------------------------------------------
"Pinky, are you pondering what I'm pondering?"
Uh, I think so Brain, but this time, you wear the tutu.
-----------------------------------------------------------------------
Received on Thu Jan 17 16:41:55 2008