Web Service Consumer Deployment Problem

[tooniron]

Hi,
I don't know if this is the best forum to post this to, but I hope
somebody can point me in the right direction.
I have a VB.NET application which references a Web Service (added
through the standard Add Web Reference dialog). The Web Reference has
been set to be Dynamic in the properties window. The only call I make
in the code to the Web Reference is in a button click event and is
(the names have been changed to protect the innocent):

Dim test As New WebReference1.MyBasicService()
test.Url = "http://1.2.3.4:8080/axis/services/ConsoleLogin?wsdl"
MsgBox(test.getUserType(txtUserName.Text))

When I run this on my machine I get a message box telling me what
type of user txtUserName.text is, as I'd expect.
However, when I install the app on a second PC, using a standard
..NET setup I get the following error :

System.Net.WebException : The operation has timed-out

Is there anything I need to install on the second PC in order to
get this kind of SOAP RPC call to work ?

Cheers,
Rato

 

[Jan Tielens]

Can you browse from the second pc to your web service? Normally you'll only
need the .NET Framework on your machine to use web services... strange.

This second pc, is it in the same network, domain, ... has it the same OS?

--
Greetz

Jan Tielens
________________________________
Read my weblog: http://weblogs.asp.net/jan

 

[tooniron]

Thanks for the swift response. I can browse to the web service
without problem, and I'm also consuming an asynchronous web service
running on the same server using XMLHTTP with no problems.
The second PC is on the same network and is on the same domain. My
development PC is running windows 2000 professional, whereas the
second PC is running windows 2000 server. Would this make any
difference ?

Cheers,
Rato

 

[Jan Tielens]

W2k3 server should work too... can you browse from that computer to your web
service test page?

--
Greetz

Jan Tielens
________________________________
Read my weblog: http://weblogs.asp.net/jan

 

[tooniron]

Ooops, my bad. It appears the login I was using didn't have the
required privileges.

Cheers,
Rato