From the perspective of the user's outlook profile finding the mailbox, yes, just creating a CNAME record of one.domain.com and pointing it to two.domain.com will resolve your issue for the outlook clients. However, you will need to ensure that if two.domain.com will be the new smtp server exchanging mail with other smtp hosts, then you will want to update the MX record(s) as well. Mail is delivered between mail systems using the MX record. An Outlook client uses a standard DNS host record to located a mail server.

When it comes to hardware and software requirements, it depends on what you are using this server for. For basic storage of files, you need to pay close attention to the amount of storage you require. Alot of CPU power is not really required, but extra RAM will help. Of course, when it comes to your storage, faster drives will provide a better experience. If you have other software that will be integrating with this server, check with those vendors to see if they will have any specific requirements for the OS, network, etc...

For 205.16.39.0 /28, the first usable range is 205.16.39.1 - 205.16.39.14. The network address is 205.16.39.0 and the broadcast address is 205.16.39.15.

Well, I would start at the router and work your way back until you find a group of computers that exhibit this issue. So, the next time this happens, plug a laptop directly into the LAN port of the router and see if you have internet access. If you dont, then the problem is the router. If you do, plug the switch back in to the router and start testing ports until you can determine the point on the network that is causing this issue.

There are tons of books and websites. Too many as a matter of fact. I would recommend that your purchase a good set of training books. Books provide you a cost effective method for an introduction. In addition, you will probably want to setup a host computer and install virtualization software so that you can practice hands on labs.

If you are interested in Microsoft networking, I would consider this training kit: [URL="http://www.amazon.com/gp/product/0735663270/ref=as_li_ss_il?ie=UTF8&tag=jomesblanitkn-20&linkCode=as2&camp=217145&creative=399373&creativeASIN=0735663270"]http://www.amazon.com/gp/product/0735663270/ref=as_li_ss_il?ie=UTF8&tag=jomesblanitkn-20&linkCode=as2&camp=217145&creative=399373&creativeASIN=0735663270[/URL]

Yes, TCP/IP v4 has not really changed in decades. You should be more than OK.

In your router config, just create another port forwarding rule that listens on port 20202 and maps that to server B. The only issue here is that your clients will have to absolutely send the traffic to your public IP destined on port 20202 or whatever other port you want. It just can be the same port that you are using to map to server A.

Alternatively, if you can get your ISP to give you another public IP, and your router allows for a configuration of two public IPs, then each IP can map directly back to one server each.

Not possible with DNS. What you would need to do is do the redirect on the web site itself. So, have the website listen on port 80, then do a redirect to port 20202. Redirects can be done at the website configuration, via a URL rewrite, meta tag "refresh" or via code such as with server side scriting (asp.net, php, etc...).

Make sure that the client DNS settings for your XP computer is pointing ONLY to the DC and not your router or ISP DNS servers. If your client queries any DNS server other than a DNS server that has a zone with AD information, it will not be able to locate your DC(s).

You can either change the subnet mask for that subnet (between router a & b), or add a new subnet then add the new hosts to the new subnet.

There really is no other option.

The subnet mask when applied to the IP address basically extracts the subnet portion of the IP address. This is done when you apply the AND operation against the IP address. What you do is convert the IP address into a binary number. Then you convert the subnet mask into a binary number. AND the numbers together, and the result is the subnet address.

Example:

IP: 1101 1000 . 0000 0011 . 1000 0000 . 0000 1100 (216.003.128.012)
Mask: 1111 1111 . 1111 1111 . 1111 1111 . 0000 0000 (255.255.255.000)
  1101 1000 . 0000 0011 . 1000 0000 . 0000 0000  (216.003.128.000)

Some routers provide run a web server to allow the administrator to use a web browser to interact with. This is where you may think that the router was programmed using Java. Now, it may be that the router's HTTP server is serving java pages. That is not uncommon. You would need to check with your router's documentation for more information about the HTTP server that it is running. However, as L7Sqr indicated, the core IOS that the router is running to "route" packets is not going to be written in Java.

