garends
28th April 2008, 18:27
Hi

I have the following problem

On some machines can not connect to Baan, all
IP are in the etc/hosts, but some are not connected,
which gives the error is 512, this port is well in the config

When we change the ip on the other machine, its connected, the customer is the B40c73 for Baan IVC2. I dont know if a problem of networks or Unix server.

if a machine is turned off for one week at
turn it on and does not connect.
By changing the ip achieves connect again

that will be what happens?

thanks

mig28mx
29th April 2008, 17:55
Hello.
It seems to me that is a network problem. Perhaps you are using DHCP to assign ip address to your machines. If this, check if there is a not valid range of ip address. Another thing you must check is the firewall policies. Baan uses port 512 rexec to connect via bshell. Be sure that your firewall is allowing this port.

Hope this helps.

garends
29th April 2008, 18:50
hello

thanks, yes I am using DHCP to assign IP, but all range are valid.

The port 512 is allowing in the firewall policies. Several machines are connected using
this port

mig28mx
29th April 2008, 18:58
Ok,
Let´s start from the obvious. Can you ping to the unix server, form a machine that can not connect?

garends
30th April 2008, 17:23
Hello

Thanks, yes I can ping at unix server, but not connect or login in Baan,

mig28mx
30th April 2008, 18:03
can you ping from the unix server to a specific IP address that can´t connect?

Someday I have faced this issue, and the solution was put the ip address that can´t connect in the file hosts of the unix server, but as I see on your 1st message you have already done.

How is your BW client side configuration? are you refering to the baan server as an alias or an absolute IP address?

Try to add the alias to the hosts file on the client side.

Hope this helps.