Search results for query: *

Warning, There is an MS bug when upgrading an NT40 PDC to Win2k that you will not find out until after you have the problem. Check out this article. Trust me, it is worth looking into ahead of time. http://support.microsoft.com/support/kb/articles/Q257/6/23.ASP

Ok, There are 2 pieces to this config. One, I am assuming you are using private addressing on the inside interface and want all nodes internal to be able to access the internet. Here is how to do it. External Interface config should have "IP NAT Outside" in its config. Internal...

Assuming that you have a 2600 series routers of better, if you have 16mb flash and Cisco IOS IP IPSEC, you can do Private LAN to Private LaN VPN Tunnels over the Internet.

Do a show running and look at the interface configs. Look for a line that says "access-group 199 (in-out). If you do not see this, the ACL is not applied. If this is the case, do you have a firewall or another device that would do filtering. Does the router have the IP/FW IOS on it?

Exchange 2K must have Active Directory. Exchange 5.5 does not. You must have AD and DNS configured and functioning correcty for Exchange 2K.

You can NOT add a Win2K Server into an NT4.0 Domain as a DC or in NT4.0 Terms BDC. IT can ONLY be a member server. This is achieved NOT via Active directory , but through Computer properties, Network Identification. If you try Active Directory, you must have an AD up and configured with DNS.