Hi,

Following is a scenario we currently are experiencing since converting to VPN. Any help, best guesses or sympathy would be appreciated. ;)

Baan Version: BaanIV c3 (tools) BaanIV c3/c4 (App)
Both our company and our Parent company have Baan installed on separate servers, separate installations, in different geographical locations. Till a few weeks ago we had a Frame Relay setup which allowed us to log onto each others servers and Baan applications, e.g. Log on to server 2 from site 1, start Baan and run a program (or visa versa). We can no longer do this using Baan GUI. The option dialogue box starts up, as if Baan is going to open, but then simply hangs for approx 5 mins, get a Windows Socket Error and exits automatically. This problem however does not surface when logging in with ASCI user (ba6.1)

Any ideas? What could be causing this?

Many thanks in advance,
Robert Poulter
rob_poulter@yahoo.com

My sympathy you can have anyway :-)

Does the VPN and all components in between allow for port 512 (rexec) ?
How are the BaaN server network settings, does it use DNS to resolve client ip addresses ?
Any activity / logging in log.bshell etc ?

regards,
Robert

Hi Rob,

Thanks for the reply (and sympathy). Though I'm a techy my skills are related to dev. I'd like to answer your questions, but I'm not sure how to gather the info for you... :confused:

Does the VPN and all components in between allow for port 512 (rexec) ?
How can I tell? Do you know? If not I will contact our maintenance co for this
How are the BaaN server network settings, does it use DNS to resolve client ip addresses ?
Will find out
Any activity / logging in log.bshell etc ?
Checked, there are none

BTW the error we get is "Windows Socket Error 10053". I found a posting on Baanboard related to error 10053. Seems like a connectivity problem (as you have stated Rob ;) )
Just need to find a fix !!!

Thanks

Hi Robert

You need to add a firewall in your network, if already have then try to find a suspected switch which may cause network congestion.