2000 Server as a domain controller

[LeDeau]

I'm running a domain out of Omaha, and I want people to be able to connect their machines and logon from Chicago and Detroit. What ports do I need to have open, and is there anything else I should know before doing this? Thanks in advance...

 

[GlenJohnson]

How are you going to have them connect? VPN, VNC, terminal services or 3rd party software? We need a few more details. Thanks. Glen A. Johnson
Johnson Computer Consulting
MCP W2K
glen@johnsoncomputers.us



"There is only one good: knowledge; and only one evil: ignorance."
Socrates (470- 399 BC); Greek philosopher.

 

[LeDeau]

Right, that's what I'm trying to figure out myself, what's the best way for us. I want them to be able to log on and have pull their profile off of the DC in Omaha. And I want them to be able to have the DC also setup the permissions and policies for their machines while they are logged onto the domain. It it even possible to have them connect? Pretty much what I'm asking is, can they connect just as if they were in the same office building? (I understand that it would be much slower) Thanks...

 

[GlenJohnson]

So, you want userA to sit in Chicago, and log onto dc in Omaha? If this is what you want, then you'll have to figure out what security settings you need. TightVNC is a free download, but you have to really check security as it sends everything in plain text. I use this for one old NT server I have in another town. However, when I want to connect to a server on my network here from home, (Which would be the same as a user in Chicago), I use a VPN and authenticate on the dc. This gives us much more security, but it's a lot harder to set up. (Funny that you have users in Chicago, I'm from Rockford, which is about 50 miles north.) Glen A. Johnson
Johnson Computer Consulting
MCP W2K
glen@johnsoncomputers.us



"There is only one good: knowledge; and only one evil: ignorance."
Socrates (470- 399 BC); Greek philosopher.