We are having a problem with the Logon group in our ECC 6.0 production system. We have three servers. Two of them are clustered. I’ll call these two CI1 and CI2. They both normally have an SAP instance running on them. We have a separate Enqueue/Message Server. The third ECC 6.0 server just has a dialog instance on it. I’ll call this server DI. These are all on Windows Server 2008R2 servers. We normally have all three of these servers in a logon group called “default”. Last week, I removed CI2 from the default logon group. When I added it back into the logon group, we started getting an error that said “partner ‘169.xxx.xxx.xxx’ not reached. WSAEWOULDBLOCK: Resource temporarily unavailable” when users tried to log in. I removed CI2 from the logon group and the error stopped. The 169.xxx.xxx.xxx IP address is not a good address, I can’t ping it and it isn’t defined in our DNS. One of our system administrators said it is a bogus IP address that Microsoft assigns to NIC cards. In the SMMS (Message Server Monitor) transaction, when I click on Goto > Parameters > Display, I see the 169.xxx.xxx.xxx address listed for “server addr”. Also, when I click in Goto > Logon Data > Display, I see the 169.xxx.xxx.xxx as the Host Address for all Logon Types. The real IP address for this server is 10.xxx.xxx.5. Also, in SMMS, when I click Goto > Expert Functions > Host Name Buffer, I see the 169.xxx.xxx.xxx address listed at the top next to the HostName of the server with the domain name. Also, in the SMGW (Gateway Monitor) transaction, when I click on Goto > Remote Gateways, I see the 169.xxx.xxx.xxx address listed beside CI2. And another thing, in SMGW, when I click on Goto > Expert Functions > Network Addresses, I see the 169.xxx.xxx.xxx address listed at the top by the Host Name (with domain) and the Source is “HOSTNAME”.
My questions are why is my system trying to use this 169.xxx.xxx.xxx address, where is it coming from, and what do I have to do to make it start using the correct IP address?