Networking Forums

Networking Forums > Computer Networking > Windows Networking > I need help with VPN on Server 2003

Reply
Thread Tools Display Modes

I need help with VPN on Server 2003

 
 
=?Utf-8?B?RG91Zw==?=
Guest
Posts: n/a

 
      03-30-2005, 01:03 AM
I am trying to do this for my aunt's small business. I don't even work there.
They have a cable router. Connected to it through a switch is their server
running Windows Server 2003. There are about 8 PC's also connected to the
switch. The public IP is ported TCP/CP 1723 by the router to the server's
internal IP. I have enabled the server role for the VPN. I setup a VPN
connection on a remote client. I can connect to the server, and I can use
Remote Desktop to control the server, but I can't see the shared folders on
the server. When I "ipconfig" I get an internal address to their network on
the remote machine, on the VPN connection.

Any ideas why I can't see the folders? I am using a local user account that
the folders are normally accessible to.
 
Reply With Quote
 
 
 
 
Phillip Windell
Guest
Posts: n/a

 
      03-30-2005, 03:04 PM
The Cable NAT Device is the one that should be doing the VPN. It will be
more dependable than trying to pass the "Tunnel" to the Server. Some of
those Cable NAT Devices aren't capable of passing the Tunnel like that
anyway,...of course some can't act as a VPN Server either.....

Doing a Static NAT on port 1723 is not all there is to it. There is also
Protocol-47 (that's protocol-47 not port-47) that has to be dealt with as
well. The feature is often called "VPN Pass-through".

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


"Doug" <(E-Mail Removed)> wrote in message
news:1D0F601E-0D6E-4E1E-90C5-(E-Mail Removed)...
> I am trying to do this for my aunt's small business. I don't even work

there.
> They have a cable router. Connected to it through a switch is their server
> running Windows Server 2003. There are about 8 PC's also connected to the
> switch. The public IP is ported TCP/CP 1723 by the router to the server's
> internal IP. I have enabled the server role for the VPN. I setup a VPN
> connection on a remote client. I can connect to the server, and I can use
> Remote Desktop to control the server, but I can't see the shared folders

on
> the server. When I "ipconfig" I get an internal address to their network

on
> the remote machine, on the VPN connection.
>
> Any ideas why I can't see the folders? I am using a local user account

that
> the folders are normally accessible to.



 
Reply With Quote
 
=?Utf-8?B?RG91Zw==?=
Guest
Posts: n/a

 
      03-30-2005, 08:25 PM
Should I enable NAT on the Server? Here's the deal: I didn't setup the server
initially. It is just a fileserver for Quickbooks and some document folders.
The person who did isn't available. The DHCP addresses for the other network
PC's and the server (the only static IP) are defined by the cable router. I
did request the router be set for Protocol 47. Time Warner won't let me
configure the router myself, I have to request changes to it through them.

I have just about had it, but I promised them I would get it to work.

Should I let the server assign the IP addresses? I don't want to screw up
the part of the system that IS working.

Thanks for your help!

"Phillip Windell" wrote:

> The Cable NAT Device is the one that should be doing the VPN. It will be
> more dependable than trying to pass the "Tunnel" to the Server. Some of
> those Cable NAT Devices aren't capable of passing the Tunnel like that
> anyway,...of course some can't act as a VPN Server either.....
>
> Doing a Static NAT on port 1723 is not all there is to it. There is also
> Protocol-47 (that's protocol-47 not port-47) that has to be dealt with as
> well. The feature is often called "VPN Pass-through".
>
> --
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>
> "Doug" <(E-Mail Removed)> wrote in message
> news:1D0F601E-0D6E-4E1E-90C5-(E-Mail Removed)...
> > I am trying to do this for my aunt's small business. I don't even work

> there.
> > They have a cable router. Connected to it through a switch is their server
> > running Windows Server 2003. There are about 8 PC's also connected to the
> > switch. The public IP is ported TCP/CP 1723 by the router to the server's
> > internal IP. I have enabled the server role for the VPN. I setup a VPN
> > connection on a remote client. I can connect to the server, and I can use
> > Remote Desktop to control the server, but I can't see the shared folders

> on
> > the server. When I "ipconfig" I get an internal address to their network

> on
> > the remote machine, on the VPN connection.
> >
> > Any ideas why I can't see the folders? I am using a local user account

> that
> > the folders are normally accessible to.

>
>
>

 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Remote connection Server 2003 to Server 2003 Sandy Windows Networking 2 08-13-2007 03:50 PM
TCP/IP Stack Improvements in Windows Server 2003 and Windows Server 2003 Service Pack 1 Deepak Bansal [MS] Windows Networking 0 06-14-2005 01:14 AM
Webcast on TCP/IP Stack Improvements in Windows Server 2003 and Windows Server 2003 Service Pack 1 Deepak Bansal [MS] Windows Networking 0 06-13-2005 11:55 PM
SP1 Broke my Server 2003 with Exchange server 2003 Backup Windows Networking 3 04-22-2005 05:34 AM
Windows WPA Client does not Install in Server 2003 or SBS Server 2003 John Holmblad Windows Networking 10 01-21-2004 12:39 AM



1 2 3 4 5 6 7 8 9 10 11