every webservice call taking 5 seconds

[James]

Hi,

I have built a windows app that makes calls to a webservice. Both webservice
and windows apps are built with .net 2.0. The problem is... when I run the
client Windows app on the dev machine, calls to the production webservice
are very fast (milliseconds). When I run the exact same Windows app on a
different machine... same log in, calling a webservice on the same
production server.... EVERY call takes 5 seconds (not just the first call).

I cannot understand why this would happen, or how to debug? It happens on
any client machine except the dev computer.

Any ideas?

Thanks in advance!!
James

"James" <j DOT w AT zoom DOT co DOT ukwrote in message
news:OE**************@TK2MSFTNGP04.phx.gbl...

Hi,

I have built a windows app that makes calls to a webservice. Both
webservice and windows apps are built with .net 2.0. The problem is...
when I run the client Windows app on the dev machine, calls to the
production webservice are very fast (milliseconds). When I run the exact
same Windows app on a different machine... same log in, calling a
webservice on the same production server.... EVERY call takes 5 seconds
(not just the first call).

I cannot understand why this would happen, or how to debug? It happens on
any client machine except the dev computer.

Any ideas?

I would look at the settings for network proxies and make sure they're
correct on the client machines. Same with DNS server settings. Maybe it
takes five seconds just to connect to the server?

--
--------------------------------------------------------------------------------
John Saunders | MVP - Windows Server System - Connected System Developer

[James]

<[e-mail] in message
news:eC*************@TK2MSFTNGP06.phx.gbl...

>

"James" <j DOT w AT zoom DOT co DOT ukwrote in message
news:OE**************@TK2MSFTNGP04.phx.gbl...

>Hi,

I have built a windows app that makes calls to a webservice. Both
webservice and windows apps are built with .net 2.0. The problem is...
when I run the client Windows app on the dev machine, calls to the
production webservice are very fast (milliseconds). When I run the exact
same Windows app on a different machine... same log in, calling a
webservice on the same production server.... EVERY call takes 5 seconds
(not just the first call).

I cannot understand why this would happen, or how to debug? It happens on
any client machine except the dev computer.

Any ideas?

I would look at the settings for network proxies and make sure they're
correct on the client machines. Same with DNS server settings. Maybe it
takes five seconds just to connect to the server?

--
--------------------------------------------------------------------------------
John Saunders | MVP - Windows Server System - Connected System Developer

Thanks for the suggestion John, unfortunately I checked the settings and
they are all the same :(

FYI - opening a website on the same server as the webservice is fast from
the client machine

Any other suggestions welcome!

James

[James]

<[e-mail] in message
news:eC*************@TK2MSFTNGP06.phx.gbl...

>

"James" <j DOT w AT zoom DOT co DOT ukwrote in message
news:OE**************@TK2MSFTNGP04.phx.gbl...

>Hi,

I have built a windows app that makes calls to a webservice. Both
webservice and windows apps are built with .net 2.0. The problem is...
when I run the client Windows app on the dev machine, calls to the
production webservice are very fast (milliseconds). When I run the exact
same Windows app on a different machine... same log in, calling a
webservice on the same production server.... EVERY call takes 5 seconds
(not just the first call).

I cannot understand why this would happen, or how to debug? It happens on
any client machine except the dev computer.

Any ideas?

I would look at the settings for network proxies and make sure they're
correct on the client machines. Same with DNS server settings. Maybe it
takes five seconds just to connect to the server?

--
--------------------------------------------------------------------------------
John Saunders | MVP - Windows Server System - Connected System Developer

I fixed it!! Turns out that in the webservice where we log activity, there
was a DNS lookup call. That call ran v fast for the dev machine, but takes a
long time for clients (and eventually fails)... I removed the lookup now the
webservice is VERY fast.

James