that's great news. Glad the info was helpful.

If you have basic network connectivity between the two hosts via PING, then at least you know that you have the path in place. Now, to allow for file sharing, you'll need to make sure that if either of the clients have a host based firewall running, that you allow for the file sharing exemptions. In addition, you'll need to create the shared resource (file share, printer, etc..) on each machine. Finally, you will need an account to authenticate to the system with the shared resource. The easiest method is to create the same user ID on both systems with the same password.

Once that is in place, you should be able to access the shared resource via UNC path (\computerName\shareName)

There is no requirement to have more than one card for a proxy server. The same card can be used for traffic to come into and out of the proxy server. Obviously, a GB Ethernet card could handle much more traffic than a 10/100 card.

Open a command prompt on the wireless laptops and type IPCONFIG /ALL. compare the results to those computers on the LAN that have access to the network and internet. Are they on the same subnet? If not, you'll either need to configure the network equipment so that they are on the same subnet, or if they will remain on a different subnet, you'll need to configure the appropriate routing on your infrastructure.

Yes, lena1990 would need to have a router (gateway) interface for every subnet that is defined.

Some employers still do care about these certification, but not as much as they did back in the early 2000s. Certification has never been the same after the certification craze occurred where many people just cheated and passed exams without any experience. I still think certification adds value, especially if in the process, you really learn and acquire additional skills.

If your plan is just to have a piece of paper or add another line item in your resume, I wouldn't bother. During an interview, it will be evident whether or not you know what you are talking about.

Preparing for the CCNA should only take a few weeks. You can buy a CCNA study guide, books, and a simulator.

Good luck.

You can either break up your current /24 segment into smaller subnets, or just create 4 /24 subnets.

If your internal network is on a private IP space, and its a small network, you don't have to break up 1 /24 segment, you can assign each segment its own /24. Otherwise, if you are limited on existing subnets and IPs, break up the /24.

Your best bet is to look at the main application that you plan to run on the server(s) and see what the requirements are for good performance.

In any case, generally, on a server, the slowest component is the disk subsystem. So, I always try to get the most I can for my money by upgrading the disk controllers and hard drives. Next, I would ensure that I have enough memory running on the system. On an x64 capable system, running a 64 bit OS, you can easily expand on RAM and the system will take advantage of it. Finally, if needed, I would focus on the CPUs.

Again, you'll get the most on your return if you first take a look at the storage and see if it meets your requirements.

Two things to check... can you directly plug into the back of the router (wired) to ensure the problem is not with your system accessing the network via wireless?

In parallel, I would contact your ISP so that they can run tests on your wire. They usually can determine if the problem is before or after the router.

If you allow your SQL server to accept remote connections, then you can query the SQL database from anywhere on your network. By default, your SQL server will listen on port 1433.

It is hard to provide you with a definite answer without knowing the specifics about the "modem". Many of these ISPs provide you with DSL equipment that is now a modem/router device. In the early days of DSL, they provided you with a modem, and you had to buy a router. That's not the case these days, as the equipment they provide has both the modem and router built in.

Hard to say without more details, but you definately have an unecessary flow of DNS on that network. Rather than having your clients point to hte firewall for DNS, then foward them to server, then forward out, just configure the DHCP scope and set the DNS clients to point directly to the server running DNS. This will remove one level out of this DNS flow and improve the speed of name resolution.

So you have a DNS server that is hosting firstdomain.com and you associated this domain with ns.firstdomain.com. so on that dns server create another primary zone for seconddomain.com. when you register this domain with godaddy, associate this domain with ns.firstdomain.com as well.

Normally, registrars want for you to specificy at least two NS servers that will be hosting your domain. having more than one NS server will improve the availability and fault tolerance of your DNS infrastructure.