M
MCM Support
Not quite sure where to post this one. This is the current state of a
network I "inherited":
The clients are a mix of Win98 and Win2K, which I am responsible for
maintaining. They login to a Novell server(s), which I do not control, and
login to the local workstation. If it matters, the dns and dhcp servers, etc
are on the Novell side of things.
Behind a contivity box I have a Win2K domain, with a combination of terminal
services/file/database servers. The servers themselves can only see
machines that are also on "inside the box" on the closed network.
After authenticating to the contivity box (using credentials stored on a
smart card), users connect to terminal services via a web interface, at
which point they authenticate to the domain. Then they login to the database
app, but thats *another* story for another day.
The poor users are just overwelmed with a zillion passwords and I'm going
nuts trying to support this.
What I'd like to have is a server outside the closed network that users can
authenticate to on initial login. But then how do I get the servers behind
the box to recognize their credentials.
And did I mention the 2 standalone Win2k and WinNT servers (currently out on
the open network) they want merged into the closed network like yesterday?
At which point I inherit another 50-100 users, some of which already exist
on the domain, some don't.
Looking for any suggestions at this point. In short...
HELP!
network I "inherited":
The clients are a mix of Win98 and Win2K, which I am responsible for
maintaining. They login to a Novell server(s), which I do not control, and
login to the local workstation. If it matters, the dns and dhcp servers, etc
are on the Novell side of things.
Behind a contivity box I have a Win2K domain, with a combination of terminal
services/file/database servers. The servers themselves can only see
machines that are also on "inside the box" on the closed network.
After authenticating to the contivity box (using credentials stored on a
smart card), users connect to terminal services via a web interface, at
which point they authenticate to the domain. Then they login to the database
app, but thats *another* story for another day.
The poor users are just overwelmed with a zillion passwords and I'm going
nuts trying to support this.
What I'd like to have is a server outside the closed network that users can
authenticate to on initial login. But then how do I get the servers behind
the box to recognize their credentials.
And did I mention the 2 standalone Win2k and WinNT servers (currently out on
the open network) they want merged into the closed network like yesterday?
At which point I inherit another 50-100 users, some of which already exist
on the domain, some don't.
Looking for any suggestions at this point. In short...
HELP!