Hello.

BM3.8
NW6.5.5
Server rebooted several times.
health CHeck (TID 10060600) is clean.
eDir without partitioning, 3 servers, RW-Replica on this server, all Servers
running NW6.5.5


I had to change the default IP for that server. As this is much easier with
NW6.5.x I postponed that till after this upgrade: The 10.204.0.0/16 will be
removed from that LAN. But the IP Configuration in RM doesn't do what it should:


I used RM IP management to switch the default IP from 10.204.0.10/16 to
10.201.0.10/16, no errors, Cert's summary only OKs. (Both IPs were bound already
before the upgrade.)

RM *does* show, that the default IP is 10.201.0.10, for httpstk's "default IP"
(81,8008, 8009) in the details it also presents, that in RM's opinion these are
bound to 10.201.0.10.


But TCPCON shows, that they *ARE* still bound to 10.204.0.10. Also a run of
PKIDIAG (2.70) shows, that the default IP still is 10.204.0.10


What is going wrong here?

How to correct?

was wondering what would happen when I just remove the 10.204.0.10, so that the
*WRONG* default IP simply isn't bound any more. But I do not want to mess up the
situation, suspect, that this might be no good idea.



Thanks for any suggestions,



Rudi.

--
IT-Beratung Rudolf Thilo
Schweinfurter Str. 131
97464 Niederwerrn
0 97 21 / 6 46 48 40