Last week we demoted a windows 2000 server from a domain controller to a standard server on our domain. This server used to be the primary DNS server. Shortly after we had 3 PC's in the office that were unable to connect to Baan through the bw client. (Baan server curretly on HP 9000 HPUX /Oracle)

The exact error message pop up box is User name or password not correct


in the background messages box is.

: rexecd: Couldn't look uip address for your host
: rexec failed host 'xxxxxxx' port 512 username 'xxxx' command '/work/baan/bse
: Error : bw failed to connect to xxxxxxx!bshell

I have tried everything. Uninstalling the client, upgrading to the newest client. Clearing the bwclient registry entries. Exporting and importing bwclient registry entries from a working pc.

I actually got one pc fixed but I had to format c: and reload from scratch.


What makes me believe this isn't just PC related or OS releated is I can resolve the baan server name from DOS, and connect to baan from DOS, just not from the baan client.

Has anyone had this issue before? SSA has basically given up trying to help me at this point. They blame it on he PC / OS.

Instead of the hostname use the ipaddress of the Baan server and give it a shot. If that works you know where the problem is.

I received a message back from SSA on thursday last week so here are the steps I took to fix the problem.
"
SSA posted
run command

from command line

rexec hostname -l unixusername ls
enter password when prompted.

If you cannont get the output, the rexec setting is messed i.e the tcpip
installtion issue
"



This has been confirmed over 3 computers now to fix the problem. apparently TCP/IP somehow got corrupted on the PC's when we demoted what used to be the PDC, DNS, DHCP, and WINS server.

On the PC's

1.) Installed NetBIOS so that the primary NIC had a protocal to bind with.
(Rebooted)
2.) I uninstalled TCI/IP from the machine for the primary NIC. (Rebooted)
3.) I then uninstalled the NIC. (Rebooted)
4.) The NIC automatically was found and reinstalled on boot up.
5.) Next I reinstalled TCP/IP. (Rebooted)
6.) Went into Advanced Settings for the Local Area Connection and moved TCI/IP
above NetBIOS in the list of protocals.
7.) and Last Uninstalled NetBIOS from the primary NIC.

Note: Uninstalling TCP/IP from a windows 2000 pro workstation without first
installing another protocal for for the Ethernet card to bind with for some
reason made it near impossible to rebind the Ethernet card to TCP/IP once it
was reinstalled. Hence using NetBIOS to temporarly bind to the network card
seemed to fix the rebinding issue.

I took notes from similar posts on the web on how to reinstall TCP/IP and added a few steps of my own after trial and error to get it to work again.