?
Solved

Access Local Server Via Public IP

Posted on 2014-03-20
4
Medium Priority
?
482 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
[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
  • 2
4 Comments
 
LVL 42

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 2000 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

Get real performance insights from real users

Key features:
- Total Pages Views and Load times
- Top Pages Viewed and Load Times
- Real Time Site Page Build Performance
- Users’ Browser and Platform Performance
- Geographic User Breakdown
- And more

Question has a verified solution.

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

BIND is the most widely used Name Server. A Name Server is the one that translates a site name to it's IP address. There is a new bug in BIND (https://kb.isc.org/article/AA-01272), affecting all versions of BIND 9 from BIND 9.1.0 (inclusive) thro…
A safe way to clean winsxs folder from your windows server 2008 R2 editions
This tutorial will give a an overview on how to deploy remote agents in Backup Exec 2012 to new servers. Click on the Backup Exec button in the upper left corner. From here, are global settings for the application such as connecting to a remote Back…
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
Suggested Courses

770 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