Hi,

While some users try to login , they get error "Couldn't look up address for your host". But they can login to server via telnet.

I couldn't find any errors in the log files.

Any ideas?

Thanks

Did you verify that their client settings are correct? Make sure there's not a typo in the hostname? Also, can they connect if they use the IP instead of the hostname?

Vince

We don't use hostname for Baan connection, we use IP address ( in bw configuration)
Everything is correct.

For real help, you should update your profile (UNIX or Windows and so on).

So here a first guess: Baan requires a reverse lookup; so check that e.g. nslookup host gives ip, and nslookup ip gives host.

Günther

Sorry, application server is Unix.

we had the same issue: it has to do with windows DNS & the aging interval of the different zones on a WAN network.
In our case the aging interval was set to 24 hours ('scavange stale records'). So when a user logged in on a zone different from the one where the baan server was located it took 15 mins (our sync interval) before his dns record was added to the dns zone where the baan server is.
Since (HP) unix only looks at the first dns server it finds it thinks that the pc is not available since it is not yet in that dns zone and therefore gives the error. After 15mins the error would resolve itself since then all dns zones have the same info.
We fixed it by changing the scavanging parameter.

Later I also found solution 6443 on baan support site which says you can disable the reverse naming lookup for rexecd. This might be easier to change depending on your specific situation.