Hello
I've got a problem getting my XP system to see a Samba share.
I set up Samba using Swat, setting a guest account with the same name
as a user account, and setting a samba password for it. "Guest OK is
set to yes and Security is set to user.
In Windows I used "manage user accounts" to set up the account and
password for the Samba host machine.
If I try to access the samba machine before bringing samba up,
everything happens much as you' expect. Network places doesn't show
the Linux machine, and I can't map a network drive. The reponses to
all these attempts are immediate.
If I bring the XP sytem up after the linux system, I can navigate as
far as the Linux system fro "network places", but if I click on that
system, after about 30 seconds, I'm told I cannot access that system,
and may not have the correct priileges.
If I try to map a network drive, the first time I try, after about 30
seconds, I get the message: "No service is operating at the
destination network endpoint on the remote system". Subsequent
attemts yield a "The network path ... could not be found" (after a 30
second wait).
If I try and browse to the folder (in Map Network Drive), I get as far
as the Linux system, and when I click on it, I get an hourglass for 30
seconds, and then nothing.
It seems clear that the XP system can see the Linux system (the ping
each other OK), and can see the Samba process, yet cannot see the
share. But if it can't see it, why does it always take 30 seconds
before reporting back. (remember, if Samba is not running, I get an
immediate return which implies it's not some network timeout). And
why would it take 30 seconds to determine that the share isn't
present, or that the permissions are wrong?
Posted Via Usenet.com Premium Usenet Newsgroup Services
----------------------------------------------------------
** SPEED ** RETENTION ** COMPLETION ** ANONYMITY **
----------------------------------------------------------
http://www.usenet.com