Wade Kuhl
24th October 2007, 22:09
Hi,

I have an issue where a new notebook on my network cannot connect to our Baan server. This may be the oddest problem I've ever had.

PC:

- Dell Latitude D630
- Windows XP SP2 - All updates except ie7
- Baan Client Versions v7.9 & v8.2
- Member of W2K3 Active Directory Domain

Problem:

Everytime I try to connect ot the Baan server, with the baan client, I get a Error 1326. This happens no matter what user credentials I use.

Symptoms:

- Ping server by name & IP address - OK
- Log on to server from another PC with the same account - OK

- Change .BWC file to access server via IP address instead o name - Doesn't work

- Attempt to log on to the server doesn't show up in the Baan server event logs

- Reinstalled Baan client v8.2 - No effect

- Uninstalled client & installed client v7.9 - No effect

- Attempt to map a drive to a share on the Baan server generates an error for a normal user & for me, the Administrator, it connects but looks more like a file to the OS than a mapped drive. - this is not always the case

- Switched network connection - No effect

- Removed docking station from the notebook - No effect

- Swapped HD into spare Notebook of the same model - No effect

Any advice someone can offer I would really appreciate.

Thanks in advance,

Wade

Markus Schmitz
25th October 2007, 11:55
Funny, some of the things you tried ...

Anyway, can the same user connect to Baan from a different Desktop?
If it is the user, it might be the od local-log-on problem.

The biggest surpise is for me, that you do not have any event log entries on the server. Can you telnet from the laptop to port 512 on the server, ie. "telnet SERVER_IP 512"? If not you might have locally a firewall running, which is blocking outgoing traffic?

Are you using rexec (Port 512) or baanlogin (Prt 7150) to connect to the server?

Regards
Markus

ahmer91
25th October 2007, 12:23
check the permission on the drive where you are saving your BWC configuration file.

Wade Kuhl
25th October 2007, 16:26
:D

We're using the default, port 512 to connect to the server.

I tried telneting on port 512 as you suggested and a session opens but there is no echo so it's had to verify that things are working.

The user is currently working fine with another desktop so it's not a credentials issue. I've tried logging in a several different users including myself - Administrator/superuser and have the same result.

The only thing I can think of is that there is some sort of corruption in the Windows Authentication files on the notebook I'm working with. If so I'm not sure what can be done other than reinstall everything.

Thanks,

Wade

Wade Kuhl
25th October 2007, 16:41
I never thought that there might be an issue with the permissions to the .BWC file. It was a good thought, but doesn't appear to be the issue here.

Regards,

Wade

Wade Kuhl
29th October 2007, 15:43
I reinstalled Windows from scratch and everything is working OK. Thanks for your advice everyone.

Wade

:o