Hi,
A couple of years ago we setup a small network with a stand-alone Win 2000 server, Services in use are: PDS, DHCP & Active directory, mostly file sharing is the key areas of use here.
All of the user work stations are Windows 200 (All professional I think). And file sharing has been working well.
However I failed to get to grips with configuring the Active directory, I must have bypassed a couple important steps in getting the Active Directory to work correctly: hence there are NO devices listed in the A-Directory as viewed on ether the server or if a workstation attempts to look at the device network directory in Network neighbourhood.
Recently the users have been set-up to use various online (Internet based services) where thy have to log into various internet web based servers. Unfortunately the users URL request frequently come back with an "Cannot find server or DNS Error" message, but I have proven that taking the "www" out of many of the URL browser address entry’s seems to provide a crude fix to the problem. This is obviously to do with my failure to configure the DNS server side of the 2K server correctly.
The internet is accessed by a Telco configured DSL Cisco router/Gateway with a static internal IP address, this independently works fine if a PC uses the ISP's DNS servers, but of course the Win2k Workstations need to look at the Servers DNS service to log on to the domain correctly.
Would someone please offer me a brief list of things to check & set-up on the server please?
Many thanks,
Jim. UK.
A couple of years ago we setup a small network with a stand-alone Win 2000 server, Services in use are: PDS, DHCP & Active directory, mostly file sharing is the key areas of use here.
All of the user work stations are Windows 200 (All professional I think). And file sharing has been working well.
However I failed to get to grips with configuring the Active directory, I must have bypassed a couple important steps in getting the Active Directory to work correctly: hence there are NO devices listed in the A-Directory as viewed on ether the server or if a workstation attempts to look at the device network directory in Network neighbourhood.
Recently the users have been set-up to use various online (Internet based services) where thy have to log into various internet web based servers. Unfortunately the users URL request frequently come back with an "Cannot find server or DNS Error" message, but I have proven that taking the "www" out of many of the URL browser address entry’s seems to provide a crude fix to the problem. This is obviously to do with my failure to configure the DNS server side of the 2K server correctly.
The internet is accessed by a Telco configured DSL Cisco router/Gateway with a static internal IP address, this independently works fine if a PC uses the ISP's DNS servers, but of course the Win2k Workstations need to look at the Servers DNS service to log on to the domain correctly.
Would someone please offer me a brief list of things to check & set-up on the server please?
Many thanks,
Jim. UK.