VPN File sharing

Greetings

I have a VPN connection between two Server 2003 machines. One machine
is locally behind a nat firewall and the other is hosted by another
company and is setup to act as an IGMP router that accepts the demand
dial connection from the other server. The VPN connection is alive--we
can get successful pings from each machine on the private IPs assigned
by the hosted server, and we can succesfully replicate SQL data between
the two. My problem lies in this: We cannot access file shares
between the two machines via unc path utilizing name or IP address.
Both machines are set up so that:
-NetBIOS over TCP/IP is enabled
-lmhosts is configured
-Client for Microsoft Networks and File and Printer Sharing for
Microsoft networks is enabled
-TCP/UDP ports 135-139 and TCP 445 are enabled on both ends, and are
forwarded from the nat router to the local server
Clearly I'm missing something here, but it's frustrating because I can
clearly see that a connection exists.
Any ideas would be greatly appreciated.

Regards
MarkS

sounds like permission issue. What do you receive if using net view command? this may help,

computer browser over vpn Computer Browsing over VPN - Permission or Cached Credentials issues. If you can ping the remote computer but can't browse the resources, you may have a ...
http://www.howtonetworking.com/VPN/b...govervpne1.htm


Don't send e-mail or reply to me except you need consulting services. Posting on MS newsgroup will benefit all readers and you may get more help.

Bob Lin, MS-MVP, MCSE & CNE
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.

"MarkS" <(E-Mail Removed)> wrote in message news:(E-Mail Removed) ups.com...
Greetings

I have a VPN connection between two Server 2003 machines. One machine
is locally behind a nat firewall and the other is hosted by another
company and is setup to act as an IGMP router that accepts the demand
dial connection from the other server. The VPN connection is alive--we
can get successful pings from each machine on the private IPs assigned
by the hosted server, and we can succesfully replicate SQL data between
the two. My problem lies in this: We cannot access file shares
between the two machines via unc path utilizing name or IP address.
Both machines are set up so that:
-NetBIOS over TCP/IP is enabled
-lmhosts is configured
-Client for Microsoft Networks and File and Printer Sharing for
Microsoft networks is enabled
-TCP/UDP ports 135-139 and TCP 445 are enabled on both ends, and are
forwarded from the nat router to the local server
Clearly I'm missing something here, but it's frustrating because I can
clearly see that a connection exists.
Any ideas would be greatly appreciated.

Regards
MarkS

I'll check out the link, thanks. When I try Net View \\IP_Address, I
receive an Error 53 The network path was not found. I receive the same
thing when trying to access \\IP_Address from the Run window (sans the
Error 53.)

MarkS

as the page says, you have a name resolution issue. you may have 3 options to fix it, DNS, WINS or lmhosts.

Don't send e-mail or reply to me except you need consulting services. Posting on MS newsgroup will benefit all readers and you may get more help.

Bob Lin, MS-MVP, MCSE & CNE
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.

"MarkS" <(E-Mail Removed)> wrote in message news:(E-Mail Removed) ups.com...
I'll check out the link, thanks. When I try Net View \\IP_Address, I
receive an Error 53 The network path was not found. I receive the same
thing when trying to access \\IP_Address from the Run window (sans the
Error 53.)

MarkS

Thanks for the ideas, I figured out the problem. It wasn't a DNS,
WINS, or lmhosts fix. I had previously stated that lmhosts was already
configured. The problem occurred with the IP filters on one of my
servers. They were improperly configured, so that basically the tcp
ports 135-139 and 445 were not open. Configured them properly and
voila, I was in business.

Regards,
MarkS