Dns Server Setup Window Xp
Wed, 20 Jan 2010 16:04:35 +0000
They feel safe enough with the other versions of Windows that you are now thinking of combating Server 2003. The idea may be a little intimidating, but it's not as bad as you think. This is a simple tutorial on the different modules in Windows Server 2003. Depending on how you want the server to determine the hardware requirements of the machine. Precisely because it is a "server" you must not spend more than $ 5,000 on the computer. This is a very largeMisunderstanding. My recommendations for minimum requirements are as follows:
- Motherboard with Onboard Video / Sound / Lan
- 1 GB of memory
- P4 3.0 GHz or Athlon 64 3200 +
- 160 GB SATA Hard Drive
- DVD-RW
- An external backup device (eg USB hard drive or tape drive)
Server 2003 loads the same way XP. Set the BIOS to boot from CD / DVD drive, pop in the disk and follow the instructions. Once it is fully installed and you will be chargedthe "Manage Your Server" made the screen. On this screen you can enable and configure the following options:
- File Server
- Enabled by default. Basically, folders can be shared on the server
- SharePoint Services
- Creates a network in which users can exchange information
- Print Server
- Act in a printer that is installed directly on the server as a network printer
- Application Server
- Turn off servers in a Web server, as well as FTP --Host
- Mail Server - Kinda useless if you installed Exchange
- Terminal Server
- The user can login directly on the server to run applications
- Remote access / VPN server
- Connect to the server remotely via VPN
- Domain Controller (Active Directory)
- Server control policy for the entire network domain
- DNS server
- Inspections name to IP address resolution
- DHCP Server
- Legal IP addresses to DHCP clients
- Streaming Media Server
- Streaming video content over the Web
- WINS Server
- Earlier name to IP Address Resolution Method.
What will always determine your needs, which enable these options will be configured. In this article we will briefly on Terminal Server, Remote Access, Domain Controller w / Active Directory and DNS server to contact. I'm going into detail about allthem in future articles.
Terminal Server: As mentioned above Terminal Server allows users to log on the server to run applications installed on the server. Besides the possibility of Terminal Server, you will also find a Terminal Server license. Here are the licenses that are installed, the user terminal server. Depending on the number of licenses you have, how many users log determined. Terminal Server and Terminal License server can both on a single machine. Toenable the license server to Control Panel -> Add / Remove Programs -> Add / Remove Windows Components -> select "Terminal Server Licensing" and install it.
To login to the server from a workstation you can use Remote Desktop, which is integrated directly into Windows XP and Vista, too. To the remote desktop search, click on Start -> All Programs -> Accessories -> Communications -> Remote Desktop. If the remote desktop appears, enter the server name or IP address to connect.
RemoteAccess / VPN: Virtual Private Networking gives you the opportunity to share remote connection to your server, and resources. The server assigns you an IP address from either the DHCP pool, or you can manually select a range of IP addresses of the servers hand out to the remote clients. Once the connection is the next step to connect to shared resources on the server. To do this, click Start -> Run -> and enter the server name orserver IP address (the server is replacedName or IP address), if everything is configured correctly, your server's shares will be displayed.
Domain Controller: Set your server as a domain controller is, you can control the network policy settings on your server. If all workstations are on the server's domain, by group and / or domain policy, you can restrict user movement. Control, where they are allowed to go and what they are able to change. With the domain controlleris the Active Directory. In Active Directory, you can add network / server users, view / configure domain controllers and domain Workstations. Allows you to assign user rights and if they login to the server via Terminal Services.
DNS Server: How DNS resolves IP addresses to more easily remember the name. Suppose your server's IP address 192.168.1.2 and his name is PCServer. DNS allows you to searchremind PCServer rather than to be 192.168.1.2. Of all the modules, this is the fact that most of the organization is on the right confusing.
This was a very basic introduction to some of the modules in Windows Server 2003. In future articles, I continue to go into detail about each one.
Thanks To : laserhair-removal-cost childsupport-lawyer /buydomainname best sunglasses zune movies
Like OpenDNS, Google today launched their own public DNS service that they say will make your web-surfing experience "faster, safer and more reliable."
If you want to access a site (say example.com) from your browser, your computer needs the IP address of the web server that is hosting that domain. The computer will then query a public DNS server to find the IP address of the site example.com.
This DNS server is generally maintained by your ISP but now you can instruct your computer (or wireless router) to use Google’s DNS server instead of your ISP’s DNS server. Google says their Public DNS Servers are hosted in data centers worldwide, and they use anycast routing to send users to the geographically closest data center.
If you are keen on making the switch to Google DNS, here’re the steps involved for Windows XP, Vista and Windows 7.
Video: Setup Google DNS on Windows XP
Select Internet Protocol Version 4 (TCP/IPv4), followed by Properties and them replace the IP addresses of your Preferred DNS server and Alternate DNS server with the IP addresses of the Google DNS servers which are 8.8.8.8 and 8.8.4.4 - the order doesn’t matter.
Screencast: Use Google DNS Servers on Windows 7 / Vista
In the above videos, I have changed settings for an Ethernet (LAN) connection but the steps are similar for Wireless networks as well.
In case you would like to setup Google DNS at the router level, open your router dashboard (e.g., http://192.168.1.1) and put the Google DNS server addresses (8.8.8.8 and 8.8.4.4) as your DNS server settings and apply.
How to Test Google DNS Servers
Open your command prompt and clear your DNS cache using the command ipconfig /flushdns. Then do a nslookup for any web address and you should see 1e100.net with 8.8.8.8 as the IP address for the DNS resolver.
C:\>ipconfig /flushdns Windows IP Configuration Successfully flushed the DNS Resolver Cache. C:\>nslookup www.microsoft.com Server: any-in-0808.1e100.net Address: 8.8.8.8 Non-authoritative answer: Name: lb1.www.ms.akadns.net Addresses: 64.4.31.252 207.46.19.190 207.46.19.254 Aliases: www.microsoft.com toggle.www.ms.akadns.net g.www.ms.akadns.net C:\>Find this article at: http://www.labnol.org/internet/setup-google-dns-servers/11439/
Tags: Archives, google dns, opendns, Internet