Microsoft Small Business Server and FTP
Home > IT Answers > Microsoft Windows > Microsoft Small Business Server and FTP
Tswirka
25 pts.
0
Q:
Microsoft Small Business Server and FTP
Windows Server 2003, FTP, SBS 2003
I have a Microsoft Small Business Server 2003 and I host a public FTP server on a Windows 2003 Server on the same network. Public access to my FTP sever is ftp.zevcohen.com. My clients can connect to the internal FTP server just fine from outside of my network. The problem is that my internal users cannot access the internal FTP server using ftp.zevcohen.com.  The internal users can only access the internal FTP server by browsing directly to it through the network. Normally this would not be an issue, but I would like to give my internal network users the ability to access the FTP server using ftp.zevcohen.com. From what I can determine, when I try to access the internal FTP server with the ftp.zevcohen.com from inside the network (either through Internet Explorer or the command line FTP utility), the request is never leaving my internal network, so that it can route through the public IP address assigned to the FTP site and then come back in to the FTP server. Does anyone have a set up like this or know of a solution?

Thanks in advance.

 



Software/Hardware used:
Windows Small Business Server 2003, Windows Server 2003
ASKED: Oct 6 2009  6:37 PM GMT
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
RELATED QUESTIONS
0
Labnuke99
26290 pts.
0
A:
 RATE THIS ANSWER
0
Click to Vote:
  •   0
  •  0
  • AddThis Social Bookmark Button
What is your internal DNS domain? Is it the same as your external domain? You may need to create an internal DNS record to point to the internal IP address of this host for your internal users to be able to access by the system name.

In the IT trenches? So am I - read my IT-Trenches blog
Last Answered: Oct 6 2009  6:48 PM GMT by Labnuke99   26290 pts.
  •   
0
0
RSS - Discussions Help
Discuss This Answer:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _



_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Tswirka   25 pts.  |   Oct 6 2009  7:05PM GMT

My internal DNS domain name is xxxxxx.MSFT, (the xxxxxx is not the same as my external domain name.
I thought I might have to add something in DNS, but I wasn’t sure how to add it. Can you elaborate on that if you think that’s the answer?

 

mrdenny   46810 pts.  |   Oct 6 2009  8:23PM GMT

The problem is that the way NAT works traffic can’t go out a network port then back in the same network port.

The easiest solution would be to add a DNS zone to your internal DNS servers called <a href="http://ftp.zevcohen.com" title="http://ftp.zevcohen. " target="_blank">ftp.zevcohen.com</a> (not <a href="http://zevcohen.com" title="http://zevcohen. " target="_blank">zevcohen.com</a> with a record called ftp) and setup a CNAME for the name “.” pointing to the internal DNS record for the FTP server. This way internal users can hit the FTP server via the name but without going out to the public net.

 

mrdenny   46810 pts.  |   Oct 6 2009  8:24PM GMT

Man the forum mangled that comment I just name.

If you have questions as to what that’s supposed to be let me know.

 

Troy Tate   0 pts.  |   Oct 7 2009  1:10PM GMT

MrDenny’s answer is the best approach with setting up the internal DNS zone with the same name as the external domain name. Then create the appropriate records for internal resources using internal addresses. This is called split-horizon (or split) DNS. See this article about split DNS for additional information.

 

Tswirka   25 pts.  |   Oct 7 2009  4:01PM GMT

I added the DNS zone as instructed by mrdenny and everything works perfectly. Thanks to everyone for their help and input.

 

NetSupport   430 pts.  |   Oct 7 2009  4:02PM GMT

Or Just add an entry to the clients hosts file. xxx.xxx.xxx.xxx  <a href="http://ftp.zevcohen.com" title="http://ftp.zevcohen. " target="_blank">ftp.zevcohen.com</a>

This would have to be done on each Client PC.

 
0