[Mono-list] Re: Remoting: SocketException on Windows client when
server runs on Linux (certain machines)
helge at lenuweit.net
Sun May 29 04:17:45 EDT 2005
Oh really! That was it, a wrong URI that the client couldn't ever reach.
Thanks Rob for showing the way to find this out!
Robert Jordan schrieb:
>> There's basically a client/server situation with the client being a
>> Windows application calling a server via TcpChannel on Linux/mono.
>> The remoted singleton object has a method that returns a class that
>> acts like a CAO. This works very well with my SuSE 9.1 based test
>> environment. For some reason, it does not work with the server
>> running on a freshly installed SuSE Linux Enterprise Server 9
>> (additionally installed pkg-config and mono-complete RPMs there). My
>> Windows client gets the proxy instances of the remote objects, but
>> the first call to the actual worker object fails - with a
>> SocketException, telling me the destination host is unreachable!? Huh!
> The problem occur when client and server don't agree upon
> a common host name, for example when the server has a
> hostname w/out a valid DNS entry.
> Try to find out the URI by calling RemotingServices.GetObjectUri()
> on the returned object. Does it return something that your client
> is able to connect to? If not, your server is probably missconfigured.
> You may also try to apply some remoting config settings
> in the app.config of your server, especially "bindTo" and
> "machineName". See
> Mono-list maillist - Mono-list at lists.ximian.com
More information about the Mono-list