Linksys AG241 port forwarding question.

Discussion in 'General Discussion' started by Anonymous, May 9, 2005.

  1. Anonymous

    Anonymous Guest

    Hi folks,
    I switched from cable to adsl internet so i need to buy an adsl router. I bought netgear DG834, but it is not working out for me. I run web and mail servers. I have got a static ip address and 4mb pipe. I set up the forwarding rules and stuffs. When people outside my network try to access my public ip address they get my server page. But when i try to access public ip address i am getting router's webpage. I dont want this to happen. I was using linksys cable 4port router and i didnt have this problem. So i giving back my netgear and thinking about getting a linksys adsl router. Is anyone using it here? I just wanna make sure that this router has got such kinda problems.

    Netgear's problem is stated here (known issue number 2). I am using latest beta netgear firmware. So updating firmware wont work. Please help me. Thanks in advance.
  2. Guyfromhe

    Guyfromhe Network Guru Member

    Many NAT devices won't support loopback theres many little DNS tricks you can use to get aruond that, I believe theres a custom firmware that allows you to enable loopback, but i'm not 100% sure.
  3. Anonymous

    Anonymous Guest


    But the linksys cable 4port router i have does support loopback connections. Thats the main reason why i am getting linksys adsl router AG241. Do you know anyother adsl router that supports loopback connections? Or is there any tutorials about enabling loopback connections in firmware? What are those little dns tricks that i can use to get around that? Thanks alot in advance.

  4. Guyfromhe

    Guyfromhe Network Guru Member

    i don't know if that ADSL router supports loopback or not, i have never seen it as an option in any linksys firmware, I believe some custom firmware have it but I don't think you can run custom firmware on that device... I suggest getting it from somewhere you can return it to if it doesn't and giving it a try...
    Now theres a couple things you can do in DNS to get around that...
    the easist thing to do if you only have 2 or 3 computers is to add an entry in hosts file to point to the internal server ip rater than the public IP for that domain...
    next thing you can do is setup a subdomain that points to the internal IP of the machine thats your webserver and only use that address from inside your lan. and lastly if you run your own DNS server you can take control of the zone where your domain is in and point it directly at the servers internal ip..
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice