Sign-in / Sign-up
Your question
Solved

Access FTP over LAN

Tags:
  • FTP
  • LAN
  • Networking
  • Routers
Last response: in Networking
March 29, 2014 1:56:59 AM

Hi All,

The set up :
Router : Netgear D200-100UKS
FTP : Mybook Live 2TB
OS : Win 7

Problem:
FTP is able to be accessed over WAN using no-ip forward to port 21 vai router.

On the LAN the only way to access the FTP is ftp://192.168.2.xxxxx but not using the host name. i.e xxhotnamexx.no-ip.biz

it seems the host name can only work over WAN and not LAN, does anyone know why that would be???

Much appreciated

More about : access ftp lan

a b X LAN
March 29, 2014 2:01:54 AM

Your router probably doesn't support what's known as 'hairpin NAT', where the data has to go out through the firewall and then back in.
m
0
l
March 29, 2014 2:16:36 AM

Someone Somewhere said:
Your router probably doesn't support what's known as 'hairpin NAT', where the data has to go out through the firewall and then back in.


Thanks

Is there a solution for this.........?
m
0
l
Related resources
March 29, 2014 2:33:52 AM

I`m not sure but DMZ of a router is outside the firewall of the router.
Or it can have it`s own set of rules in regard to firewall settings.

But it will leave it open of course to all sorts.
Unless you set up the type of log in for a user and how they can interact with files or folders.

Any service that is being provided to users on the external network can be placed in the DMZ. The most common of these services are:

Web servers
Mail servers
FTP servers
m
0
l
a b X LAN
March 29, 2014 2:43:54 AM

No, DMZ won't fix it.

It's the fact that the NAT and firewall in the router that someone connected on the internal side of the router might want to access the external IP of the router. It's quite a rare situation, and many consumer routers don't support it.

Two options:
  • Get a router that does. Finding out which do could be difficult, though.
  • Put an entry in the DNS server in the router to make it return the internal IP for the domain name. Most consumer routers won't support that, etiher.


  • Or just set it up so it talks to the internal IP by default.
    m
    0
    l
    March 29, 2014 2:47:14 AM

    Someone Somewhere said:
    No, DMZ won't fix it.

    It's the fact that the NAT and firewall in the router that someone connected on the internal side of the router might want to access the external IP of the router. It's quite a rare situation, and many consumer routers don't support it.

    Or just set it up so it talks to the internal IP by default.
    How do you do that?

    m
    0
    l
    a b X LAN
    March 29, 2014 2:49:03 AM

    What's the system that's trying to access the FTP server? Change the external domain name to the internal IP address.
    m
    0
    l
    March 29, 2014 3:01:15 AM

    Someone Somewhere said:
    What's the system that's trying to access the FTP server? Change the external domain name to the internal IP address.


    System is normal WIN 7 Professional desktop, when you say change the domain name would that be the same as changing the Workgroup name?
    m
    0
    l
    March 29, 2014 3:02:42 AM

    You know he`s right thinking about it.

    You would need a router capable of what the mod is saying.
    m
    0
    l
    a b X LAN
    March 29, 2014 3:04:14 AM

    No, I'm talking about changing where you entered 'yourdomain.noip.com' to '192.168.2.x'.
    m
    0
    l
    March 29, 2014 3:06:53 AM

    Someone Somewhere said:
    No, I'm talking about changing where you entered 'yourdomain.noip.com' to '192.168.2.x'.


    So basically I have to use ftp://192.168.2.xxx no other way around it.

    Oh well....life can't always be perfect.

    Thanks to everyone that answered.....
    m
    0
    l

    Best solution

    a b X LAN
    March 29, 2014 3:08:17 AM

    Either that or a new router.
    Share
    March 29, 2014 3:13:41 AM

    Someone Somewhere said:
    Either that or a new router.


    We just bought the router and it's out of the 30 day return period, I must admit that I never thought the router would prevent a NAT loopback.......

    But as the workaround would be to just use ftp://192.168.2.xxxxx then it's something we can live with...... but will keep in mind for future reference.

    Cheers
    m
    0
    l