Lery

I finally got this working and thought I would share how I did it. I had a little help from a buddy of mine in setting up the routing tables. The diagram below will hopefully explain it better than the description. 1) ISP (Cable) coming into E3000 Linksys Router. Linksys router configured with 192.168.1 2) Server A Windows Server 2008 connected to E3000 Linksys Router. Server has two integrated and two additional network cards on it. RRAS installed. Server A's four network cards are configured with 172.22.0., 192.168.2., 192.168.3., 192.168.1. 3) Server B connected to Server A via crossover cable. 4) Linksys WRT54GS connected to Server A. In Router mode. This is for an additional 4 ports. I am not sure the image will display properly, and you may have to right click and choose view image and then enlarge it. Sorry about that. I also have the static routes configured on the E3000 router. I have since removed the 192.168.3 subnet. It was not completely working, which I did not think it would and was using it for testing something.

Currently he is using Windows Server 2003 Enterprise installed. I'm under suspicion that these copies might not be very legit. One of the Windows XP machines failed the genuine validation test. I'm in the US, so does anyone have links or anything to get going? I'm a small time shop, so I really just want to get a high level list of information so I can tell this customer, or others, what to do regarding media and license keys. FYI, no OEM information is listed on any sticker on the machine.

Thank you for taking the time to read this post. I am starting up my own small computer repair business part time. My main focus is on the home user, but I do have two customers that are small business owners. My problem is with them :-) This one small business, at some point, worked with another computer business to set things up. He installed Windows XP boxes, Windows Server 2003 box with AD, DHCP, and Exchange Server 2003. A pretty straight forward simple setup. Now the problem is my customer no longer wishes to work with the person who originally set him up. Unfortunately, he has none of the install media or license information. Therefore, if anything goes badly on any of these machines, my customer is screwed. For now, I made images and stored them, so we could at least restore the OS on the machine. My question is this. What I would like to be able to do is to resell Microsoft licenses along with the media. The media, I feel is an important part for customers to have and own. Most small shops become a system builder licensed partners with Microsoft, which is great until the customer no longer does business with you. I know some will say that is the customer's problem, but that is not the approach I want to take here. I've searched around Microsoft's site and in order to understand their licensing program and partner program, I feel like I need to have another college degree. Is it really that complicated?

@digip, I'll definitely have to take some time and digest what you are saying. I'm still learning most of this stuff. I found a network guy at my work that is going to help me hook this up. We are going with the additional NIC card and one crossover cable route. So basically I'm going to have Server A with a total of three NIC cards. The integrated one, and the two additional ones. The crossover cable we are going to use from Server A to Server B. Then I'm not sure how he is going to set things up from there. That is the part I'll learn, and of course post here. @h3%5kr3w, my secondary router (the one not connected to the Internet and daisy chained off the main router) is a WRT54GS, so I can put dd-rt on that. I was just watching the episode on dd-rt and that is some cool mojo. At some point next week I should have this setup and will post up a diagram of what we did. I would love to see what you all have to say, and possibly how else we could of accomplished this.

Unfortunatley it is not working. How would you setup the static routes, on the router in that screenshot for 192.168.1/24 and 192.168.2/24 addressing? Anyway I try it, it doesn't work. Today I just went ahead and ordered up a crossover cable and two NIC cards. Going to play with it that way to see what I can get going.

That screenshot is really the only place to configure dynamic routing on the router, so I'm not sure what other screenshots would be helpful. The router shown in the screenshot is a Linksys WRT54GS v1.0 (very old router). Updated firmware of course. Based on the screenshot, RIP is enabled on that router, yes? The static routing in the screenshot has been removed. Please let me know anything you need and I will be happy to provide it. I am going to try to remove the router completely, and setup one of the virtual machines as a router using Routing and Remote Access, which has the RIP feature there. We'll see what happens.

