D
David Reed
Hi Phillip,
Could you give me some guidance on how you did that?
I know the DNS settings are "right" on the local client, but it seems like
this update (which I think was the .NET Framework 1.1 update (though I know
other computers on the network have that installed) changed a security
setting or something. I've since uninstalled that update, but no change was
evident.
I'm truly confused, what might have happened to suddenly prevent the
computer from connecting to the domain, when it was working fine before the
SUS update was done.
David
Could you give me some guidance on how you did that?
I know the DNS settings are "right" on the local client, but it seems like
this update (which I think was the .NET Framework 1.1 update (though I know
other computers on the network have that installed) changed a security
setting or something. I've since uninstalled that update, but no change was
evident.
I'm truly confused, what might have happened to suddenly prevent the
computer from connecting to the domain, when it was working fine before the
SUS update was done.
David
Phillip Windell said:That last time it happened to me it was just a simple DNS setting. I had to
run only one DNS setting on the client and it had to be the AD/DNS. Once
the machine is "joined" there is a little bit more flexability, but it is
really picky before you get it joined. I also used a WINS Server that the
DC/DNS and the client both pointed to.
--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
David Reed said:Phillip,
Okay.
I'm still dead in the water here.
I don't understand it, because I've got complete network connectivity. I
could even NET SEND a message from another computer on the network, and it
worked fine. It just won't let me join the domain.
ARGH!
HELP!
David