Resolving External IP address Internally
|
From: -Draino- on 5 May 2010 22:10 When I access my server from outside my LAN I use something like http://173.191.14.188/page.html When I access my serer from inside my LAN I use something like http://servername/page.html I want to be able to access http://173.191.14.188/page.html from INSIDE my LAN but I can't. I have added a forward lookup A record in DNS but it still doesn't work. What do I need to do?
From: Larry Struckmeyer[SBS-MVP] on 5 May 2010 22:30 Why? - Larry Please post the resolution to your issue so others may benefit - Get Your SBS Health Check at www.sbsbpa.com > When I access my server from outside my LAN I use something like > http://173.191.14.188/page.html > > When I access my serer from inside my LAN I use something like > http://servername/page.html > > I want to be able to access http://173.191.14.188/page.html from > INSIDE my LAN but I can't. I have added a forward lookup A record in > DNS but it still doesn't work. > > What do I need to do? >
From: Cliff Galiher - MVP on 6 May 2010 00:00 There are a couple of things worth mentioning here: 1) the "page.html" has me very nervous. You should NOT be hosting web content on your SBS server. Just need to mention that. 2) A direct IP address (173.191.14.188) will cause the machine you are testing from to try to contact that IP directly. It won't go to DNS therefore your DNS record is doing nothing. This is expected behavior. If you couldn't access the IP address before, you probably won't now. 3) The problem likely lies with your router. Many routers do not do loopback connections. In other words, it expects connections to the public IP only from the external interface. It will ignore and drop traffic to the public IP from the internal interfaces, thus when you are attempting to access your machine with a public IP from within your LAN, the public IP is causing the local machine to contact the default gateway (your router) and your router is not forwarding that traffic back to your SBS machine. This isn't an SBS issue, but a router issue. To resolve it, you'll need to refer to your router documentation or contact their support staff. Each router is different. -Cliff "-Draino-" <randyd123(a)gmail.com> wrote in message news:55a3d697-1b4b-421f-b826-69e1526268ce(a)l28g2000yqd.googlegroups.com... > When I access my server from outside my LAN I use something like > http://173.191.14.188/page.html > > When I access my serer from inside my LAN I use something like > http://servername/page.html > > I want to be able to access http://173.191.14.188/page.html from > INSIDE my LAN but I can't. I have added a forward lookup A record in > DNS but it still doesn't work. > > What do I need to do?
From: -Draino- on 6 May 2010 02:49 On May 6, 12:00 am, "Cliff Galiher - MVP" <cgali...(a)gmail.com> wrote: > There are a couple of things worth mentioning here: > > 1) the "page.html" has me very nervous. You should NOT be hosting web > content on your SBS server. Just need to mention that. > 2) A direct IP address (173.191.14.188) will cause the machine you are > testing from to try to contact that IP directly. It won't go to DNS > therefore your DNS record is doing nothing. This is expected behavior. If > you couldn't access the IP address before, you probably won't now. > 3) The problem likely lies with your router. Many routers do not do > loopback connections. In other words, it expects connections to the public > IP only from the external interface. It will ignore and drop traffic to the > public IP from the internal interfaces, thus when you are attempting to > access your machine with a public IP from within your LAN, the public IP is > causing the local machine to contact the default gateway (your router) and > your router is not forwarding that traffic back to your SBS machine. This > isn't an SBS issue, but a router issue. To resolve it, you'll need to refer > to your router documentation or contact their support staff. Each router is > different. > > -Cliff > > "-Draino-" <randyd...(a)gmail.com> wrote in message > > news:55a3d697-1b4b-421f-b826-69e1526268ce(a)l28g2000yqd.googlegroups.com... > > > > > When I access my server from outside my LAN I use something like > >http://173.191.14.188/page.html > > > When I access my serer from inside my LAN I use something like > >http://servername/page.html > > > I want to be able to accesshttp://173.191.14.188/page.htmlfrom > > INSIDE my LAN but I can't. I have added a forward lookup A record in > > DNS but it still doesn't work. > > > What do I need to do?- Hide quoted text - > > - Show quoted text - We host a web application on our SBS2003 server. It's a package tracking app that the drivers log into for real time package tracking. It's not really "page.html" but it is a software app from Xcelerator that our Mobile-Tek handheld devices dial into. We use a "Dock Scanner" in the early AM to scan the load and all the packages go into the Xcelerator program. As the drivers scan their packages for loading they come off the database to show they are on the truck. When they are delivered the handhelds send that info to the server to show the package has been delivered. Something like UPS or FedEx. Our server has an IP address of 192.168.16.2 the router is 192.168.16.1. All our workstation use the SBS server for DNS. So all internal address get resolved using something like http://servername/Xcelerator/Mobile/..... what ever, to access the Xcelerator program. Outside the handhelds use http://173.181.14.188/Xcelerator/Mobile/......what ever. So I guess this is a router issue, I was just wondering if there was a way to resolve it differently when accessing Xcelerator internally.
From: Brian Cryer on 6 May 2010 04:51
"Cliff Galiher - MVP" <cgaliher(a)gmail.com> wrote in message news:B3B8223F-DDF2-4BE4-A3AA-ABFDE75D7DDF(a)microsoft.com... > There are a couple of things worth mentioning here: > > 1) the "page.html" has me very nervous. You should NOT be hosting web > content on your SBS server. Just need to mention that. It opens the possibility of security issues and I wouldn't recommend it for anything busy, but I wouldn't go so far as to say should not host. Just be careful and ensure you know what you are doing. -- Brian Cryer www.cryer.co.uk/brian |