Access to local server .net application via public ip address
Hi,
(I logged a previous question some months ago which didn't get a definitive answer and now I have the same issue on a client network.)
I have setup an asp.net application on a local server (actually a win7 machine) and setup the router to allow access via public ip address. This previously stopped working when a new model router was used - a problem which was then solved by using the old router again!
Yesterday for some unknown reason, this issue has returned with no change in router or anything else we can tell for that matter. I can give clients the local server address which works fine but they now have to use 2 shortcuts to access the application depending on whether they're in the office or not - annoying to say the least.
To clarify, when accessing the application using the public ip address when connected to the local lan, browsers just seem to hang (as opposed to some sort of page not found error). This happens on various client pcs with various browsers.
Can anyone shed some light or point me in the direction of the relevant router settings to check - I can only think there's either been an automated BT firmware upgrade or a Windows update perhaps?
Thanks
(I logged a previous question some months ago which didn't get a definitive answer and now I have the same issue on a client network.)
I have setup an asp.net application on a local server (actually a win7 machine) and setup the router to allow access via public ip address. This previously stopped working when a new model router was used - a problem which was then solved by using the old router again!
Yesterday for some unknown reason, this issue has returned with no change in router or anything else we can tell for that matter. I can give clients the local server address which works fine but they now have to use 2 shortcuts to access the application depending on whether they're in the office or not - annoying to say the least.
To clarify, when accessing the application using the public ip address when connected to the local lan, browsers just seem to hang (as opposed to some sort of page not found error). This happens on various client pcs with various browsers.
Can anyone shed some light or point me in the direction of the relevant router settings to check - I can only think there's either been an automated BT firmware upgrade or a Windows update perhaps?
Thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
OK, I finally setup 2 entries in the hosts file on each pc, the first pointing to the local lan and the second, the wan ip address. This also allows me to use an alias for the site as suggested by brwwiggins.
ASKER
1. We still access the site using the same public ip from outside the lag so it hasn't changed
2. The site still works fine from outside the lan so I guess no blocking of any sort can be active.
3. The router has not been changed since it was working a couple of days ago so it can't be any sort of limitation with that.
We do not have dns running and it's an area where my knowledge fails me.. could you guide me on where to start as that sounds like the solution, regardless of the cause of the problem?