I hate to bring this here, but I don't know where else to go. We are experiencing what we believe to be DNS issues in our network. Here is one example of how this problem manifests itself:
On a user XP Pro workstation, an intranet web-based app that requires AD authentication won't start after a reboot of the PC. If you change *ANY* DNS setting in the TCP/IP Properties, and close the Properties, the app works and the system connects back to the server. You can do nothing more than take out our DNS Svr IP and then type in the *same* IP. Whatever you do, the app works after the change is made and the TCP/IP Properties dialog box is closed. However, a reboot will cause the app not to work once again -- until something is changed in the TCP/IP Properties on the box. The link to the app uses an IP address, not the FQDN. We *cannot* change that setting.
Our Network:
Windows 2003 Server - DC
Windows 2003 Server - DNS
Workstations (using this app) are ALL Win XP Pro
If there's anything else you need to know, LMK. THANKS for your assistance!
On a user XP Pro workstation, an intranet web-based app that requires AD authentication won't start after a reboot of the PC. If you change *ANY* DNS setting in the TCP/IP Properties, and close the Properties, the app works and the system connects back to the server. You can do nothing more than take out our DNS Svr IP and then type in the *same* IP. Whatever you do, the app works after the change is made and the TCP/IP Properties dialog box is closed. However, a reboot will cause the app not to work once again -- until something is changed in the TCP/IP Properties on the box. The link to the app uses an IP address, not the FQDN. We *cannot* change that setting.
Our Network:
Windows 2003 Server - DC
Windows 2003 Server - DNS
Workstations (using this app) are ALL Win XP Pro
If there's anything else you need to know, LMK. THANKS for your assistance!