Like I have stated in two other threads (which no one has answered please do!) I have installed Windows Server 2003 on a virtual PC and I am unable to access the internet. I think my problem is that I have installed this Virtual PC as a domain controller with Active Directory, DNS sever and DHCP server. Since I have installed this virtual machine as a DHCP server but my router is also enabled as a DHCP server do I have to disable the DHCP on my router! I think I do but can someone add their input!


Rick

Hi,
Yes, it sounds like you have answered it yourself! You cannot have two sources trying to assign dynamic IP addresses.
I think that most would advise that you install the server with the aforementioned settings and then installing a VirtualPC client on it with DHCP, DNS, etc. only in one place(the server) and firewall installed.
Having two instances of the server would work though I will not speculate on the licensing attributes.
Peace,
Clarke

I did not install a Virtual client onto the Server. I put the Server on a Virtual Hard Drive on my Vista machine. But yeah I figuredI couldn't have two DHCP servers running.

When I disable the DHCP server on my router what connection type should I put the router on: PPOE, LT2P, Static, Telstra, etc...

Also my DHCP scope is 192.168.0.10-192.168.0.254 but my default gateway of my router is 192.168.1.1 should I change the scope to 192.168.1.10-192.168.1.254?

Quote:

---

Originally Posted by ITstudent2006

I did not install a Virtual client onto the Server. I put the Server on a Virtual Hard Drive on my Vista machine. But yeah I figuredI couldn't have two DHCP servers running.

When I disable the DHCP server on my router what connection type should I put the router on: PPOE, LT2P, Static, Telstra, etc.....

Also my DHCP scope is 192.168.0.10-192.168.0.254 but my default gateway of my router is 192.168.1.1 should I change the scope to 192.168.1.10-192.168.1.254?

---

You can have multilple DHCP servers on the same network but they must the must each be configured for a different Scope.

What is your Subnet Mask? If you are using a Class C mask, then you must have routing between the two networks (192.168.1.0/24 and 192.168.0.0/24).

Hi,
I must "bow" to to that! You can actually have two DHCP servers. One must be "local" and filter for its addresses, and one can have the Internet connection, and its addresses.
It is a very good security "trick" that does not always work. It is a configuration headache! It is also a nightmare to update if you have multiple machine on the internal network.
I do stand by what I said.
Do not put the server as the VirtualPC, rather make a client that. It is easy to delete the client and start from "scratch."
Peace,
Clarke

I cannot "not" have the server be the Virtual PC. This is the way I have it set up, as of right now I do not have an extra desktop to put WIndows Server on. I am not managing any PC's/clients I did this just to get some extra experience with Active Directory. I do however want my internet to work.

I have a class C address 192.168.1.1 (Default Gateway)!
The DHCP Server defaulted my scope to 192.168.0.0 not 192.168.1.0 could this be why my internet doesn't work.

My subnet mask is 255.255.255.0

Before I used Virtual PC 2007 to install Windows Server 2003, I onlt had 3 laptops connected to a Linksys Wrt150-N. The default gatway for that router was 192.168.1.1 not 0.1

Now when I installed Serv03 on my VPC it also installed the server as the domain controller, DNS Server, and DHCP server.

I tried to connect to the internet and I couldn't. I went in to my router and seen that DHCP was enabled on my rotuer and so I changed that from DHCP to static because I was unsure of what to set it as. After that I turned my VPC on (thus starting WinServ03) I clicked on to the configure DHCP to see if there was something missing and that is were I seen that my scope was set as 192.168.0.10-192.168.0.254. Should I set this to 192.168.1.10-192.168.1.254.

Let me know!



P.S. Obviously I don't have much experience with server OS's I just want my internet to work and I want to play with AD and play around with permissiona and policies etc...


Thanks In Advance!


Rick

Hi,
Given the circunstance, I would say that the router should look for an outbound DHCP and have a static IP for connection to it. Then the VPC server should have the same address specified.
Barring this, turn DHCP off on both if your ISP will allow this and see what happens.
Peace,
Clarke

Hi,
Just another thought! I have heard that the NIC address could be null instead of the actual address embedded in the firmware. What is the message you get?
The network adapter with address "00:00:00:00:00:00" of virtual machine "...." failed to initialize because the address is a null address.

To fix this problem you should use REGEDIT to:

Examine the key value at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Class\{4D36E972-E325-11CE-BFC1-08002bE10318}\<nnnn>\DriverDesc to locate the desired host adapter where <nnnn> is a four digit number.
Look at the GUID value for the NetCfgInstanceId key value.
Add the DWORD key at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\VPCNetS2\Parameters\Adapters\<guid>\Flags and set the value to 0 where <guid> is the GUID found in step 2.
Restart the computer.
Peace,
Clarke

I am unable to access the internet. The message is unable to load page, and it gives 3-4 reasons of possibilities.

What if disable the role of DHCP on the server and have my router act as the DHCP as it had?

I think the problem is the default gateway for my router was 192.168.1.1 but the server put the scope at 192.168.0.0

I am unsure...

