sweetcaro
asked on
Public IP in internet explorer takes me to router instead of web server
Up till a week ago I was able to access http://mail.comreal.com from inside our office, now instead of taking me to the site it takes me to my router's admin page.
This is the situation: mail.comreal.com is the dns for our public ip which is 65.37.128.250
The router I'm using, linksys, has port 80 set to forward to my internal server.
If you go to mail.comreal.com form anywhere OUTSIDE our office, it works exactly how it's supposed to and it's going to the right place...
however, when I go to mail.comreal.com inside the office, it doesn't forward me to the server, it takes me to the router.
My workaround was to go to the hosts file and set mail.comreal.com to the ip of my server so it wouldn't take me to the router. However, little later i realized that a few applications like FTP were not working right.
I need to restore the dns or whatever is causing this name "mail.comreal.com" to go to my router instead of where it's supposed to go.
A day before this happened I had called earthlink (our sdsl provider) because we couldn't access a website (www.miamire.com) from the office and I thought it was some kind of dns issue. The guy on the phone said he could ping the site ok but he said he rebooted our modem and also changed the primary and secondary dns to smething else.
Could it be that somehow he messed something up so that internally port 80 is set to the router instead of forwarding to the server? Pinging mail.comreal.com gives the right public ip, but when going on the web it goes to the router.... if i type the public IP in internet explorer it also goes to the router.
Thanks, hope I was able to explain clearly... it's confusing
This is the situation: mail.comreal.com is the dns for our public ip which is 65.37.128.250
The router I'm using, linksys, has port 80 set to forward to my internal server.
If you go to mail.comreal.com form anywhere OUTSIDE our office, it works exactly how it's supposed to and it's going to the right place...
however, when I go to mail.comreal.com inside the office, it doesn't forward me to the server, it takes me to the router.
My workaround was to go to the hosts file and set mail.comreal.com to the ip of my server so it wouldn't take me to the router. However, little later i realized that a few applications like FTP were not working right.
I need to restore the dns or whatever is causing this name "mail.comreal.com" to go to my router instead of where it's supposed to go.
A day before this happened I had called earthlink (our sdsl provider) because we couldn't access a website (www.miamire.com) from the office and I thought it was some kind of dns issue. The guy on the phone said he could ping the site ok but he said he rebooted our modem and also changed the primary and secondary dns to smething else.
Could it be that somehow he messed something up so that internally port 80 is set to the router instead of forwarding to the server? Pinging mail.comreal.com gives the right public ip, but when going on the web it goes to the router.... if i type the public IP in internet explorer it also goes to the router.
Thanks, hope I was able to explain clearly... it's confusing
Last Comment
your Server should be doing DNS and DHCP with your router as nothing but a gateway.....then you can manually control these records
ASKER
DHCP is NOT enabled on the router. The server is a windows 2003 and is running DHCP.
mail.comreal.com is set in the hosts file to 192.168.20.3 (web server) and that was my workaround. However, some applications like FTP that run on that server, are still redirecting somehow back to the public ip (passive mode is set to the public ip which now reroutes to the router instead).
Are you saying I should also set the public ip 65.37.128.250 to 192.168.20.3 ?
Inside of the server I opened DHCP administration and this is a screen shot of what it looks like:
http://i173.photobucket.com/albums/w45/comreal/dhcp.jpg
I dont know if anything got changed there or is missing so that internally port 80 (web) goes to the server instead of the router. Is it because it's showing router to be the router ip and it shouldn't be there? Someone mentioned it should be a gateway not a router.
Also here's a screen show of tcp/ip properties (192.168.20.1 = router, 192.168.20.3 = server).
http://i173.photobucket.com/albums/w45/comreal/dhcp.jpg
mail.comreal.com is set in the hosts file to 192.168.20.3 (web server) and that was my workaround. However, some applications like FTP that run on that server, are still redirecting somehow back to the public ip (passive mode is set to the public ip which now reroutes to the router instead).
Are you saying I should also set the public ip 65.37.128.250 to 192.168.20.3 ?
Inside of the server I opened DHCP administration and this is a screen shot of what it looks like:
http://i173.photobucket.com/albums/w45/comreal/dhcp.jpg
I dont know if anything got changed there or is missing so that internally port 80 (web) goes to the server instead of the router. Is it because it's showing router to be the router ip and it shouldn't be there? Someone mentioned it should be a gateway not a router.
Also here's a screen show of tcp/ip properties (192.168.20.1 = router, 192.168.20.3 = server).
http://i173.photobucket.com/albums/w45/comreal/dhcp.jpg
It seems you also have DNS server inside your network?
If so, then work on DNS views. I am not sure if this is available or how do we implement views in windows DNS.
The basic is that you need to create two views; internal and external. For external view the mail.comreal.com will be resolved to 65.37.128.250 and for internal views it will resolve to 192.168.20.3.
Internal means your network probably 192.168.20.0/24 and external means all other.
Hope this will give you some idea.
Thanks,
Rajendra Adhikari
If so, then work on DNS views. I am not sure if this is available or how do we implement views in windows DNS.
The basic is that you need to create two views; internal and external. For external view the mail.comreal.com will be resolved to 65.37.128.250 and for internal views it will resolve to 192.168.20.3.
Internal means your network probably 192.168.20.0/24 and external means all other.
Hope this will give you some idea.
Thanks,
Rajendra Adhikari
Add a Host record in the Forward Lookup Zone for "Mail" - point it to 192.168.20.3.
The issue is that you have a registered PUBLIC name for your AD Namespace. All queries for your domain from inside your LAN must be resolved by your own DNS server as it is Authoritative for that zone.
The issue is that you have a registered PUBLIC name for your AD Namespace. All queries for your domain from inside your LAN must be resolved by your own DNS server as it is Authoritative for that zone.
ASKER
this is what my dns looks like, and I added the mail.
http://i173.photobucket.com/albums/w45/comreal/dns.jpg
I try going to the actual public ip on internet explorer: 65.37.128.250 and it's still taking me to the router instead of the web server. It's as if internally we are bypassing the router because the router has port 80 set to forward to 192.168.20.3 which is the server but for some reason inside the office this forward isn't working... the public ip on internet explorer should take me to the server but it's not, it's taking me to 192.168.20.1
mail.comreal.com works because in the hosts file i have it set to 192.168.20.3 unfortunately this is just a workaround to access our web server but it does not work with our FTP.... mail.comreal.com/uploads is our webserver... you can connect from outside because the passive mode directs it to the public ip, but in the office we get an error... and there are other applications we have trouble with because of this as well.
http://i173.photobucket.com/albums/w45/comreal/dns.jpg
I try going to the actual public ip on internet explorer: 65.37.128.250 and it's still taking me to the router instead of the web server. It's as if internally we are bypassing the router because the router has port 80 set to forward to 192.168.20.3 which is the server but for some reason inside the office this forward isn't working... the public ip on internet explorer should take me to the server but it's not, it's taking me to 192.168.20.1
mail.comreal.com works because in the hosts file i have it set to 192.168.20.3 unfortunately this is just a workaround to access our web server but it does not work with our FTP.... mail.comreal.com/uploads is our webserver... you can connect from outside because the passive mode directs it to the public ip, but in the office we get an error... and there are other applications we have trouble with because of this as well.
For starters, you have a Single-Label domain name - which I'm not even sure at this point matches your AD Namespace.
http://support.microsoft.com/kb/300684/en-us
You can't add "Mail" to that zone since it isn't the same.
Please right-click My Computer (on the server) and select Properties. On the Computer Name tab, please post the domain name as it shows there (or a screen shot).
http://support.microsoft.com/kb/300684/en-us
You can't add "Mail" to that zone since it isn't the same.
Please right-click My Computer (on the server) and select Properties. On the Computer Name tab, please post the domain name as it shows there (or a screen shot).
ASKER
Here are all the screen shots at once I added a few that might help including the name tab on computer properties
<center>
<a href="http://i173.photobucket.com/albums/w45/comreal/nametab.jpg" target="_blank">
<img src="http://i173.photobucket.com/albums/w45/comreal/th_nametab.jpg"></a>
<a href="http://i173.photobucket.com/albums/w45/comreal/router.jpg" target="_blank">
<img src="http://i173.photobucket.com/albums/w45/comreal/th_router.jpg"></a>
<a href="http://i173.photobucket.com/albums/w45/comreal/routing.jpg" target="_blank">
<img src="http://i173.photobucket.com/albums/w45/comreal/th_routing.jpg"></a>
<a href="http://i173.photobucket.com/albums/w45/comreal/forwarding.jpg" target="_blank">
<img src="http://i173.photobucket.com/albums/w45/comreal/th_forwarding.jpg"></a>
<br><br>
<a href="http://i173.photobucket.com/albums/w45/comreal/dns.jpg" target="_blank">
<img src="http://i173.photobucket.com/albums/w45/comreal/th_dns.jpg"></a>
<a href="http://i173.photobucket.com/albums/w45/comreal/tcpip.jpg" target="_blank">
<img src="http://i173.photobucket.com/albums/w45/comreal/th_tcpip.jpg"></a>
<a href="http://i173.photobucket.com/albums/w45/comreal/dhcp.jpg" target="_blank">
<img src="http://i173.photobucket.com/albums/w45/comreal/th_dhcp.jpg"></a>
</center>
<center>
<a href="http://i173.photobucket.com/albums/w45/comreal/nametab.jpg" target="_blank">
<img src="http://i173.photobucket.com/albums/w45/comreal/th_nametab.jpg"></a>
<a href="http://i173.photobucket.com/albums/w45/comreal/router.jpg" target="_blank">
<img src="http://i173.photobucket.com/albums/w45/comreal/th_router.jpg"></a>
<a href="http://i173.photobucket.com/albums/w45/comreal/routing.jpg" target="_blank">
<img src="http://i173.photobucket.com/albums/w45/comreal/th_routing.jpg"></a>
<a href="http://i173.photobucket.com/albums/w45/comreal/forwarding.jpg" target="_blank">
<img src="http://i173.photobucket.com/albums/w45/comreal/th_forwarding.jpg"></a>
<br><br>
<a href="http://i173.photobucket.com/albums/w45/comreal/dns.jpg" target="_blank">
<img src="http://i173.photobucket.com/albums/w45/comreal/th_dns.jpg"></a>
<a href="http://i173.photobucket.com/albums/w45/comreal/tcpip.jpg" target="_blank">
<img src="http://i173.photobucket.com/albums/w45/comreal/th_tcpip.jpg"></a>
<a href="http://i173.photobucket.com/albums/w45/comreal/dhcp.jpg" target="_blank">
<img src="http://i173.photobucket.com/albums/w45/comreal/th_dhcp.jpg"></a>
</center>
ASKER
oops sorry here they are
http://i173.photobucket.com/albums/w45/comreal/nametab.jpg
http://i173.photobucket.com/albums/w45/comreal/router.jpg
http://i173.photobucket.com/albums/w45/comreal/routing.jpg
http://i173.photobucket.com/albums/w45/comreal/forwarding.jpg
http://i173.photobucket.com/albums/w45/comreal/dns.jpg
http://i173.photobucket.com/albums/w45/comreal/tcpip.jpg
http://i173.photobucket.com/albums/w45/comreal/dhcp.jpg
http://i173.photobucket.com/albums/w45/comreal/nametab.jpg
http://i173.photobucket.com/albums/w45/comreal/router.jpg
http://i173.photobucket.com/albums/w45/comreal/routing.jpg
http://i173.photobucket.com/albums/w45/comreal/forwarding.jpg
http://i173.photobucket.com/albums/w45/comreal/dns.jpg
http://i173.photobucket.com/albums/w45/comreal/tcpip.jpg
http://i173.photobucket.com/albums/w45/comreal/dhcp.jpg
Try changing the port on router to something like 8080 on the router. Then, If your current configuration does not take you to the server then, try the split DNS. "HOW TOS" on the windows 2003 Server is given here:
http://articles.techrepublic.com.com/5100-10879-6097830.html
Hope this will resolve your problem
Thanks,
Rajendra Adhikari
http://articles.techrepublic.com.com/5100-10879-6097830.html
Hope this will resolve your problem
Thanks,
Rajendra Adhikari
Ok, the domain name matches AD - that much is good. However, a single-label domain doesn't register properly in DNS.
Read the article to fix that part.
As for why you can't get to your webserver internally - you are attempting to leave the network through the router then come back in. Since the request is a local address and is coming back from outside the router it is considered "spoofing" and will likely be blocked at the router or the ISP.
You'll have to continue with HOSTS or add the external namespace to your DNS server.
Read the article to fix that part.
As for why you can't get to your webserver internally - you are attempting to leave the network through the router then come back in. Since the request is a local address and is coming back from outside the router it is considered "spoofing" and will likely be blocked at the router or the ISP.
You'll have to continue with HOSTS or add the external namespace to your DNS server.
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Wow Netman66 THANK YOU! You just hit a cell in my brain and that was it! I remembered a week ago I had gone into the router's firewall and had Enabled NAT Redirection... Disabling that just fixed my issue!!!
God sometimes I feel stupid.... thanks to everyone for helping, this is awesome :)
God sometimes I feel stupid.... thanks to everyone for helping, this is awesome :)
Windows Server 2003
Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).
129K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
My suggestion now is to put the public DNS server IP (The one your ISP provided) on your hosts instead of getting it from the router. It will resolve your problem for now.
Check if there is any setting on your router DHCP setting where you can explicitly define DNS IP for distributing its clients.
Goodluck,
Rajendra Adhikari