Well, I've got a lot of ground to cover this week and next. The first thing that I have been working on this week was trying to document a standard method for creating and installing the Virtual Network that I will be using for the upcoming lab. This entails documenting the setup of the two servers and the two workstations, and all the myriad settings involved.
It is kind of a pain having to work around Windows activation. At the start of the internship I was pretty excited, so I installed the servers and workstations without meticulously documenting every step. Now I am faced with having to kind of "roll back" everything I have done so that I can describe it. I am afraid to just delete the existing VMs and start over again for fear of setting off activation protections and being denied the ability to reinstall them at all. Note to self, be more restrained in the future.
I figured I would have to do some brushing up on Active Directory and such. It's been awhile since I took any server focused classes but I figured no big deal. Then I ran into my first major hurdle. When I was first testing the idea for this lab, I hadn't actually experimented with my proposed routing scheme. I just wanted to be sure that I could see all the traffic on the wire. Now I am rapidly discovering that 1.) I need a lot of brush up on routing tasks, or 2.) there is something going on due to this being a virtual set up that is causing problems.
If you recall week five's theoretical network diagram, I wanted to set up the main server (AD domain controller and database server) as a dual homed machine. The 'exterior' NIC would be either VirtualBox bridged or NAT and the 'interior' NIC would be VirtualBox internal networking. My problem is that I cannot get the server to route between the two interfaces.
I thought I would keep it simple at first, and just enabled IPEnableRouter in the registry and added a static default route to the external IP. This didn't work though. I next tried installing and configuring Routing and Remote Access and couldn't make that work either. I have manged to get the DNS and DHCP going but this damn routing is killing me. I haven't yet decided if it is a problem because of the 'virtualness' of the network or just that I am doing something wrong. I need to maybe try the VirtualBox host only interface and see if that works. Will have to get this figured out fast, because this coming week is the most important part of the project.
Next week the focus is on coming up with an actual plan of attack for the lab, and writing up a proposal for the idea. I need to get input from my adviser and other team members, adjust the proposal accordingly and then write it up. I rate this as a very important task so I will have to solve this routing dilemma ASAP.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment