Mapping drives

[Guest]

I have a strange issue. I get the message "the speified network name is no
longer available" when I attempt to map a drive to a windows 2000 system
across a VPN connection. The strange thing is that this used to work prior to
upgrading the source domain from NT to 2003. The Target domain is 2003. The
other strange thing is that it works fine mapping to 2003 machines.

The target systems are in a DMZ in a separate forest over a VPN connection.
Both have the same ports open in the firewalls (ports 139 and 445). Another
interesting thing is that when I attempt to map the drive from the local
domain where the DMZ exists it usually connects, but sometimes it gets the
same error.

Anyone have any thoughts?

--Nick

 

[Steve Parry]

I have a strange issue. I get the message "the speified network name is
no longer available" when I attempt to map a drive to a windows 2000
system across a VPN connection. The strange thing is that this used to
work prior to upgrading the source domain from NT to 2003. The Target
domain is 2003. The other strange thing is that it works fine mapping to
2003 machines.

The target systems are in a DMZ in a separate forest over a VPN
connection. Both have the same ports open in the firewalls (ports 139 and
445). Another interesting thing is that when I attempt to map the drive
from the local domain where the DMZ exists it usually connects, but
sometimes it gets the same error.

Anyone have any thoughts?

--Nick

Will it map if you specify the ip address rather than the name ?
ie
\\192.168.1.1\sharename as opposed to \\servername\sharename

 

[Guest]

No, it's not a DNS issue. Same thing with IP or host name.

--Nick