Notifications
Clear all
Topic starter
We are running 12.0.7 and recently changed the IP scheme in our organization, however the CPS client will not allow users to login. We temporarily added back the old IP address to the NICs on the servers, as a second IP address, which then allowed users to login. We have rebuilt the website through server setup both with the new IP address only and with both and no matter what we do, the client only allows login to the application if the old IP address is configured as a second IP address for the NIC. Any suggestions?
Posted : September 5, 2017 7:57 am
can you ping the new IP address from the local machines?
it sounds like a DNS issue.
Posted : September 5, 2017 8:02 am
Topic starter
Yes, we can ping the new IP addresses from the locals, and DNS is pointing to the new IP addresses, we were using class c private addresses and went to class A. Funny thing is the A records for the old IP addresses aren't in DNS anymore, but the application still works fine as long as the old IP address is attached as a secondary on the NIC
Posted : September 5, 2017 8:05 am
Topic starter
Yes, we can ping the new IP addresses from the locals, and DNS is pointing to the new IP addresses, we were using class c private addresses and went to class A. Funny thing is the A records for the old IP addresses aren't in DNS anymore, but the application still works fine as long as the old IP address is attached as a secondary on the NIC.
Posted : September 5, 2017 8:07 am
Was Jboss completely uninstalled / installed with the new IP on the server? I would try that if it ends up not being DNS related.
Posted : September 5, 2017 8:08 am
Have you done this:
ipconfig/flushdns
ipconfig/registerdns
Posted : September 5, 2017 8:12 am
Have you done this:
ipconfig/flushdns
ipconfig/registerdns
Posted : September 5, 2017 8:12 am
Topic starter
Tried that through server setup>advanced setup options>install website; same experience, tried again using the same path but uninstall website and then went back and installed the website.
Posted : September 5, 2017 8:14 am
Topic starter
I will give that a shot when I gain access to the server again, however, this is occurring on the locally installed client on the app server as well as the fat clients distributed through the network. Thanks.
Posted : September 5, 2017 8:16 am
Hmm...after adding in the IP did you see it listening on port 9443? Does the page load and just authentication that is failing? Are you using application or AD security? Maybe go through advanced options and reset security to the domain (if that's the security model in use).
Posted : September 5, 2017 8:19 am
you will probably have to run it on the local machine as well, along with any machine, even the server, if it is not recognizing it.
Posted : September 5, 2017 8:21 am
Or maybe the client needs to be reinstalled...could be a few things I guess.
Posted : September 5, 2017 8:23 am
Topic starter
Hmm...after adding in the IP did you see it listening on port 9443? Does the page load and just authentication that is failing? Are you using application or AD security? Maybe go through advanced options and reset security to the domain (if that's the security model in use).
We are using http so 9003 is our port but it is listening. The web page loads, the login box comes up, then when you login it sits for a minute before erring out with red text in the login box that says contact sys admin, looks like its trying to display an error code but that gets cut off, so yes it seems to be authentication failing. We are using AD security. One of my next steps is to toggle to local security and applying and then resetting to AD security, saw that suggested in these forums, thanks for the insight.
Posted : September 5, 2017 8:25 am
Topic starter
Got it will do thanks for the suggestion.
Posted : September 5, 2017 8:26 am
Do your domain controllers have both old and new IP addresses currently by chance? I wonder if the AD authentication is trying to reach the domain controllers' old IP addresses, which would fail until you add the old IP address to the JBoss server (I think it's the JBoss server that handles authentication anyway).
A packet capture on the JBoss server while it only has the new IP address will show you the domain controller IP it is trying to reach.
Posted : September 5, 2017 9:49 am
Page 1 / 2
Next
