Hi Barry: Again the exacts of this may vary depending on the version of Workstation you're running, but you have three choices for networking. NAT, bridged, and host only. It sounds like you were set to NAT. In that situation, VMWare Workstation uses a virtual NAT router and sets your VM up behind that. In Host only, VMWare Workstation puts you on an isolated network, you can talk to the host and other VMs, but there is no internet access. Bridged puts you on the same network as the host. If the host's network has DHCP you'll get a lease from that DHCP server, it will be just like you have another computer on that network. You can do more complex things such as set up custom network segments and such, you can even simulate slow LAN segments, but those are the three basic settings. As I said it sounds like you're on NAT. This should be fine so long as you don't need anything other than your host to talk to the VMs. Often when I'm playing with software in a VM at work, if the software needs to be on its own domain such as SCCM 2012, I'll set up a VM using host only networking so there's no chance of interfeerance. Ryan -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Barry Toner Sent: Friday, August 03, 2012 3:29 PM To: Blind sysadmins list Subject: Re: [Blind-sysadmins] Problems setting static IP on SRV 2K8 Hi, With Andrews help off list I was able to solve this. Basically VmWorkstation puts you ona different network to the Network the host machine you are running the VM on. For example. My host machines network was 192.168.1.1 and the VM is sitting on 192.168.200.2 So keeping within that range I was able to set the static IP and I used the loop back address 127.0.0.1 for the Servers Preferred DNS. In a fact using the Server as it's own DNS. I once more have Internet connectivity and a Static IP so I can now go forward and configure AD. Cheers, Barry. -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Andrew Hodgson Sent: 03 August 2012 19:51 To: Blind sysadmins list Subject: Re: [Blind-sysadmins] Problems setting static IP on SRV 2K8 Hi, Ok if you have DCPromoed then you _must_ set the DNS server in TCP/IP properties to either 127.0.0.1 or the machine local IP. Andrew. -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Barry Toner Sent: 03 August 2012 18:52 To: Blind sysadmins list Subject: Re: [Blind-sysadmins] Problems setting static IP on SRV 2K8 Hi, I've AD installed and I've DCPromo'd. Didnt' this installer DNS when I installed AD? Cheers, Barry. -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Andrew Hodgson Sent: 03 August 2012 18:06 To: Blind sysadmins list Subject: Re: [Blind-sysadmins] Problems setting static IP on SRV 2K8 Hi, You haven't installed the DNS service onto the system so you can't use the local machine as a resolver. What that article is talking about is when you use the system as a domain controller, in which case the DNS needs to point to a machine that is authoritative for the AD forest, which in most cases is the local machine in most environments where the DNS service is installed on the same machine. Use your router or whatever settings you have on Windows 7 for the DNS server and it should work. When you go with AD it will need changing. Andrew. -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Barry Toner Sent: 03 August 2012 17:36 To: Blind sysadmins list Subject: [Blind-sysadmins] Problems setting static IP on SRV 2K8 Hi folks, I've set these up on client machines no problems for years but not on a server and not in a server running within a VM. FYI I'm using VM Workstation v8. I go into Network, adaptor settings, hit properties on TCP/IP v4. Typing in the static IP I want to use 192.168.2.24 I got the Gateway address prior by running ipconfig/all which came back as 192.168.2.0 So I put that in, and according to this MS Article http://technet.microsoft.com/en-us/library/cc754203(v=ws.10).aspx I can use the current machine as the DNS Server so I thump it's IP in to the Preferred DNS. In saying this according the the same article I can do the same for the alt DNS, but this throws up an error saying they both can't be the same. No problem I leave Alt DNS blank. I tick the box to validate on exit, click OK, click close. The Net Diog keeps coming up and it's aying it's found a problem but has no idea what it is. I'm also not able to browse out on to the net. I can ping the machine IP but the gateway address is unreachable. FYI I've tried the default Gateway of 192.168.2.1 and I'm using the default Subnet Mask of 255.255.255.0 Help? Cheers, Barry. _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins