Re: Urgent : IE Web control problem

From: MWells (outbound__at_sygnal.com)
Date: 01/12/05 

Date: Thu, 13 Jan 2005 10:57:11 +1300

I'm assuming that no-ip offers essentially standard DNS services; your
hostname resolves to an IP, and your IIS server (optionally) checks the host
header to direct the request.

It sounds like you're seeing your website ok, but that not all of it works,
so we can probably assume that the DNS and host header configuration is all
satisfactory.

My money is still on the javascript library paths. I suspect you can see
them fine internally, and can't see them at all externally. Using both your
internal and external hostnames, try hitting the /aspnet_client and
/webctrl_client directories. You should get "Directory Listing Denied". If
from your external path you get a 404 error, that's your problem.

You should be able to resolve this by making copies of both directories into
your application directory.

"John F" <a@b.com> wrote in message
news:u8JZbQI#EHA.2196@TK2MSFTNGP14.phx.gbl...
> Hi,
>
> I'm using two different url's to access the same box. M, I'm using dynamic
> DNS to navigate to my site (which is my box at home). I'm using no-ip.org
> (check the site out, if you want). Like I said, when I test the site using
> Localhost everything works fine but when I come to the site using the
> no-ip.org web site, I then have the problem with the toolbar not working.
>
> Regards
> John.
>
> "MWells" <outbound__at_sygnal.com> wrote in message
> news:uJJHu7D%23EHA.3416@TK2MSFTNGP09.phx.gbl...
> > If the site works on your development machine, but not on the
> > test/production server (i.e. a different box), then the problem is most
> > likely related to the javascript library that supports webcontrols.
> >
> > Double-check to make certain that you have the both "webctrl_client"
> > directory and the "aspnet_client" directory available on your production
> > server.
> >
> > Also, I have encountered situations where deployments to a Windows 2003
> > server can meet with an odd complication. There appears to be a second
> > version of the "aspnet_client" javascript library, but -both- are
> > identified
> > as version 1_1_4322. I can't say why the distinction exists or under
what
> > circumstances it occurs; it may be related to a SP or tool install. The
> > behavior is similar to what you're describing... autopostback clicks
don't
> > fire... but the problem isn't limited to IE WebControls. Even regular
> > ASP.NET buttons will fail in this scenario. If you encounter this same
> > problem, try doing a backup of the "aspnet_client" dir on your server,
and
> > copy over the one from your development machine.
> >
> > If your failure scenario involves two different urls pointing to the
same
> > box, then I don't have an immediate explanation. Barring some form of
> > proxy
> > issue, you should be able to see the same directories through any Url
that
> > hits your website.
> >
> > Btw, your second Uri below has me a bit baffled; did you mean;
> > http://mysite/mypage.aspx
> > Or are you doing something particular with a .org filetype?
> >
> > /// M
> >
> >
> > "Microsoft Newsgroups" <a@b.com> wrote in message
> > news:uthoVWB#EHA.3260@TK2MSFTNGP14.phx.gbl...
> >> Hi all,
> >>
> >> I'm having an interesting problem with my IE Webcontrols. I'm using the
> >> toolbar and when I test it in my browser using
"http://localhost/mysite",
> > it
> >> works fine. Incidentally, I have "mysite" set up as a web application.
> >> Now
> >> when I test it going through "http://mysite/no-ip.org" then the toolbar
> >> doesn't work properly. It seems to merely render the images and any
> >> subsequent embedded Javascript but there are no events fired to the
> >> server
> >> upon clicking.
> >>
> >> What could this pssibly be and how do I rectify this? I still want to
> >> continue using IE Webcontrols.
> >>
> >> Please help as this is quite urgent.
> >>
> >> Regards
> >> John.
> >>
> >>
> >
> >
>
>