A Windows XP Pro PC in City1 (which is part of a NT 4 domain) is trying to map a network share across a VPN tunnel (dedicated site to site) to a Windows 2003 Server in City2 which is not part of a domain, is a standalone server, and there is a workgroup in operation there.
The City1 XP PC can successfully map shares through the VPN tunnel to an XP Pro PC in City2 that is on the same network as the 2003 Server.
The share and NTFS permissions on the 2003 Server shares have been double checked.
The 2003 Server (with IP 192.168.168.xx) successfully returns a ping from across the VPN tunnel from the XP Pro machine in City1.
Other PCs on the City1 network can map shares on the Ottawa 2003 Server just fine.
The command used to attempt to map the share on the 2003 Server is as follows:
Net use f: \\192.168.168.xx\shared
And the result is a System 53 error; network path does not exist.
When looking at the Network Neighborhood from an XP machine in City 1, City2's workgroup can be seen. If double clicked, it shows the PC's in the workgroup, and it is possible to look at the shares on CIty2 XP machines, but not the 2003 server. If you double click on the 2003 server, it gives an error indicating that permissions due not exist and to contact the administrator.
Employing -- Net use f: \\192.168.168.xx\shared /user:2003_Server_name_here\administrator is also not successful, resuting in a system error 53, so it's not even possible to try to map and provide the local administrator password of the 2003 server.
So the I guess the question is, what is different from a security standpoint for a 2003 Server vs an XP machine when serving up shares to a machine that is in a different domain. What needs to be done to allow the mapping of the drive?