Re: New Thread for Tony Su

From: Tony Su (anonymous_at_discussions.microsoft.com)
Date: 06/26/04 

Date: Fri, 25 Jun 2004 22:52:31 -0700

First, as Jim suggests...
I am going to assume that access to your website from the
Internet will be on port 80. If you intend to access your
website from the Internet on port 443 (SSL), then run the
Telnet test on that port.

Run your Telnet test again against your WAN IP address (or
FQDN if you're deploying more than one website on the WAN
IP address). Do not connect from a remote box outside your
Internet router to avoid possible filtering in that box.

If successful, then test from outside your Internet
Gateway router.

If not successful, then you need to inspect your Web
Publishing rule. A candidate for problems might be the
bridging tab. Another candidate might be how you're
referencing your interior website... try referencing your
website by IP address or if you must reference the site by
FQDN, then verify your LAN name resolution is accurate.

And, review your Incoming Web Listener. If ISA isn't
listening, your Web Publishing rule won't be applied.

As always, stop/restart the FW and Web Proxy services if
you modify anything.

If you <still> can't find the problem, if you haven't
already check your ISA WEBEXTND logfiles. The error code
can be a big clue what your problem is.

Tony Su

>-----Original Message-----
>Toni,
>
>Telenet port 80 from behind the ISA works fine.
>
>Claus
>"Tony Su" <anonymous@discussions.microsoft.com> wrote in
message
>news:209b401c4595f$737e78d0$a501280a@phx.gbl...
>> Telnet on port 80 is a fundamental test you have to
pass.
>>
>> Run the same test from behind ISA to the website. If it
>> still fails, then the WWW service and/or website
>> configuration is faulty. If it passes, then you can
verify
>> that ISA should be able to pass requests to an actively
>> listening service, so can then focus on ISA.
>>
>> Tony Su
>>
>>
>>
>>
>> >-----Original Message-----
>> >Toni,
>> >
>> >I was called away for an emergency in Canada and just
>> came back. I thought
>> >it might be easier to start a new thread on this. Even
>> though I'm hosting
>> >the website in question currently on another server, I
>> still would like to
>> >resolve the problem on the original ISA and appreciate
>> your help.
>> >
>> >Here is your last post to the old thread:
>> >
>> ><Do this test
>> >
>> ><telnet [WAN IP] 80
>> >
>> ><Do you get a blank screen?
>> >
>> ><Also, after a failure,
>> ><Look in the WEBEXTNDxxxxx ISA logfile for the specific
>> ><entry where the connection failed, copy that one entry
>> and
>> ><send it to me.
>> >
>> ><Tony Su
>> >
>> >The telnet fails and there are no WEBEXTNDxxxx files -
>> only WEBEXTDxxxx are
>> >present. There are no entries relating to the
connection
>> failure.
>> >
>> >Any idea what I can do next?
>> >
>> >Thanks,
>> >Claus
>> >
>> >
>> >.
>> >
>
>
>.
>

Relevant Pages

  • Re: SharePoint 3.0: problems with external access
    ... Create a new certificate for the WSS 3.0 website? ... "Go to 'Alternate Access Mappings' and in the 'Internet Zone' for your ... Port 443 won't work because it is already used by the Default Web Site. ... What you need to do is create a wildcard certificate and use it in ISA. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBSServer processes Port 80 blocked
    ... ISA rules will apply anyway. ... I've found that certain Windows apps don't work properly because they get ... What does it mean to send over port 80? ... He is in the BackOffice internet ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: SBS mit Isa-Server erricht Webseite von internen Clients nicht
    ... mach mal ein ipconfig /flushdns auf dem Client und auf dem Server. ... MVP ISA Server ... Browser auf dem Server kann man nun die Website anzeigen und im ... Regel: SBS Internet Acess Rule ...
    (microsoft.public.de.german.isaserver)
  • Re: Public Website on SBS 2003
    ... hosting and PROTECTING a website is specialist field and ... As leythos says you need to open HTTP port to the www. ... network settings are on servers internet connections. ...
    (microsoft.public.windows.server.sbs)
  • Re: SharePoint 3.0: problems with external access
    ... "Go to 'Alternate Access Mappings' and in the 'Internet Zone' for your ... Port 443 won't work because it is already used by the Default Web Site. ... What you need to do is create a wildcard certificate and use it in ISA. ... The steps to publish WSS 3.0 applications behind ISA 2004 are the same ...
    (microsoft.public.windows.server.sbs)
Loading