map nework drive over vpn to shared folder

I am able to VPN into a hosted network in which I am renting a machine. I
can ping this machine. I have connectivity to SQL Server databases on this
machine. I can RDP into this machine and work on its desktop with full
control.

However , I cannot map network drives from my machine to shared folders on
the remote machine. Via RDP , I have shared these folders giving everyone
with full permissions.

I am on Vista Ultimate SP1. I connect to the internet via Comcast broadband.

The remote hosted machine is Windows Server 2003 R2 Standard Edition SP2

John A Grandy <johnagrandy@g-mail-dot-com> wrote:
> I am able to VPN into a hosted network in which I am renting a
> machine. I can ping this machine. I have connectivity to SQL Server
> databases on this machine. I can RDP into this machine and work on
> its desktop with full control.
>
> However , I cannot map network drives from my machine to shared
> folders on the remote machine. Via RDP , I have shared these folders
> giving everyone with full permissions.
>
> I am on Vista Ultimate SP1. I connect to the internet via Comcast
> broadband.
> The remote hosted machine is Windows Server 2003 R2 Standard Edition
> SP2

It would help if you explained exactly how you'd tried & the exact error
messages you got when doing so....

"John A Grandy" <johnagrandy@g-mail-dot-com> wrote in message
news:u2gnwZMhJHA.4572@TK2MSFTNGP04.phx.gbl...
>I am able to VPN into a hosted network in which I am renting a machine. I
>can ping this machine. I have connectivity to SQL Server databases on this
>machine. I can RDP into this machine and work on its desktop with full
>control.
>
> However , I cannot map network drives from my machine to shared folders on
> the remote machine. Via RDP , I have shared these folders giving everyone
> with full permissions.
>
> I am on Vista Ultimate SP1. I connect to the internet via Comcast
> broadband.
>
> The remote hosted machine is Windows Server 2003 R2 Standard Edition SP2

This issue, I think, is most often a name resolution issue. How are you
attempting to map? By name or by IP?

-Frank

> This issue, I think, is most often a name resolution issue. How are you
> attempting to map? By name or by IP?

Most likely it's naming. But it may also be routing and/or port blocking.
The ISP may not allow that host to make outbound connections necessary for
filesharing. This as a defense against various malware attacks (where the
machine gets compromised and seeks to attack others).

You'll need to know the IP address of your home machine's side of the VPN
connection. Bring up a cmd prompt on your home machine and use "ipconfig
/all". Make note of the IP address of your local VPN connection.

RDP into the remote machine. Bring up a cmd prompt on it. See if you can
ping your home machine. Use your VPN's local IP address on the remote
machine with the command "ping ip.address.of.yourmachine". If that works
then there's enough routing setup properly to allow the connection. Then
try using "new view \\ip.address.of.yourmachine" to see if you can view the
shares on your home machine. If you can ping but can't 'net use' then there
may be firewall issues.

-Bill Kearney

I can not ping from the remote machine back to my local machine.

I ran ipconfig /all

Here is the section I assume contains my local machine's ip on the vpn :

NOTE : for privacy's sake , I changed the actual ip

PPP adapter myvpn:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : myvpn
Physical Address. . . . . . . . . :
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 10.3.8.78(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 10.0.80.11
10.0.80.12
NetBIOS over Tcpip. . . . . . . . : Enabled

"Bill Kearney" <wkearney99@hotmail.com> wrote in message
news:qridnTEk2uzrbRvUnZ2dnUVZ_oHinZ2d@speakeasy.net...
>> This issue, I think, is most often a name resolution issue. How are you
>> attempting to map? By name or by IP?
>
> Most likely it's naming. But it may also be routing and/or port blocking.
> The ISP may not allow that host to make outbound connections necessary for
> filesharing. This as a defense against various malware attacks (where the
> machine gets compromised and seeks to attack others).
>
> You'll need to know the IP address of your home machine's side of the VPN
> connection. Bring up a cmd prompt on your home machine and use "ipconfig
> /all". Make note of the IP address of your local VPN connection.
>
> RDP into the remote machine. Bring up a cmd prompt on it. See if you can
> ping your home machine. Use your VPN's local IP address on the remote
> machine with the command "ping ip.address.of.yourmachine". If that works
> then there's enough routing setup properly to allow the connection. Then
> try using "new view \\ip.address.of.yourmachine" to see if you can view
> the shares on your home machine. If you can ping but can't 'net use' then
> there may be firewall issues.
>
> -Bill Kearney