Welcome to ISAserver.org
Forums |
Register |
Login |
My Profile |
Inbox |
RSS 
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Web Publishing Problem
|
Users viewing this topic:
none
|
Logged in as: Guest
|
Login  | |
|
Web Publishing Problem - 30.May2001 3:59:00 AM
|
|
|
tilke
Posts: 3
Joined: 30.May2001
From: Ridgefield, CT, USA
Status: offline
|
ISA Server is sitting behind Linksys Cable/DSL router. Router has internal IP address of 192.168.1.1; ISA/IIS Server is 192.168.1.2. Implemented installation as per excellent Shinder tutorial. Published web site uses port 8082 on IIS. Request for web site from external client is getting to ISA as evidenced by ISA Session Monitoring. Request is also getting to IIS as evidenced by request for Index.htm in IIS W3SVC3 log. Some response is getting back to client as evidenced by 'Web Site found. Waiting for Reply', and the Linksys router outgoing log indicates a handshake of some sort. Unfortunately, client browser simply hangs and no further data is delivered to client. Request for web site works fine from within LAN. Any ideas would be greatly appreciated! Thanks, Peter Tilke
|
|
|
|
RE: Web Publishing Problem - 31.May2001 9:25:00 PM
|
|
|
tshinder
Posts: 47669
Joined: 10.Jan.2001
From: Texas
Status: online
|
Hi Peter, Interesting problem. I'm impressed that the request is making it to the external interface of the ISA Server, given that the external interface has a private IP address. I assume that you're using a 1 to 1 mapping between the router and the external interface of the ISA Server. Try binding a public IP address to the external interface of the ISA Server and create a DNS entry for that interface and see how that works. HTH,
Tom ------------------
Tom Shinder
http://www.isaserver.org/shinder/
 Get It Here
|
|
|
|
RE: Web Publishing Problem - 1.Jun.2001 4:09:00 AM
|
|
|
tilke
Posts: 3
Joined: 30.May2001
From: Ridgefield, CT, USA
Status: offline
|
Tom, Thanks so much for looking into this. I managed to identify and resolve the problem when I discovered that I was actually publishing small web pages. It turns out that there are some incompatibilities in supported TCP/IP packet sizes with DSL PPPoE that I haven't delved into completely... Any TCP/IP packet larger than 1492 bytes was getting trashed during publishing. If I explicitly set the MTU parameter on the Linksys router (now 192.168.1.2), and the exteranl interface on the ISA machine (192.168.1.1) to be 1492, then suddenly everything works! I imagine this would be a problem for many people trying to publish from behind a DSL connection with PPPoE. Thanks again for your help and the excellent tutorial: I'm going to buy your book. Cheers, Peter Tilke quote:
Originally posted by tshinder:
Hi Peter,Interesting problem. I'm impressed that the request is making it to the external interface of the ISA Server, given that the external interface has a private IP address. I assume that you're using a 1 to 1 mapping between the router and the external interface of the ISA Server. Try binding a public IP address to the external interface of the ISA Server and create a DNS entry for that interface and see how that works. HTH,
Tom
|
|
|
|
RE: Web Publishing Problem - 4.Jun.2001 2:21:00 AM
|
|
|
tilke
Posts: 3
Joined: 30.May2001
From: Ridgefield, CT, USA
Status: offline
|
Tom, You're absolutely correct. Using the ping test I reduced the MTU to 1464, I believe this is because ping puts a 28 byte header in, yielding 1492, but I'll follow the recommendation and reduce the MTU size to 1464. Thanks again, Peter
|
|
|
|
 New Messages |
 No New Messages |
 Hot Topic w/ New Messages |
 Hot Topic w/o New Messages |
 Locked w/ New Messages |
 Locked w/o New Messages |
|
 Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts |
|
Printable Version
RE: Web Publishing Problem - 