web service client fails to connect via active directory

[SimonSellick]

Hi,

I'm not sure whether this is the correct place to post this, but if not I'd be grateful for a pointer to a more appropriate forum.

We have a web service client app which I developed in Java, running under WinXP. The web service is on the other side of a firewall (on the Internet). All has been well until a recent move, since when the client fails to connect to the web service, timing out after about 30 seconds. I have successfully run a cut-down version of the client from a location outside the LAN (no firewall), so it seems to be the environment that has changed. The network bod thinks that possibly the client might be being asked to authenticate itself to Active Directory, in which case it probably does not know how to do that (I certainly haven't told it how).

I'm not expecting a solution from so little information, but I really don't know what I should provide that might be relevant. Can anyone offer any advice as to the sort of things that we should be looking at, please?

Any suggestions would be welcomed.

Thanks in advance,

Simon Sellick.

 

[MoreFeo]

I'd think about a proxy issue or firewall, rather than authentication.
Do you need to set up a proxy to access the internet?
Do you know the port this web service uses, and do you know if the firewall accepts this port?

 

[SimonSellick]

Thanks for the response.

We have checked that the firewall is open to the port and both (client host and web service) IP addresses, and we have tried adding an explicit proxy to the client code before it tries to make the connection to the web service. Neither of these has helped.

Authentication was suggested as a possibility by IT support. I am trying to get a trace of the network traffic involved to see whether it shows anything interesting, although I'm not really sure what to look for or whether it will be in plain text or encrypted.

Can you think of anything else that we should investigate?

Thanks again,

Simon.