Anybody know anything about Apache server etc, wierd IP problem.

Ok here's the score. My hosting service keeps disappearing so i'm trying to set up Apache on a local machine and hopefully a working email server (thats more important as i'm lost without my emails). Now... I can access the server on 192.168.x.x and also by typing my external IP into a proxy like hidemyass.com but for some reason I can't access my external IP directly as it pops up the router log in box. Any ideas? Pretty sure this shouldn't be happening and remote admin on the router (Netgear WNR2000) is turned off.

13 Comments

Not sure if my suggestion has any value, but I'm trying to brainstorm!

Two things:
Is port forwarding activated on your router, so you are able to not just access your server from your internal IP range.
Is it possible that the ISP you are using has a proxy itself which is the reason you are unable to access your external IP?

If I'm wrong, I hope someone more knowledgeable will correct me.

Original Poster

Whats up Doc;6313768

Not sure if my suggestion has any value, but I'm trying to brainstorm!Two … Not sure if my suggestion has any value, but I'm trying to brainstorm!Two things:Is port forwarding activated on your router, so you are able to not just access your server from your internal IP range.Is it possible that the ISP you are using has a proxy itself which is the reason you are unable to access your external IP?If I'm wrong, I hope someone more knowledgeable will correct me.



Yeah its all set up fine, port forwarded etc. As I say, I can access my own IP from an external proxy server but not direct. If I try to go direct the router thinks i'm trying to log in. Now to me that should only happen if I go to 192.168.1.1. Poxy bloody thing :lol:

so you are setting the external ip in your client software but trying to access it from the same ips subnet?
if thats the case the nat on the router will kick in and the access will be limited to the router.
can you access an externally located machine via logmein or something?, that will be the test as really this system has no use otherwise.
to get your local machine to pick up its email use that machines internal ip

Original Poster

It's difficult to explain really. Should be easier now the DNS records have updated....

If I want to access my webserver locally I have to goto 192.168.1.14. If I just type [url]www.shengis.net[/url] into firefox I get this :

http://www.shengis.net/hukdpics/ws1.jpg

Through a proxy I get this:

http://www.shengis.net/hukdpics/ws2.jpg

Incidentally, I have no idea if the pictures above are showing or not (unless I look at this page through a proxy), due to the aforementioned problem :lol:

that will be the dns either on the router, u can try an entry into the local hosts file pointing shengis.net to the local ip of the machine or even the external ip but not really sure its possible to bypass the dns on the router to that extent, as you say it would mean hiding the fact you are on the lan from the router(???), any joy with the routing table in the router?

Page is working fine for me.
I presume you've fixed it then.

Original Poster

maddogb;6321572

that will be the dns either on the router, u can try an entry into the … that will be the dns either on the router, u can try an entry into the local hosts file pointing shengis.net to the local ip of the machine or even the external ip but not really sure its possible to bypass the dns on the router to that extent, as you say it would mean hiding the fact you are on the lan from the router(???), any joy with the routing table in the router?



Already tried the hosts approach, I was sure that would work. What's really weird about it is that if you access it by the dotted IP locally (192 etc) its fine but even setting the domain with the hosts file to the local IP fails. It's a real mystery as it should be the same as just entering the IP as far as the routers concerned. Was trying to get hmailserver running earlier, got it sort of working but then had massive fail trying to get subdomains working.

Original Poster

unknownuser;6322330

Page is working fine for me.I presume you've fixed it then.



That's the point, it's fine for anybody but local users ;-) Offline now anyway while I sort out remote hosting........

Shengis;6322487

Already tried the hosts approach, I was sure that would work. What's … Already tried the hosts approach, I was sure that would work. What's really weird about it is that if you access it by the dotted IP locally (192 etc) its fine but even setting the domain with the hosts file to the local IP fails. It's a real mystery as it should be the same as just entering the IP as far as the routers concerned. Was trying to get hmailserver running earlier, got it sort of working but then had massive fail trying to get subdomains working.


If you ping it does it get the right ip address?
if you do "tracert yourdomain" does it try to go via the router?

lol, this one of those things where you spend hours/days chasing and in the end just create shortcuts on the local machines with the IPs entered numerically,
can't see how you can get round this m8,
Whilst the hosts file should work with the internal ip it looks like no matter what you do(aprt from using a proxy) the dns/nat on the router will kick in (caching makes it more awkward as testing relies on strict procedural reboots etc.)
When you think about it all is actually working "as it should"
1. when you enter the domain name the isp dns resolves it to your routers external address, your router, which when handed the packet recognises correctly its own address and kicks up the admin box because the only matching entry in its firewall/routing table is from your machine and the remote admin exclusion doesn't apply because its a local address.

2.entering the external ip in the host file will not bypass the above routine but entering the local ip should so you need to clarify why this is not working.

have you got a page by page guide to the routers admin functions?

Original Poster

maddogb;6323347

1. when you enter the domain name the isp dns resolves it to your routers … 1. when you enter the domain name the isp dns resolves it to your routers external address, your router, which when handed the packet recognises correctly its own address and kicks up the admin box because the only matching entry in its firewall/routing table is from your machine and the remote admin exclusion doesn't apply because its a local address.



Even though i've sort of given up, should that actually happen though? If you connect to the router through a lan IP it pops up the login box, which it should do. But should it really do that for what is effectively an external IP, even though that external IP is the one it leeched from the modem? Effectively the routers talking to itself :lol: I'm pretty sure it shouldn't happen but it seems pretty common on netgear stuff from looking on google. Maybe there is no solution apart from using the local lan IP as a shortcut and a proxy just to check outside machines can connect. I just don't like to think that is the only answer though as it seems lie a bit of a bodge to me.

My only 'workable' idea was to get firefox portable, find a free proxy and set it up in that. Finding a free proxy that actually works though....

Shengis;6339023

Even though i've sort of given up, should that actually happen though? If … Even though i've sort of given up, should that actually happen though? If you connect to the router through a lan IP it pops up the login box, which it should do. But should it really do that for what is effectively an external IP, even though that external IP is the one it leeched from the modem? Effectively the routers talking to itself :lol: I'm pretty sure it shouldn't happen but it seems pretty common on netgear stuff from looking on google. Maybe there is no solution apart from using the local lan IP as a shortcut and a proxy just to check outside machines can connect. I just don't like to think that is the only answer though as it seems lie a bit of a bodge to me.My only 'workable' idea was to get firefox portable, find a free proxy and set it up in that. Finding a free proxy that actually works though....



it will depend on the router doing any dns caching i would of thought and only netgear will know that.
out of curiosity did you try with both open dns and your isp dns? also are you using ddns though this will only cause problems if you are rebooting the router/renewing its external ip often
how about the local machine lan set up is it on static ips or dhcp?
Think you will need to plan this carefully, execute it and wait 24hrs to test so that the isp dns entries etc are all up to date also its likely to be more successful if you manually enter the external dns server entry in local ip setup

Just to rule out your own local computer dns cache:

Have you tried ipconfig /flushdns in the command prompt ?
Post a comment
Avatar
@
    Text
    Top Discussions
    1. 75% off Sky TV for existing customers. Only works when you call the specifi…17386133
    2. (heads up) Mini SNES price finally dropped on Amazon pre orders68
    3. Ebid over Ebay22
    4. Just heard this...2 ★★★★★★★★★★★★★★ congrats to all on 392k ★★★★★★★★★★★★★★7763999

    See more discussions