Error joining a domain after iis lockdown

  • Thread starter Thread starter peter
  • Start date Start date
P

peter

Hi,

I've got a situation where I have windows 2000 Advanced
Server hosting Citrix's Nfuse Classic 1.7 which uses iis.
The server has been having a few problems were the iis
service has a habit of dying frequently.

Most of the things I had looked at pointed towards a
authenication issue. I thought that it might have been an
issue with domains computer account. So I took it out of
the domain, which on hind sight wasn't the smartest of
things to do.

When I tried to add it back into the domain, I get a error
when trying to join the domain.

Later on I found out that the iis lockdown tool had been
executed on the machine. I know that this will uninstall
and remove unnecessary services - this could be the thing
that causing the problem.

Has anybody got any ideas? Has anybody come across this
before? I need to get this back into the domain, as
quickly as possible, any help anyone can provide would be great

Cheers
 
peter said:
Hi,

I've got a situation where I have windows 2000 Advanced
Server hosting Citrix's Nfuse Classic 1.7 which uses iis.
The server has been having a few problems were the iis
service has a habit of dying frequently.

Most of the things I had looked at pointed towards a
authenication issue. I thought that it might have been an
issue with domains computer account. So I took it out of
the domain, which on hind sight wasn't the smartest of
things to do.

When I tried to add it back into the domain, I get a error
when trying to join the domain.

Later on I found out that the iis lockdown tool had been
executed on the machine. I know that this will uninstall
and remove unnecessary services - this could be the thing
that causing the problem.

Has anybody got any ideas? Has anybody come across this
before? I need to get this back into the domain, as
quickly as possible, any help anyone can provide would be great

Cheers
Click to expand...

Are you using the Citrix Secure Gateway on the same server as well? If you
are, you're probably dealing with a port 443 conflict in IIS. The fix is to
add a new static ip to your existing NIC or adding another NIC altogether.
Then configure the CSG to use the new ip.
 
Back
Top