network webpage question

[Guest]

I have a 3 machines LAN with a laptop, 1 winXP and a win2K server. I have a
webpage and FTP site on the win2K and the a Belkin F5D7231 router/firewall
connects the LAN to broadband services and links the wireless LAN using
another Belkin bridge F5D7230. People can FTP and browse the win2k server
from outside the LAN but we cannot. This is not very productive because we
are constantly updating the site and It is best checked browsing outside the
LAN, from the world wide web, but using our own internet connection. Belkin
says that it can't be done once our machine is on the same LAN and behind the
same firewall where our webservices are set. Is it a win2k problem? Is a
Belkin software problem? Does anyone out there have the same problem or could
recommend hardware that bypasses this issue?

many thanks

Ted

 

[BobC]

I have a 3 machines LAN with a laptop, 1 winXP and a win2K server. I have a
webpage and FTP site on the win2K and the a Belkin F5D7231 router/firewall
connects the LAN to broadband services and links the wireless LAN using
another Belkin bridge F5D7230. People can FTP and browse the win2k server
from outside the LAN but we cannot. This is not very productive because we
are constantly updating the site and It is best checked browsing outside the
LAN, from the world wide web, but using our own internet connection. Belkin
says that it can't be done once our machine is on the same LAN and behind the
same firewall where our webservices are set. Is it a win2k problem? Is a
Belkin software problem? Does anyone out there have the same problem or could
recommend hardware that bypasses this issue?

many thanks

Ted

There is no route from your LAN to the Internet then back. To view the web
site from your LAN you need to use http://YourServersPrivateIpaddress. From
the Internet the url is http://YourServerPublicIpaddress.

I'm not familiar with your router but this is a limitation of cheaper
consumer level routers.

 

[Guest]

Can anyone please recommend a router that will allow me to browse my
development page hosted on my LAN WIN2K webserver over, i need to see it on
the internet http://YourServerPublicIpaddress.

thanks,

 

[Sole Viktor]

you shouldnt need that, your problem is that when you use the webservers
address, for example www.yourcompany.com you are using internet dns to
resolve it into the public ip address of the server, wich you cant access
thru your current router.

the cheap solution is to edit your hosts file, and add an entry with
www.yourcompany.com that points to the internal ip address, for example
192.168.1.10

that will fool your internal machines to think they are access the public
name, but actually hitting your internal address.

 

[Guest]

I understand your suggestion, but the problem is that even if I enter my
internal IP to access the server, we have written hypertext links
ie:"http://myserver.ftpfolder/myfile.htm.

These files cannot be accessed this way and I get IE error 400. What can i do?

thanks

Ted

 

[DrTechMech]

Looking for Free Hypertext Application Demo's & VB Scripting Info.

Check out this developers web site:

http://personal.nbnet.nb.ca/freehtas/

Best Regards.

 

[Phillip Windell]

I understand your suggestion, but the problem is that even if I enter my
internal IP to access the server, we have written hypertext links
ie:"http://myserver.ftpfolder/myfile.htm.

If the links are on the same site on the same server they can be re-written
to be "relative links". But even if you used IP#s there will still be
problems if you ever involve a proxy because IE doesn't acknowledge them as
IP# and will pass them to the proxy to be resolved which will always fail.

Intranet site is identified as an Internet site when you use an FQDN or an
IP address
http://support.microsoft.com/default.aspx?scid=kb;en-us;303650

I may not be totally ware of the situation because I don't have any earlier
posts, bu if you are having trouble accessing the page while "inside" the
network, but it works from outside the network,...then you need to make sure
that the Site's URL as you are entering it must resolve the internal IP# and
not the external public IP# that you have it "published" by on the outside.
You cannot use the public IP# becuase you cannot make a "u-turn" through a
NAT Device if it is the NAT device that is publishing the site to the
outside.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/ISA2004_AccessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/techinfo/Guidance/2004.asp
http://www.microsoft.com/isaserver/techinfo/Guidance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
-----------------------------------------------------