Networking

[Sydders01]

Hello All,

 

I am an IT Apprentice in a school,

 

 

I would like to know more on networking.

 

I am after starting a job as an apprentice in a school.

 

I went home and build a server on a vm machine on a hp server desktop.

 

 

my setup is as follow

 

desktop has windows 7 ultimate installed.

 

VMware installed

 

server 2012r2 installed in the VMware machine

 

my question is as follows--

 

if I give the server a static IP address , how can I remote into it from a different workstation outside the VMware?

[Guest obsidianpillar]

Hello All,

 

I am an IT Apprentice in a school,

 

 

I would like to know more on networking.

 

I am after starting a job as an apprentice in a school.

 

I went home and build a server on a vm machine on a hp server desktop.

 

 

my setup is as follow

 

desktop has windows 7 ultimate installed.

 

VMware installed

 

server 2012r2 installed in the VMware machine

 

my question is as follows--

 

if I give the server a static IP address , how can I remote into it from a different workstation outside the VMware?

 

Put the VM's NIC attached to "Bridge Mode", then make sure you give the VM a similar IP address/subnet as your main network. Ensure you've enabled Remote Desktop and you'll be able to login.

[Sydders01]

Thanks Tom,

 

Please how do I go about putting my vm's nci in bridge mode?

 

how can I fine the ip address/subnet mask of my broadband?

[dloudon96]

Go to start, run, cmd, then type in ipconfig

[Sydders01]

Hi Thanks,

 

 

the address are in the 192.168 (APIPA) it means if I setup DHCP on my server and ranges , if the server looses the address I might not be able to connect to the server

[Guest obsidianpillar]

Thanks Tom,

 

Please how do I go about putting my vm's nci in bridge mode?

 

how can I fine the ip address/subnet mask of my broadband?

 

To put the VM's NICs to Bridge, launch VMWare Workstation, right click on your VM and click Settings, under "Network Adapter" change from NAT to Bridged. This will then use your local DHCP Server to obtain an IP (if the NIC inside of the VM is set to obtain an address from DHCP).

 

In your case however, before you do this you will want to change your Server 2012 VM to an IP within your subnet. To do this, you will need to find out what Class/Subnet your "Main" network's IP is on.

 

On your physical PC, go to Start > All Programs > Command Prompt. Within Command Prompt, enter in "ipconfig". You will see lots of address' here, ignore any that mention "VMWare". Scroll up until you see something similar/same as "Ethernet adapter Local Area Connection" or "Wireless adapter Local Area Connection". This is your physical address assigned to you if you haven't configured a static one. Eg yours could be 192.168.0.2 with your subnet as 255.255.255.0. (192.168.0.X is the standard for Virgin Media's SuperHubs)

 

We now know the two pieces of information we need.

 

Now, go to your Server 2012 VM, right click on the Networking Icon in the Taskbar, and click open Network and Sharing Center, right click on "Ethernet", then select properties. Double-click on IP Protocol Version 4 (TCP/IPv4). Now you can configure your static IP. Using my above example, and assuming your settings are the same (most UK ISP's settings are) give your VM an address of 192.168.0.200, subnet of 255.255.255.0 and default gateway as 192.168.0.1. For DNS, put in 8.8.8.8 as if your planning to setup Active Directory, the wizard will override this anyway.

 

I've tried to put the above in stupidly easy steps as possible. If you have any other problems however, feel free to reply!

[Sydders01]

Hi Tom,

 

 

 

Thanks it worked. I wasn't able to authorize my dhcp after creating it as there is no option to authorize when I click the action menu? does this have anything to do with the wifi connection?

 

 

To put the VM's NICs to Bridge, launch VMWare Workstation, right click on your VM and click Settings, under "Network Adapter" change from NAT to Bridged. This will then use your local DHCP Server to obtain an IP (if the NIC inside of the VM is set to obtain an address from DHCP).

 

In your case however, before you do this you will want to change your Server 2012 VM to an IP within your subnet. To do this, you will need to find out what Class/Subnet your "Main" network's IP is on.

 

On your physical PC, go to Start > All Programs > Command Prompt. Within Command Prompt, enter in "ipconfig". You will see lots of address' here, ignore any that mention "VMWare". Scroll up until you see something similar/same as "Ethernet adapter Local Area Connection" or "Wireless adapter Local Area Connection". This is your physical address assigned to you if you haven't configured a static one. Eg yours could be 192.168.0.2 with your subnet as 255.255.255.0. (192.168.0.X is the standard for Virgin Media's SuperHubs)

 

We now know the two pieces of information we need.

 

Now, go to your Server 2012 VM, right click on the Networking Icon in the Taskbar, and click open Network and Sharing Center, right click on "Ethernet", then select properties. Double-click on IP Protocol Version 4 (TCP/IPv4). Now you can configure your static IP. Using my above example, and assuming your settings are the same (most UK ISP's settings are) give your VM an address of 192.168.0.200, subnet of 255.255.255.0 and default gateway as 192.168.0.1. For DNS, put in 8.8.8.8 as if your planning to setup Active Directory, the wizard will override this anyway.

 

I've tried to put the above in stupidly easy steps as possible. If you have any other problems however, feel free to reply!

Edited September 2, 2021 by ZeroHour

[Guest obsidianpillar]

Hi Tom,

 

 

 

Thanks it worked. I wasn't able to authorize my dhcp after creating it as there is no option to authorize when I click the action menu? does this have anything to do with the wifi connection?

 

You normally authorise the server when you have an Active Directory domain setup. Have you got this? Be wary of that when you setup another DHCP Server on your main network you will have to disable the one by your router. Also, whenever you shut down the VM, no clients will be able to obtain an IP. This isn't the best way to do this by your solution. I would either settle for all VM's to be only connected to the NAT setting as it was in the first instance or do as you are doing currently but set a manual DNS on clients to be able to join domain etc.

 

Hope this helps.

 

Tom