Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 376
  • Last Modified:

File Sharing using Routing and Remote Access AND VPN

Hi,
I have configured for Accepting VPN Connections from Remote Client using Routing and Remote Access in Windows server 2003 Standard.

If I use a remote desktop, I am able to Remotely connect to my distant server.

My problem is, I can ping my remote ip address and the internal ip in my settings. How do I do now to have access to my other servers for sharring files?
0
maxleb
Asked:
maxleb
1 Solution
 
rr_haleCommented:
If you can ping the inside IP of the server you're using to terminate your VPN, but can't ping anything beyond that, it sounds like the other devices don't know how to return the packets to your remote client.

You should either point them to the inside address of your server as their default gateway, or add static routes to your default gateway pointing to your VPN server as the next hop to your distant (client) IP address.
0
 
Thorbear_IcemountainCommented:
Are you getting a VPN connection? If you are then you should be able to go about it the normal way. A post with IPconfigs would help...
/T
0
 
ChiefITCommented:
File and printer sharing are done in two different ways simultaneously.

 The first way is through netbios broadcasts. You know that netbios broadcasts will not go through NAT, over a VPN tunnel, or two different subnets. This is why they say, netbios is not routeable. The only way to get this to work this way is:
1)  to have a WINS or LMHOST record  connection between the Domain master browser of site A and the remote PC or remote site's domain master browse (Site B)r.
2) This method uses WINS/NETBIOS port 137/TCP, and netbios datagram ports 138 & 139 UDP.
3)  It will require you have netbios over TCP/IP enabled (Not Netbios over DHCP).
4) It is also necessary that you do NOT run IPversion 6 on either the 2003 server or Vista machine. Netbios will not go through an IPv6 toredo tunnel.
5) and your netbios bindings must be correct to share between sites.


The second and newest method is through SMB shares over TCP.
In order to get this to work you need:
1) an open path on SMB port 445/TCP, Netbios datagram port 139/UDP, and RPC port 135/UDP. (NOTE: MOST ISPS BLOCK SMB SHARES BECAUSE OF THE VULNERABILITIES OF THE SHARES AND ACCESS TO OPEN SHARES THAT HACKERS EXPLOIT, THESE PORTS ARE HIGHLY TARGETED)
2) you must not be using IP version 6.


Remember both of these ways are done simultaneously. The first method that answers the call, will be used to gain access to the share. Here is a couple links and description on what I call the OLD SCHOOL method and NEW SCHOOL method.
_____________________________________________________________________

Old school way is to create a WINS connection between the site domain master browsers. (Those are usually the PDCe's)
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Q_23652843.html

New school way is to get SMB shares going through the tunnel on port 445 and Netbios datagram port 137. Now some ISP's block port 445 due to the vulnerabilities of that data. Also, some routers are now encrypting port 445 to secure the shared traffic. So, this setup depends upon what is offered to you.
http://ourworld.compuserve.com/homepages/timothydevans/browse.htm
0

Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now