I have a windows-based application that connects to an Oracle database.
When I launch the application, it connects to oracle just fine, and brings up my login-box. Per the application settings we have configured, it uses an Active Directory login method rather than using an application-specific one. So you supply the login window with your AD credentials, and there is a drop-down menu from which you can select the domain. The window looks very similar to the Windows XP login screen.
The problem we're finding is that in a specific part of our building (PCs on the second floor connected to two particular networking closets) the drop-down menu that normally is filled with all the available domains is completely blank.
The application usually takes a few seconds to connect to oracle and then another few seconds to retrieve the domain list and display the AD logon. Right now it takes about 40 seconds before the AD logon comes up, and then it's blank.
If I use a PC on the 3rd floor, or remote connect to a machine in another building, I can access the domain logon easily.
This same thing happened a few weeks ago and self-corrected after about 3 hours.
The application works just fine if you by-pass the AD logon and use a different connection method. I am in there and it works just great. It's not an oracle problem that I'm aware of. As far as I know oracle does absolutely no communication with the AD, that's done client-side and then the client reports back whether the authentication attempt was successful and the server allows you to log in.
The order of events looks something like this when everything is working right:
Open app on client PC
App connects to Oracle database
Oracle database recognizes client and communicates that the client should use an AD logon window to connect
Client connects to AD to retrieve domain info
AD logon window is displayed
Enter AD credentials
AD credentials accepted by DC
Application communicates to Oracle database that authentication was successful for user X
Application logs in to the user account linked to that AD account.
I've tried everything I can think of on the PC side. Release/renew IPs, flushdns, registerdns and even winsockfix.
XP can connect to the domain just fine. Nobody has trouble logging into Windows, but all of a sudden the application will no longer find that domain list, and you can't just type the domain name in, because it's not an editable field.
Can anyone think of a reason why I wouldn't be able to retrieve a domain list, or why a 3rd party application wouldn't be able to use AD authentication?
It seems to be limited to a specific part of the network, but our network team tells me there's nothing wrong. I'm stumped and I have to get this fixed by tomorrow AM