Slowresponse by machine name, fast w/Localhost?

TheMSsForum.com: The Microsoft Software Forum

I'm developing some basic asp.net stuff locally. The code works fine, no
errors. If I hit it this way:
http://localhost/mypage.aspx it runs great.

If I hit it this way:
http://machinename.domain.com/mypage.aspx it takes about 30 seconds before
it returns the page on the first session hit. After that, it runs great
during that session.

This wouldn't be a problem except that the development of this work is being
monitored by my boss. He's a bit impatient about the poor performance when
he tries to hit my work from his machine using the URL above.

Where should I start looking to resolve this issue? Is this a DNS/Network
problem?

Thanks for any help you can offer.
Bernie
Top

Re: Slowresponse by machine name, fast w/Localhost? by Kristofer

Kristofer
Thu Dec 08 12:35:47 CST 2005

Hello,

Yes, it may very well be a DNS or network issue. I can not see any reason
why IIS would delay a request from a remote machine, unless the code by
some reason do this (and in that case it would be a problem with the code
and not IIS). The reason why i say this is that IIS does not differentiate
between remote requests and local requests.


--
Regards,
Kristofer Gafvert
http://www.gafvert.info/iis/ - IIS Related Info


bernadou wrote:

>I'm developing some basic asp.net stuff locally. The code works fine, no
>errors. If I hit it this way:
>http://localhost/mypage.aspx it runs great.
>
>If I hit it this way:
>http://machinename.domain.com/mypage.aspx it takes about 30 seconds before
>it returns the page on the first session hit. After that, it runs great
>during that session.
>
>This wouldn't be a problem except that the development of this work is
>being
>monitored by my boss. He's a bit impatient about the poor performance when
>he tries to hit my work from his machine using the URL above.
>
>Where should I start looking to resolve this issue? Is this a DNS/Network
>problem?
>
>Thanks for any help you can offer.
>Bernie
Top

Re: Slowresponse by machine name, fast w/Localhost? by Ratatooie

Ratatooie
Fri Dec 09 10:33:15 CST 2005

To help differentiate;

add a line in the HOSTS file (%windows%/system32/drivers/etc/HOSTS) to
bypass the DNS lookup. If it still lags, it's not DNS or DNS lookup related
network. If it still lags on remote machine and not on local, then you have
it pegged as general network.

"Kristofer Gafvert" <kgafvert@NEWSilopia.com> wrote in message
news:xn0ear6nrhrjr9j00c@news.microsoft.com...
> Hello,
>
> Yes, it may very well be a DNS or network issue. I can not see any reason
> why IIS would delay a request from a remote machine, unless the code by
> some reason do this (and in that case it would be a problem with the code
> and not IIS). The reason why i say this is that IIS does not differentiate
> between remote requests and local requests.
>
>
> --
> Regards,
> Kristofer Gafvert
> http://www.gafvert.info/iis/ - IIS Related Info
>
>
> bernadou wrote:
>
>>I'm developing some basic asp.net stuff locally. The code works fine, no
>>errors. If I hit it this way:
>>http://localhost/mypage.aspx it runs great.
>>
>>If I hit it this way:
>>http://machinename.domain.com/mypage.aspx it takes about 30 seconds before
>>it returns the page on the first session hit. After that, it runs great
>>during that session.
>>
>>This wouldn't be a problem except that the development of this work is
>>being
>>monitored by my boss. He's a bit impatient about the poor performance
>>when
>>he tries to hit my work from his machine using the URL above.
>>
>>Where should I start looking to resolve this issue? Is this a DNS/Network
>>problem?
>>
>>Thanks for any help you can offer.
>>Bernie


Top

Re: Slowresponse by machine name, fast w/Localhost? by bernadou

bernadou
Fri Dec 09 10:42:02 CST 2005

Thanks to both of you for your responses. It turns out that there was an
extra software NIC (microsoft TV adapter or something... don't remember now)
that was sending out a weird 0.3.0.5 IP. No idea where it came from but once
we disabled it (which it fought us on doing...), the regular hardware NIC
took over and everything was fine.
Thanks,


"Ratatooie" wrote:

> To help differentiate;
>
> add a line in the HOSTS file (%windows%/system32/drivers/etc/HOSTS) to
> bypass the DNS lookup. If it still lags, it's not DNS or DNS lookup related
> network. If it still lags on remote machine and not on local, then you have
> it pegged as general network.
>
> "Kristofer Gafvert" <kgafvert@NEWSilopia.com> wrote in message
> news:xn0ear6nrhrjr9j00c@news.microsoft.com...
> > Hello,
> >
> > Yes, it may very well be a DNS or network issue. I can not see any reason
> > why IIS would delay a request from a remote machine, unless the code by
> > some reason do this (and in that case it would be a problem with the code
> > and not IIS). The reason why i say this is that IIS does not differentiate
> > between remote requests and local requests.
> >
> >
> > --
> > Regards,
> > Kristofer Gafvert
> > http://www.gafvert.info/iis/ - IIS Related Info
> >
> >
> > bernadou wrote:
> >
> >>I'm developing some basic asp.net stuff locally. The code works fine, no
> >>errors. If I hit it this way:
> >>http://localhost/mypage.aspx it runs great.
> >>
> >>If I hit it this way:
> >>http://machinename.domain.com/mypage.aspx it takes about 30 seconds before
> >>it returns the page on the first session hit. After that, it runs great
> >>during that session.
> >>
> >>This wouldn't be a problem except that the development of this work is
> >>being
> >>monitored by my boss. He's a bit impatient about the poor performance
> >>when
> >>he tries to hit my work from his machine using the URL above.
> >>
> >>Where should I start looking to resolve this issue? Is this a DNS/Network
> >>problem?
> >>
> >>Thanks for any help you can offer.
> >>Bernie
>
>
>
Top