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
Solved

Access Local Server Via Public IP

Posted on 2014-03-20
4
475 Views
Last Modified: 2014-03-21
We have a couple of servers within our local LAN that are available from the Internet as well.  The problem is that LAN users must use the private IPs of the servers instead of the public URL or they are unable to connect.  This gets confusing when people move between inside the office and remote locations.  It would be better if we could just use the public address/IP for everything.  

The LAN is a Windows domain using the DC for DNS and it all sits behind a SonicWALL gateway.
0
Comment
Question by:slattdog
  • 2
4 Comments
 
LVL 39

Expert Comment

by:Adam Brown
ID: 39943003
One of the security features sonic wall implements is to block attempts to connect to your Public IP address from inside the environment. There may be a way to stop this from happening, but I haven't used SonicWall in a while, so I can't give you instructions on how to do that.

Probably the best solution for the issue you are dealing with is to add an Internal version of the DNS zone that users use to access the server using the URL to your internal DNS servers. If you do this, you can have the same URL to access the server, but you can configure the internal version of the URL to connect to the private IP. This will allow internal users to connect to the server using the Same URL as external, and it won't impact external users' ability to access the server.
0
 

Author Comment

by:slattdog
ID: 39943299
That was kind of what I figured, but I'm not sure how to make that entry in the Windows Server 2008 DNS.  Any help there?
0
 

Author Comment

by:slattdog
ID: 39943375
just to update...

The local domain = domain.local
The public domain = domain.com
0
 
LVL 8

Accepted Solution

by:
N-W earned 500 total points
ID: 39944075
Just open up the DNS console on your 2008 DNS Server, expand your server listed on the left hand side, right click on "Forward Lookup Zones" and select "New Zone".

Go through the wizard selecting "Primary Zone" and specify the zone name as "domain.com" (there are other options to select which will depend on your environment).

When the zone is created, just add the required DNS records under that zone.
0

Featured Post

How Do You Stack Up Against Your Peers?

With today’s modern enterprise so dependent on digital infrastructures, the impact of major incidents has increased dramatically. Grab the report now to gain insight into how your organization ranks against your peers and learn best-in-class strategies to resolve incidents.

Question has a verified solution.

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

Redirected folders in a windows domain can be quite useful for a number of reasons, one of them being that with redirected application data, you can give users more seamless experience when logging into different workstations.  For example, if a use…
I've written instructions for one router type, but this principle may be useful for others of the same brand and even other brands of router. Problem: I had an issue especially with mobile devices that refused to use DNS information supplied via…
This tutorial will walk an individual through locating and launching the BEUtility application to properly change the service account username and\or password in situation where it may be necessary or where the password has been inadvertently change…
This tutorial will show how to configure a new Backup Exec 2012 server and move an existing database to that server with the use of the BEUtility. Install Backup Exec 2012 on the new server and apply all of the latest hotfixes and service packs. The…

790 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