System Error 53 in XP when trying to connecting to SAMBA
Allen, Michael B (RSCH)
Michael_B_Allen at ml.com
Fri Nov 22 03:28:51 GMT 2002
> -----Original Message-----
> From: Dan De Cotiis [SMTP:ddecoti1 at swarthmore.edu]
> Sent: Thursday, November 21, 2002 10:19 PM
> To: smb-clients at lists.samba.org
> Subject: System Error 53 in XP when trying to connecting to SAMBA
> Hello everyone,
> I realize that some of what I am doing with SAMBA is not appropriate from a security standpoint, but I am simply trying to demonstrate a concept to others in my organization.
> I am trying to setup a public samba share that is accessible by members of my organization at remote campuses (I realize that using samba alone for this is probably a bad idea and that I should
> probably be using some sort of VPN technique). I need to support windows 98, 2000, and XP clients. I have set SAMBA up correctly, I think because I can map a network drive to Windows 98 and 2000
> by mapping to \\188.8.131.52\myshare <file:///\\184.108.40.206\myshare>. This technique does not work for my XP clients.
What is this "technique" you're using? Is this some Samba hackery I have never seen before?
> I am unable to map the drive in XP, and I get a "the network does not exist" error. I have enabled NetBIOS over TCP/IP in the advanced TCP/IP settings dialogue, but when I open a command windows
> and type "net view \\220.127.116.11\myshare <file:///\\18.104.22.168\myshare>" I get a message that "System Error 53 has occurred".
C:\>net helpmsg 53
The network path was not found.
Which means that it cannot find a share with that name but it's not clear what name is being
passed through to sambe. Is it 'myshare <file:///' or something else?
> When I issue this same command in 98 and 2000 I don't have a problem, and the command returns a list of available shares on the samba server. I know the XP doesn't play nice with samba, but can
> any offer a suggestion as to what I can do to allow the XP clients to see the shares?
Sounds like XP is interpreting your hacked UNC path. You should get a capture with Ethereal
or NetMon and see what the share name is in the SMB_COM_TREE_CONNECT_ANX
More information about the smb-clients