Re: Testing environment question



Then you had better leave it on! If you are running a domain, the DC needs to be available at all times that anyone might need it .

"JohnB" <jbrigan@xxxxxxxxx> wrote in message news:u$VRqH2mIHA.5956@xxxxxxxxxxxxxxxxxxxxxxx
The problem with that, that I forgot to mention is; the server isn't always on. But the router is.


"Bill Grant" <not.available@online> wrote in message news:%23xFtZB2mIHA.5956@xxxxxxxxxxxxxxxxxxxxxxx
You can't run a domain on a network like that without making a few changes.

For your domain members to function properly they must use the local DNS server. That is how they find domain resources, including the logon server. It makes no difference whether they are hard metal or virtual machines.

Turn off the DHCP function on the router. You can set up DHCP on the DC or you can just configure the machines manually to use the router for default gateway but use the DC for DNS.

Modify the DNS on the DC to forward to a public DNS (such as the one at your ISP). Your local DNScan now supply the local needs of AD and resolve foreign URLs.

"JohnB" <jbrigan@xxxxxxxxx> wrote in message news:u%23cQa21mIHA.1768@xxxxxxxxxxxxxxxxxxxxxxx
I am in the process of studying for a MCP, and have run into a problem. I have the following setup:

- I have setup a PC with a 180-day eval copy of Windows Server 2003.
- It's a home network with a NetGear router. The router is setup for DHCP.
- There are 4 computers on the network, counting the 2003 server.
- On one of the PC's I have install Microsoft's Virtual PC. The VPC has been joined to the domain.

My problem is I can't use any of the 2003 Administrative MMC's from the VPC. It says it can't find the domain, even though the VPC was joined to the domain without a problem. I'm guessing it's a DNS issue. The reason I say that is, the VPC doesn't show up in DNS on the server. I do not have DHCP setup on the server.

I thought about configuring DHCP on the server, thinking the VPC would then show up in DNS. But my problem is, I already have DHCP running on the router and, I don't want to turn that off because the "home" computers rely on that.

What's the best solution for this situation? Should I just set the VPC to static IP, and then add it in DNS on the server? I'd rather not, because then I miss out on the opportunity to test this as if it was a corporate network. But then I don't know of any other way, while still keeping DHCP on the router. (I guess I have the option of putting static IP addresses on the other home computers, and then disabling DHCP on the router).

Thanks in advance for your help.






.



Relevant Pages

  • Re: SBS 2003 Misconfigured?
    ... I've thrown quite a bit at them, and just have to disagree that they are inherently less secure than the netgear. ... setup DHCP and I have also gone in and manually created a new scope ... when I first used the Netgear router with SBS 2003, ... than one SBS server in a company makes no sense. ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot connect to RWW from home PC
    ... eth0 172.26.0.1/16 Extra none ... That would be the address you need a DNS record for. ... One question - if I reset the Thomson Router will that clear all the ... Heres' the info for our server: ...
    (microsoft.public.windows.server.sbs)
  • Re: NAT/RD install quirkiness. Server seems to work fine, but why
    ... DHCP is disabled and only a range of static IP addresses are ... One of which is the server. ... Although I don't have the DNS settings in front of me, ... router as the gateway. ...
    (microsoft.public.windows.server.networking)
  • Re: Connecting Remotely to Server/Desktop Files (Remote Access)
    ... The router will have two sets of DNS entries: ... Those it gives to DHCP clients. ... DNS servers it uses on it's external interface.) ... > I'll try it later this evening when I'm at the server and see if it works. ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot connect to RWW from home PC
    ... No 10.0.0.138 is the address used to log onto Thomson's router to make the ... On the DNS question I can add an MX record in the DNS area of GoDaddy's ... eth0 172.26.0.1/16 Extra none ... Heres' the info for our server: ...
    (microsoft.public.windows.server.sbs)