Re: Changed ISP, now webserver doesn´t work behind ISA!
From: Tony Su (TonySu_at_discussions.microsoft.com)
Date: 03/08/05
- Next message: Thomas L. Goodson: "Re: VPN"
- Previous message: Eric: "Continous Problems With SBS 2K3 Backup"
- In reply to: Jeff Teel: "Re: Changed ISP, now webserver doesn´t work behind ISA!"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 7 Mar 2005 19:13:02 -0800
Hello Jeff,
That's generally been my experience also, but we can't forget large private
networks like AOL. When you have a large private network like that, their DNS
may update more slowly and replication to the furthest reaches might take
longer.
Hence, the general "2 weeks" admonition although 3 days should be plenty for
people who aren't connected to large private networks.
Tony
"Jeff Teel" wrote:
> I would have to say if it is not resolving in a week at the most then
> something is wrong. In my experience with moving web sites to different
> servers/IP addresses it has only taken two days.......three days tops. That
> was also the case when moving one web site from a server on the west coast
> to one in New Jersey. The name was resolving in three days. I am located in
> the middle so the name servers had to have updated in a big area fairly
> quickly.
>
> "Tony Su" <TonySu@discussions.microsoft.com> wrote in message
> news:FF9A43BA-B115-4BAD-880D-33B100A97A5B@microsoft.com...
> > Htello Tony,
> >
> > Your old information may still be cached in public DNS servers for awhile
> > yet... sometime up to a couple weeks, typically.
> >
> > You can test whether you're configured properly as follows...
> > From outside on the Internet, point to a DNS which you know should resolve
> > properly (I manage my own public DNS, so this is very easy for me to do...
> > I
> > can simply point to my machine).
> > Or, depending on how you're exposing your website(s), connect by IP
> > address
> > instead of by FQDN.
> >
> > Either way, you're attempting to get the "straight scoop" from your
> > machine
> > bypassing any possible DNS issues.
> >
> > That won't solve Internet name resolution for everyone, but at least you
> > can
> > know if you're configured properly and should just wait.
> >
> > HTH,
> > Tony Su
> >
> >
> >
> >
> > "Tony" wrote:
> >
> >> Hi,
> >>
> >> We have a SBS 2003 premium with ISA 2000. 2 NICS
> >>
> >> Yesterday we changed ISP, and thus reconfigured the external NIC.
> >> Before changing we hade the external NIC going to a router and from
> >> that to a modem (ADSL). The router had external NICS IP in DMZ.
> >>
> >> When we now changed ISP we took away the router and connected the
> >> external NIC straight to the modem.
> >>
> >> We ran the connect to internet wizard and changed the appropriate
> >> settings for smtp etc. We did not change the firewall at all.The
> >> wizard ran through just fine.OWA / OMA and RPC over HTTP is also
> >> working, however we also have a website located on the SBS server.
> >> And that can not be reached now :(
> >>
> >> I should mention that we have our DNS records on a server located
> >> elsewhere, thus when we now changed ISP / IP adress we had to update
> >> the DNS records accordingly on that DNS server.
> >>
> >> I can´t figure out why the website is not working, when I ping it from
> >> an external source it answers on the correct IP.
> >>
> >> When I look in ISA I have a destination set pointing to this website.
> >> And also a web publishing rule which uses that destination set.
> >> The incoming web request is listening correctly on the external NIC.
> >> And in IIS that site is listening on the internal NIC. And TCP port
> >> 80.
> >>
> >> Does anyone have a clue what can be the problem?
> >> I bet I´m overlooking some littly tiny thing but right now it´s beyond
> >> me :(
> >>
> >>
> >> thx in advance / Tony
> >>
> >>
>
>
>
- Next message: Thomas L. Goodson: "Re: VPN"
- Previous message: Eric: "Continous Problems With SBS 2K3 Backup"
- In reply to: Jeff Teel: "Re: Changed ISP, now webserver doesn´t work behind ISA!"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
