Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

internet connection share / HTTPS: problems

Status
Not open for further replies.

drev1l

IS-IT--Management
Apr 25, 2002
14
GB
Collective Brains,

I am trying to use ICS on a Win 2K pro machine to allow connection to a secure web page only accessable via a dial up connection. On the ICS machine I can dial-up to the specific page, and connect to it's HTTPS login page, but when I set a static route on a client pc to access this login page, I get the "you are about to enter a secure web page" dialog box then it fails to load the page in!!!

Are there any settings within the ICS appl that I need to change ??
has anyone encountered a sinmilar problem?
I presume that it is something to do with the way https establishes a secure connection to the client pc, any tips on how this actually works..?

Thanks in advance for the thought processing!

drev1l
 
Here are my thoughts,

The windows 2000 ICS that I used did not act as a router, rather, it let other computers use its internet connection. This means that the "main" computer with an ip of 63.22.134.90 lets computer 192.0.0.2 use its connection to send a request to https:\\securesite.com. However, the secure site can tell that the request came from 192.0.0.2 but "wrapped" with the address of 63.22.134.90.(Think of it, how many 192.0.0.2 computers are there out there?) I do not know enough about tcp/ip to tell exactly what happens, but this did happen to me. I installed winroute, and my problem was solved because my client computer sent the request to my "gateway" which sent its own request to the secure server, then sent the answer to the client.

This is a little vauge, but I figured it out because I could not send email from the clients, and the pop server used a form of hostname authentication. That is, if you are on our network, you can send mail. 63.*.*.* was on the network, 192* was not, so we could not send email.

Sorry I can't say exatly what the deal is, but this is close. Install winroute and you should be set.

If anyone can tell me the technical part of this "wrapping" I described, I would appriciate it.

CJB
 
CJB

Thanks for the quick response, I am looking into a trial version of winroute and testing to see if I can get it to bend to my will. I have a few issues with the product though. We use static IP inside the office and it appears that WInRoute insists on using DHCP to work. I can set an IP range covering the set of five workstations that need access to this HTTPS site, but the users still need to browse out to the internet via our LAN G/W, ONLY using the Dial-up for the one site. So far I haven't been able to set up the Winroute server PC to route only the one ip address to the dial-up and the rest to the LAN G/W. in the route list it has the route 0.0.0.0 pointing to itself and thereby routing everything through the dial-up.

Any further advice about this would be greatfully received.

drev1l

P.S. I hope you wrap up warm ;-)
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top