Yeah I was playing with that part last night and could not get it working. Here is the Linksys router WRT54GS configured with 192.168.2.1 address, which has the clients that would use the 192.168.2 subnet connected to it. This router is then connected to the Linksys E3000 router which is set for the 192.168.1. subnet. Notice the Dynamic Routing: RIP. So I should be good. This WRT54GS is also configured as a Router. Now the static routing part, is what keeps driving me crazy. I actually took a virtual machine running on the 192.168.2 subnet, added a virtual network card to it. That card uses the 192.168.1 subnet, and the original virtual card is using 192.168.2. This machine can now access the internet and domain features. Then I went ahead and installed Routing and Remote Access and tried setting up a static route in that. Used my windows xp test machine and for awhile I got on the internet and everything was working. Then I tried backing out what I did so I could pinpoint it, and now its back to not working again. Driving me nuts. I will go and check out GN3 now, thanks for that.

Will do and thank. Yesterday I was playing around and found that creating the secondary subnet was simple enough. Getting the clients to access the internet, and resources on the other subnet, not so much. Since I do not have additional NIC cards yet, what I did was this: Internet | Linksys E3000 Router (192.168.1.1) |____Server A Connected to this, running 7 Virtual Machines. All on the 192.168.1 subnet. | Linksys WRT54GS connected from Linksys E3000. Gave this router an IP address of 192.168.2.2. |___ Server B connected from here. Virtual machine Win XP running off this client, and changed the IP address of the machine, to something like 192.168.2.15. That worked for putting the machine on the subnet. I could ping the resources on the 192.168.2 subnet just fine. Of course internet access was a no go. I was reading about setting up a direct route on the routers, which I tried to do. It would not accept what I was giving it, or would just plainly not work. I would love to not have to do this with multiple NIC cards. I think doing this with multiple NIC cards, is called Multi-homing, which when I researched that topic, all comments mentioned NOT to do it. So perhaps there is another way. What about using ESXi or VLAN's? This is really a pain in the butt for something that would seem like a simple task. I'm just trying to test out what my software application does when it has two subnets to work on. As an example of what I'm trying to do, I found this post http://www.velocityreviews.com/forums/t403...one-subnet.html He got it working, but unfortunately I do not understand the replies, to be able to try it. Too bad they don't give better details there :-)

Thanks again for the reply. I think I am going to have to just bite the bullet, get the network cards, and go from there. I'm still a little lost on how to approach this. Remember I already have the two servers running ESXi 4.1 (just upgraded from 4.0) today. I'll toss the two NIC cards in server A and see what I get from there.

Thank you, this does help. But the Nic part threw me off a little. Server A and Server B have their integrated NIC cards already in there. They currently are both on the 192.168.1 subnet. I was told, but I'm not sure it is fact, that I need to purchase an additional two NIC cards and put them both into one of the servers. In this case I think, I'm not sure, Server B. It is important that everything on Server A continues to use the 192.168.1 subnet, and server B would use the secondary subnet of say 192.168.2. I was also told its necessary that the server that is going to have both NIC cards (for a total of three), on it, that I have to not use ESXi 4.0 and instead load Windows Server 2003. I'm sure Linux would work as well, but I'm not familiar with Linux as much as I am with Microsoft OS's.

I was hoping to see a show or if no show, then perhaps someone has this well documented somewhere? Here is what I have setup and what I'm trying to do. Cable Internet Connection into Linksys E3000 Router. Secondary Linksys router (WRT54GS) for the additional RJ-45 connections. (It is what I had laying around). Server A is running VMWare ESXi 4.0 Runs a VM with my DNS, AD, DHCP server. Plus a few other VM's. Server B is running VMWare ESXi 4.0 Runs a few Windows Server VM's. I am currently running on the 192.168.1 subnet. I would like to add a secondary subnet into my network. I want do do this mainly for some specific software testing. As I understand it, I have to buy at least two additional NIC cards. Ok can do that. Then, from that point, I am lost at how to start. What server do I put the two NIC cards into? Server B I guess? The ultimate goal is everything on Server B is using the new subnet. We will say 10.23.5 (Yes I just made that up). Everything on server A will continue using 192.168.1. I would need the VM's running on the new subnet (10.23.5), to also be able to access the internet. Extra points if the VM's can also access the VM's running on the 192.168.1. subnet. So, there you go. That should fill up a 30 minute show. -Lery