Problem resolving hostname

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Problem resolving hostname

NorbertHartl
I have a problem using the gemtools on my notebook. If I do

GsSocket getHostAddressByName: 'seaside.gemstone.com'

in a workspace I get nil response. Doing the same from a topaz session (same user) I get the address resolved.

Any ideas?

Norbert
Reply | Threaded
Open this post in threaded view
|

Re: Problem resolving hostname

Thelliez
Nobert,

I just tried on my dev VM and it worked...


Thierry
Reply | Threaded
Open this post in threaded view
|

Re: Problem resolving hostname

Dale Henrichs
In reply to this post by NorbertHartl
On 05/16/2011 02:18 PM, Norbert Hartl wrote:
> I have a problem using the gemtools on my notebook. If I do
>
> GsSocket getHostAddressByName: 'seaside.gemstone.com'
>
> in a workspace I get nil response. Doing the same from a topaz session (same user) I get the address resolved.
>
> Any ideas?
>
> Norbert

Norbert,

Are you running gemtools on the same host that you are running topaz?

A nil response usually means that the call failed and for GsSocket you
can find out about the error for the system call by evaluating the
following expression:

   GsSocket lastErrorString

Dale
Reply | Threaded
Open this post in threaded view
|

Re: Problem resolving hostname

NorbertHartl

Am 19.05.2011 um 01:49 schrieb Dale Henrichs:

> On 05/16/2011 02:18 PM, Norbert Hartl wrote:
>> I have a problem using the gemtools on my notebook. If I do
>>
>> GsSocket getHostAddressByName: 'seaside.gemstone.com'
>>
>> in a workspace I get nil response. Doing the same from a topaz session (same user) I get the address resolved.
>>
>> Any ideas?
>>
>> Norbert
>
> Norbert,
>
> Are you running gemtools on the same host that you are running topaz?
>
Yes, of course.

> A nil response usually means that the call failed and for GsSocket you can find out about the error for the system call by evaluating the following expression:
>
>  GsSocket lastErrorString
>
I didn't have time to test it again until now. And now it works :( ... well ... :) but ...

Norbert