Saturday, January 21, 2006

Windows 2003 Server Lab 1-2 Active Directory & DNS

After plugging into the network each page looks exactly like what is in the lab manual - SWEET. Interesting info at the DNS Registration Diagnostics. Interesting - it gives an error message on the first one that you get to. It says the primary DNS server tested was dns.cp.msft.net (207.46.138.10) but of course gives an error. Selected the second one (Install and configure DNS server on this computer...) and it appears to work as expected. Actually the most difficult thing to do was read the text on the screen (since I'm using VNC, it is even smaller!).

For lab purposes, we are using a dynamically assigned IP address, but the Domain Controller works best was static IP.

Windows Server 2003 Lab Configuration

Student computers (where XX is the unique number assigned to students)

Computer name: ServerXX
Windows domain name: Contosoxx
Internet domain name: Contosoxx.com
Fully qualified domain name (FQDN): Serverxx.Contosoxx.com
--------------------
For the Instructor
Computer name: HALSERVES
Windows domain name: Contoso
Internet domain name: contoso.com
FQDN: HALSERVES.contoso.com

IP Address: 10.1.1.xx
Subnet Mask: 255-255.0.0
Default Gateway: get from network admn.
Preferred DNS Server: IP address of DNS server
Alternative DNS Server: IP address of another DNS server

Windows 2003 Server NAT/Firewall Device

What I discovered in this process is that unless you are hooked into a network, you will not see the server role list. It skips that step and goes to the Active Directory. This means that I will certainly need to connect into a network in some way. According to the class notes, the best way for this to work is to isolate the classroom from the rest of the campus network. According to the Lab Setup Guide, the best way to do this is to use a Network Address Transaltion (ANT) or firewall device. This will prevent IP addressing and name resolution issues with the rest of the campus. I will check with Mike and Eric to see if this will cause problems with other systems. The best bet is to configure a NAT/Firewall device or to set up IP addresses as 10.2.2.1 as the IP range. and Subnet mask as 255.255.0.0

Windows Server 2003 and VNC

This starts my blog on the Windows Server 2003 class. To begin with, I installed using the 180 day valuation package on HAL, my older computer from many years ago. I call him HAL because he has a blue light.

Anyway, HAL had Windows XP Professional on it, so I started the computer and then put the CD in it and then restarted it. It went through the process quite normally, although I could have used the Quick NTFS, but chose the normal selection since it checks the drives, etc. Yikes it really did take some time (37 minutes) and I suspect it will be even longer on the student machines. HAL has 256 MB of ram (the minimum required) and the student boxes only have 128MB on at least 4 of them. I put in a request for a ram bump, but time will tell if that can happen or not.

I was installing MS2003 in the design room of XCaliber, and David's music was not agreeing with me, so Daniel helped me set up UltraVNC. Ultra VNC allows me to set HAL about anywhere and use my own keyboard and mouse in my office - SWEET... Changed the display settings so it works for me and my HAL is talking at 192.168.1.55 - again, SWEET. Think to remember, plugging the network cord in the bottom port game me a different IP address - go figure.

I'm thinking this would be a good thing to show the students too, but I doubt that Mike will give me more machines for play. I may need my students to come out to XCaliber to work with a network unless the school will let me close off HH20.

In Windows 2003 Server, you use Ctrl-Alt-Delete to begin. I almost made that mistake and then realized the with VNC, I would be restarting my machine if I used that command. You use CAD on Ultra VNC to send that command to the machine.

Thursday, January 05, 2006

My first podcast I attribute to a flood in my office...

On October 7, 2005, my office at SMWC was flooded. Three inches of water, rug floating, and smoke seeping out from under my desk where the surge protector was melting. Sounds like a bad thing, right? At the time, I thought so. However, several weeks later, with equipment replacement a possibility, I did some researching to find the best equipment to help me podcast my lectures - more like PROFCAST. I'm a novice, so I went for a podcasting kit and watched Carl Franklin's hands as he put together the kit. I have NOT been disappointed. It was easy.

It took me two minutes to record my first podcast. I kept it (just so I have the first one). I feel I'm a better podcaster now since I've worked on slowing down, adding inflection, working on the "ummms" and other distracting sounds. So here is my first podcast!

This is my FIRST podcast.