virtualbox.org

Hey all,

I have setup a few "labs" in my time on VB, but i am really having issues try to add other servers to a domain on my new fresh lab.

I have one server setup, activated, and updated it to domain controller with AD, DNS and DHCP roles, and I'm having issues when trying to add a second server into the domain.

On the second server, I have added the DNS server address to the network properties (the IP of the DC) but it still cannot see the domain I created (domain.local), and it IS on the same Network interface as the first server (with an IP of 192.168.231.1 which was auto created when i created the Network Adapter). This network interface is NOT setup as a DHCP server, as my DC is doing this, as that setup has worked better for me in the past.

**Quick Edit: The network card (on the second server that i want to add to the domain) is constantly giving me a 169.x.x.x address as well, and i cant understand why it would be doing this??**


I have done this (created labs) many times, so I can't see what could have gone wrong this time around.

Any advice, or suggestions. (if you need more info on anything, then please let me know!)

Read chapter 6 of the User Manual, then check the Networking Tutorial in Tutorials and Rules/FAQ.

RDP Live wrote:**Quick Edit: The network card (on the second server that i want to add to the domain) is constantly giving me a 169.x.x.x address as well, and i cant understand why it would be doing this??**

This means you need to get a crash course of Networking 1-0-1. It seems you have no idea what you're doing. Anyone that understands networking knows what that address means (Google for APIPA).

This means you need to get a crash course of Networking 1-0-1. It seems you have no idea what you're doing. Anyone that understands networking knows what that address means (Google for APIPA).

I know exactly what Private IP addressing is. I am fairly comfortable with networking as a whole too! Never mind...I'll just figure it out on my own. I have set up several labs in the same way i am doing now..and i was just getting this error this one time.

You know...you don't have to be so rude about it!! I was after help...i guess i wont find it here!!

Looks like I'm going back to vmWare Workstation then. As they say: You get what you pay for...and this program is free afterall, so i don't expect the help/support to be of any worth either. I was proven correct!

This is a volunteer forum, not Oracle support!

Since your networking problem had nothing to do with VirtualBox in the first place, I cannot understand why you would go back to VMWare. It is cumbersome compared to VirtualBox.

Different virtualization systems all do the same things, but they do them in different ways. You need to become familiar with these differences when you change from one to another, be it Microsoft, Oracle, VMWare, Citrix or whatever.

Well I have been seeing a lot more shall I say harsh remarks here of late. Still the OP deserves an answer.

While we can not help you with the actual network setup of the domain as it is outside the scope of this forum, you really should look at getting your test domain outside you local LAN. More than likely this is what is confusing your second server. I always set my test domains up on an Internal network. See This Link and read Chapter 6.5 Internal networking in your VirtualBox users guide. Since you have done this before you should have no problems understanding the information.

BillG wrote:This is a volunteer forum, not Oracle support!

Since your networking problem had nothing to do with VirtualBox in the first place, I cannot understand why you would go back to VMWare. It is cumbersome compared to VirtualBox.

I agree...vmWorkstation is very very resource intensive and the "easy-ness" and simplicity of Virtual Box is fantastic! I was just having one minor networking issue...and i blamed it on VB. Quick to judge i know...but i have done the same procedure in VB countless times...and I couldn't think why my servers were acting in this manner.

One thing I am going to do is rebuild the servers again..must have been a minor temp glitch and like i said..i was quick to jump!

Basically, ling story short...i have a deadline of some documentation to get done for the end of the week, and i need to run through an install of application on Server 2008...and this delay was just one of several delays i have already faced, so i threw my toys out the pram...Now, i have been in time-out and i will try again!!

Have no fear all...i am NOT switching back to vmWorkstation...i will make another go of it.

Thanks again for the advice and the comments...I will try again!!

Perryg wrote:See This Link and read Chapter 6.5 Internal networking in your VirtualBox users guide. Since you have done this before you should have no problems understanding the information.

Thank you very much! Will give this a read!

EDIT: OK..so after a little reading I relaised where i went wrong in this "lab" setup and 'apparently' in all other labs i have setup in the past. I have been doing it the LONG way around in the past so this time I changed the adapter to Internal Network and set the name to the same name for my 2 servers...BOOM! it worked!!

So So simple...I have been setting this up quite differently in the past (and it worked)..but this time...it just didn't cut the mustard!!

Oh well....problem solved...thanks again all...and I hope that next time I ask for help, i wont get such a bashing from a MOD (aka Bigfoot!)

Speak soon all!

Martyn.

I wasn't bashing. If I was, the post would have been completely different. My understanding was that you didn't know why you get a 169.254.x.y address range, hence I reference to google for APIPA, which that address is (it's not a private IP). If you would know about it, I figured you would know why you got it and would understand what you need to do to investigate. I gave you the tip to read the manual about the network options and the tutorial for that reason. Shame you had to be told a second time before you actually took a look.