Solved

Windows 2003 VPN-Should the application & VPN servers be on the public domain?

Posted on 2006-11-21
3
189 Views
Last Modified: 2010-04-18
In a small office environment, we have installed Windows 2003 Server (used as file and application server.  This is also acts as domain controller).  We have separately installed Windows 2003 VPN Server.  The servers are installed but there the file server is not accessible from remotely via the VPN server.  There is one setting that we are not sure and wondering if anyone can help answer.  The VPN server is in the public domain, i.e. VPN_server_name.publicdomain.com.  However, the file server is not in the public domain.  applictions_server_name.internaldomain.com.  Do you see any problem here? In other words, do we need to name the domain on the Application server the same as of our public domain?
0
Comment
Question by:annasad
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
3 Comments
 
LVL 38

Assisted Solution

by:Hypercat (Deb)
Hypercat (Deb) earned 150 total points
ID: 17988948
If you want VPN users to be able to access files and folders on your private domain, the easiest way to do it is to have both servers on the same domain.  I'm not sure what your purpose for having the two servers in different domains would be.  If you have your VPN users connecting and authenticating on a different domain from your private domain, they will not be able to access files and folders on the private domain unless you configure a trust relationship between the two domains. Once you do that, you really are not increasing your security level significantly by having the two servers in different domains, if this was the purpose.

Hope this helps!

Deb
0
 
LVL 23

Assisted Solution

by:TheCleaner
TheCleaner earned 150 total points
ID: 17989146
If you can VPN in and simply cannot browse/map to the internal file server, then it's probably a simple DNS issue.  You can test this by VPN'ing in and then pinging the file server name by the FQDN (so fileserver.internaldomain.com).  If it resolves ok, try mapping a drive to that FQDN/sharename.  If that works, and you are using the simple XP "vpn client", go into the TCP/IP properties of the VPN connection setup, and then DNS, and add the internal domain name as the DNS suffix for that connection.  Then you should be able to resolve the fileserver simply by the shortname/netbios name.
0
 
LVL 48

Accepted Solution

by:
Jay_Jay70 earned 200 total points
ID: 17990816
if your users who are working locally  (without VPN) can resolve the name of that server in the public domain then there is no reason that your remote clients cannot.....I have taken to mapping simply by IP Address over VPN's when its giving me grief...lazy i guess
0

Featured Post

PeopleSoft Has Never Been Easier

PeopleSoft Adoption Made Smooth & Simple!

On-The-Job Training Is made Intuitive & Easy With WalkMe's On-Screen Guidance Tool.  Claim Your Free WalkMe Account Now

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

This may not be a text book method to resolve VSS backup issues but it seemed to have worked on few of the Windows 2003 servers we had issues while performing a Volume Shadow Copy backup. If you have issues while performing a shadow copy backup usin…
Learn about cloud computing and its benefits for small business owners.
Attackers love to prey on accounts that have privileges. Reducing privileged accounts and protecting privileged accounts therefore is paramount. Users, groups, and service accounts need to be protected to help protect the entire Active Directory …

751 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question