remote server is unreachable or the request has timed out
I've installed the Client and server applications to two different Windows 2000 machines and get the same error on both when I start the client "The remote server is unreachable or the request has timed out."
I have SQL Server 2000 and sa has a blank password. The SQL Server instance can be referenced using "local" and I believe that I've followed the instructions on the server page. My TaskVision.exe.config looks like:
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<appSettings>
<!-- User application and configured property settings go here.-->
<!-- Example: <add key="settingName" value="settingValue"/> -->
<add key="AppUpdater1.UpdateUrl" value="http://localhost/taskvisionupdates/updateversion.xml"/>
<add key="TaskVision.AuthWS.AuthService" value="http://localhost/taskvisionws/authservice.asmx"/>
<add key="TaskVision.DataWS.DataService" value="http://localhost/taskvisionws/dataservice.asmx"/>
</appSettings>
</configuration>
I can pull up the XML files using the URL's above and verified that the database was created whne the server installed. Any ideas?
Guy Bloomfield
Guy-
Did you ever get anywhere with this? I have just put my webservice, now filled with the taskvision security model, out to my production server and am having this problem. I have been fiddling with it for 3 hours. Egads!!
I don't know if its from my client to my web service or from the web service to the sql server.
I have experimented with my sql connection string based on some other posts.
The strangest thing is that it is intermittent. Once in a while, I get past the log in but stuck elsewhere. But usually it is in the login. However the VERY first routine works - passing the user login and pw to the sql server. It's after that that I'm hosed...
Thanks for any clues
julie
I'd be very interested to hear anyone else's experience in this as well...
Here's my experience:
http://www.windowsforms.net/Forums/ShowPost.aspx?tabIndex=1&tabId=41&PostID=878
Could someone from Microsoft gives us a hand at diagnosing this issue? :-)
Mixed solution and no help from Microsoft. I installed it on my laptop and my desktop. Both have local installations of SQL Server. I followed the instructions on the server install web page, on both machines. At first it worked on neither.
On the laptop though, I walked away and left the login page up as I went to lunch. When I got back to my desk it told me that an update was available for this program I chose yes (or something) and after that it worked.
I still can't get it going on the desktop though. I even copied the config files over from the laptop. SA has a blank password on both machines and they're both members of the same domain. I log into both machines using the same domain account.
Not sure if that helps.
Guy
Here is what we found was my problem after some 30 hours of trying everything else.
It was the proxy settings in i.e. on my client machine!!
I figured that out by turning them off in i.e. (settings/connection/lan settings/proxy)
Of course, that's not a good solution.
The real solution can be had in one of two ways.
First is in the machine.config for the client machine. This is not favorable to me becuase you can't always control that in deployments.
The default setting in machine.config (on the client machine) , usesystemdefault, is set to true by default. This causes .net to lean on i.e. settings for it's proxy settings. All of .net - even WinForms apps.
The second is in the appconfig.
So by adding a few little lines of code in my app.config :
<system.net>
<defaultProxy>
<proxy usesystemdefault="false" />
</defaultProxy>
</system.net>
The problem went away.
There were a lot of other things that I did on the way to this solution. So in case this isn't the answer to your problem, you can see some of the other ideas in the blog that I wrote about this at http://dotnetweblogs.com/JLerman/posts/4283.aspx.
Post your results back to here. I am thinking about building a list of things to do to solve this problem.
julie
