I have discovered an odd problem in a workgroup of servers recently. This is on an NT4 network which is up to date on security patches. I noticed it on my IIS web server, and proxy server. I have tried for the last several days to try and find a resource online to explain/fix what's been happening. The best I have found were a handful of unanswered posts on the public forums about somewhat similar occurrences to other administrators.
Basically my problem is this:
I login under my personal administrative account, bring up IIS, and view the sites with out a problem, all is well.
If I login with the computers administrator account, or even my partners personal administrative account, IIS displays the websites and ftp sites as:
FTP Site #1 Stopped
FTP Site #2 Stopped
Website #1 Stopped
Website #2 Stopped
So its not displaying the name of the actual ftp/website, and its displaying it as stopped. However if you try to access these websites from the internet they are functioning properly. But like I said, login under my personal administrative account and all the sites are displayed correctly with their names, and running.
I have been unable to find anything solid as to why this is occurring or how to rectify it. Might just be a glitch in NT4 IIS4, who knows... Any suggestions?
Basically my problem is this:
I login under my personal administrative account, bring up IIS, and view the sites with out a problem, all is well.
If I login with the computers administrator account, or even my partners personal administrative account, IIS displays the websites and ftp sites as:
FTP Site #1 Stopped
FTP Site #2 Stopped
Website #1 Stopped
Website #2 Stopped
So its not displaying the name of the actual ftp/website, and its displaying it as stopped. However if you try to access these websites from the internet they are functioning properly. But like I said, login under my personal administrative account and all the sites are displayed correctly with their names, and running.
I have been unable to find anything solid as to why this is occurring or how to rectify it. Might just be a glitch in NT4 IIS4, who knows... Any suggestions?