asked on

Deployed ASP.Net system will not connect to Web Service ..but will connect from Visual Studio!

Greetings,

I'm new to this so I apologize in advance!

I developed an ASP.NET in VS and it pulled the information it needed from the remote site. Once deployed to the "apps" server it gives the message below.

What can be the cause of my problem?

Many thanks,

Paul

A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 109.169.78.11:80
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 109.169.78.11:80

Source Error:

Line 128: AppSettingsHelper.FixYourStreetApiFolder(), _
Line 129: AppSettingsHelper.FixYourStreetApiVersion())
Line 130: Dim ListOfIncidents As List(Of FixYourStreetIncident) = Client.GetIncidentsGreaterThanId(LastFYSIncidentOnTasklist)

Source File: c:\inetpub\wwwroot\Liosta\Tasklist.aspx.vb Line: 130

ASKER CERTIFIED SOLUTION

Nasir Razzaq

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Tablecloth

ASKER

Hi Codecruiser,

Thanks for the quick reply.

Yes, there is a Firewall, but tests I did on the server, on instructions from the remote site people, show that we CAN connect over it.

All very mysterious, its possible to run the project in Visual Studio but not when deployed..

As ever it's no doubt something small that I've overlooked...

Tablecloth

ASKER

Would you have any further ideas?

Nasir Razzaq

Try telneting on that ip and port. Error message indicates connection issues.

Tablecloth

ASKER

Thank you Codecruiser, it was the Firewall all along!