Also chuckhole, when you asked me what my subnet mask was did you mean according ot my router or the server. Cause like I had stated before the server says it's default gateway is 192.168.0.1 which would make my subnet mask 255.255.0.0/16 but the router's default gateway is 192.168.1.1 which would make it 255.255.255.0/24 wouldn't it?

Rick

Hi,
I think the subnet on the router would then be 255.255.254.1, if I remember right, may need to look them up, however. The subnet defines the number of bits allowable in the other addresses addressable, "clear as mud," on the network.
Try setting those addresses one digit apart.
Peace,
Clarke

Unless I've missed it, what IP is your virtual server picking up?

As a side, I'd dump M$'s attempt at virtualisation and go with The Pros in this field, VMware!
Their server product (GSX) is a freebie and rocks !
Runs fine on my laptop and desktop and makes for a great test bed, esy to use as well.

The IP address I am getting when I type ipconfig /all is 192.168.0.1

Well that's normally a gateway address, probably why you can't connect.

I am unsure why I cannot connect.

What would happen if I assign myself an IP that within the scope the DHCP defines. The scop the DHCP defines is 192.168.0.10-192.168.0.254. That means there are 244 IPs that DHCP server can dish right? What if I give the server machine a static IP of 192.168.0.9. Outside the scope, where-as it won't dish that number out to another PC while I'm using in.

Like I siad I am new to server OS's. Bare with me and again I thank you all in advance!

Rick

Don't think of it as different from a desktop OS as the nuts and bolts are generally the same.

Now it depends on which DHCP you are referring to.

How do I determine what my scope needs to be. 192.168.0.1 (default gateway)
Or 192.168.1.1 (default gateway)

I try to statically assign myself an IP by going into my LAN settings but whatever I change it to does not show up in the command prompts ipconfig command. All that shows is that my IP is 192.168.0.1 and that my subnet mask is 255.255.255.0 and I have no default gateway.

I delted the default scope and added one of my own 192.168.1.5-192.168.1.254 (which can be used to dish out 250 IP's. Now does my server have to have an IP within that scope or can I go outside the scope for it i.e.. 192.168.1.2.

By doing this I hope it would set my default gateway at 192.168.1.1. but no luck. When I look under leases it says my machine has leased an IP 192.168.0.12 which is valid for 8 hrs. (that is my designated lease time)

Where can I find the IP for my router, I believe this is the issue. When I setup my scope I need to designate a router that the clients will use, I keep entering 192.168.1.1 which is the default gateway of the router not the router's IP right?

Would it be inside the router interface?

Hi,
Try turning DHCP on the router. I say this to allow it on connected machines. Try going +1 on the server and defining your gateway to the Internet as the server. Just re-read my sub-netting material. It seems that this is the way through and theway to do it.
Peace,
Clarke

Hi IT Student. I'm getting a bit confused with all these posts as to what's going on. So here's what I'm thinking you've got set up.

Your router has it's DHCP server turned on, handing out 192.168.1.X/24 addresses. The router's IP is 192.168.1.1.

You have your Vista machine with a virtual Windows 2003 Server on it, which is also a DHCP server. It's scope is 192.168.0.10-192.168.0.100, and the server's IP is 192.168.0.1.

If that's correct, my question to you: Do you want to require the PCs that pick up a DHCP address from the server to route their internet access through the server? Most businesses don't run this way, but it's useful sometimes if you're going to study Routing and Remote Access in Windows Server 2K3. I'd advise against it, until you get the DHCP and DNS server running.

To get internet to work with your DHCP server on Win2k3, you need to have the Router (currently 192.168.1.1/24) and the Server (192.168.0.1/24) on the same subnet. I would probably change the server's IP to 192.168.1.2. Then, in your DHCP scope, you should have some range of 192.168.1.X address. The recommended Microsoft way to do this is to have the scope include 192.168.1.1-192.168.1.254, and then create an exclusion for 192.168.1.1-192.168.1.2.

Once you have the DHCP scope set up, you need to configure the options. If you're using the win2k3 server as a DNS server also, you can configure the DHCP option for DNS server to the server's new IP, which I would have set to 192.168.1.2.

I can't remember the name of the option, but it should be either Gateway or Router, which you need to set as another DHCP option. You would set this to the IP of the router. It tells the computers that pick up a DHCP address where to route packets, if they're not destined to the same network. The server should ALSO have this set as a default gateway, since it's going to be looking up DNS queries.

As for the DNS server, you don't need to configure it with forwarders if you don't want to. As long as it has a list of servers in the root server box (can't remember the name of the tab), the server will be able to get the DNS entries from there. If you want to use a forwarder, either use your ISPs DNS servers, or the free public servers 4.2.2.1 and 4.2.2.2.

Hope that helps a bit :) Any question about it, feel free to ask. I went through M$FT certification testing for MCP, MCDST, and MCSA, so I do know most of the preferred Microsoft ways to do things, on exams.

Forgot to mention: all said and done, you'll want to turn the DHCP server on the router off. It should still get it's internet IP from DHCP, but there should be an option to turn off the local DHCP server.