I am studying Active directory. I created a virtual lab to experiment for the couse I am studying.
I am using Oracle VM 6.1 and I created 2 virtual machine. One where I installed Windows server 2019 and one wher eI installed Windows7 (my laptop cannot run anything bigger than that).
In each VM I created 2 network adapters, the first is attached to "internal network" on and the second to a "bridged adapter"
I then set the ip of the win2019 VM to 192.168.100.10 and the one for the Win7 machine to 192.168.100.50, both from the network configuration of the OSs.
I then activated the DNS service on the Win2019 and used 192.168.100.10 as DNS in the Win7 network configuration.
When I ping -4 server1 ( the anme I gave o the Win2019VM) from cmd in Windows7 I get as ip 192.168.100.31.
If I deactivate the bridged network adapters in both machines, I get the expected one, 192.168.100.10
If I reactivate the adapters, I get 192.168.100.31 again.
Seems WIN2019 gets the internal network adapter as second ethernet adapter.
From what I see on the course I am studing it is expected to have 192.168.100.10 as result of ping -4 server1 with both networks adapters active.
How can I get the DNS have server1 give 192.168.100.10 Ipv4 address when I ping it? Happy to provide more details if needed.
I am almost new to networking so please be patient if it is a stupid question. I checked the forum, but seems none posted this question here
Thnaks in advance
Edit this is the ipconfig /all for the Windows 2019 machine aka server1
This the win7 one
IPCONFIG /ALL from both servers.
Related
I recently installed Metasploit on my windows 10 PC. It changed a lot of configurations I think.
Now even after uninstalling it I still have that issue.
I'm connected to a wireless network which gives me (192.168.1.100), usually when I type this address it takes me to the same site as (localhost) or (127.0.0.1) but now it doesn't.
Note that I'm trying to access that IP from the same PC not externally.
And ping 192.168.1.100 works, but ping 192.168.1.100:80 does not work.
And I'm pretty sure I've tried all the possible configurations for the IIS binding.
I've been searching around and found no similar issues have been asked.
My desktop (windows 7) is in LAN, has IP (192.168.3.121).
I installed vmware (windows 7), using NAT connection (172.168.174.128). The guest is able to access internet without problem.
In guest, if I "ping 192.168.3.121", this will be ok.
If I "ping 192.168.3.xxx", will also be ok.
If I "ping 192.168.174.2" (DNS), this will be ok.
If I "ping 192.168.174.1", can't ping.
Note my host Vmnet8's ip is indeed 192.168.174.1. Ping from host also doesn't work.
From host:
"ping 192.168.174.128" (guest IP), does not work
"ping 192.168.174.2", does not work
Both host/guest windows are installed without any other "security/defender/firewall" related softwares.
Anywhere can go wrong?
Thanks.
If you configured your vmware VM to run in a virtualized NAT network, then you will not be able to access/ping your VM from the Host, or anywhere else for that matter, without configuring port forwarding for that virtual NAT network.
If you would like to be able to access your VM from your host you can either:
A) Change the mode of the network adapter for the VM to a bridged adapter. This will make the VM act as if it is just another computer on the same network your Desktop is and will be accessible at an IP such as 192.168.3.122
or
B) Add a Host-Only network adapter to the VM. This second NIC will be connected to a network that has no internet access, but is connected to the host and any other VMs on the same host-only network
Also, check the firewall settings to allow inbound ICMP inside the VM.
You mean that you cannot ping to the VMnet8 interface of your physical PC.
Maybe it is not activated.
It should be activated first by issuing the command at the cmd prompt with the admin's privilege.
C:\Windows\system32>netsh interface set interface name="VMware Network Adapter V
Mnet8" admin=ENABLED
I have seen this issue with two different windows 10 machine & two different version of vmware workstation ( 15 & 16).
One way it works is I start the wireshark & under capture options I select on VMWARE8(default for workstation/need to adjust according to your NAT Interface) & than start ping from My Local Machine to NAT IP of the VM .
It takes time but it works. I do not what triggers this .
My initial thought was it's one of the Windows 10 upgrade but with two different version of windows 10 & this old issue resurfaced.
Navigate to "Control Panel\Network and Internet\Network Connections".
Disable and Enable the VMware Network Adapter VMnet8 and try again.
I was having same problem after the latest release of VirtualBox-6.1.6-137129-Win update. "NAT Network" on any of the guest machine was not working. So i downgraded my virtual box version to 6 and works fine with all my VMs but problem remains in Kali Linux.
NAT Network was successful in giving IP to kali machine but Internet was not working. Problem i found was somehow gateway of kali wasn't set. Then i configured both Gateway and DNS manually and it worked for me.
Make sure that you Uncheck the option "Use this Connection only for resources on this network."
Kali manual configuration for IP, DNS and Gateway
I have an ubuntu VM running in VirtualBox. I am trying to ping it, but cannot. I have the network setting changed from 'NAT' to 'bridged'.
here is the screenshot of the ip address info:
and here is the result of a ping....
i did some google searching, but have not been able to pinpoint the issue yet.... thanks
When you use NAT mode, you will never ping the virtual machine from the host machine because it is the NAT restriction. But when you use the bridged mode, you should be able to ping the virtual machine because it will create a direct path as if both of the machine directly connected. If the ping is fail, perhaps there is some program or application that are blocking the network like a firewall.
we have a situation here. We are all working on a database installed into a virtual machine running on our laptops. The virtual machine is naturally configured to use NAT networking and all goes well.
We need to move this VM because its very RAM consuming and we found another machine to place it.
The new machine have an IP into a different subnet but is perfectly reachable by our laptops.
We configured the VM to use Bridged nwetorking so VM now have the same IP of the other subnet.
The guest OS is perfectly reachable from network so this is not a problem.
When I connect to VM's Oracle I obtain an ORA-12505 ...
Since I'm not a dba how to configure oracle to listen correctly from the new subnet ??
Thank in advance
EDIT:
another clue: when I connect to the VM and with the oracle user I give a LSNRCTL services I obtain
TNS-12541 no listener
When I switch back to the OLD subnet ALL works fine
SOLVED !!! The problem was on linux OPEN SUSE ! The network name was set to change according to DHCP.. The network name was not found on tnsnames.ora and the service did not start
Removing the option to change name according to DHCP all now seems to work properly
I have windows server 2012 installed on a VM along with windows 8 to do DHCP lab (I am new to networking), but the server cannot assign an IP address to windows 8.
I am using a wireless router.
In the server's powershell, I type ipconfig /all to see my IP address and subnet mask and my default gateway,
which is IP address:
10.0.2.15 255.255.255.0 10.0.2.2
I went to network to set static IP address the same as above and the preferred DNS server is 10.0.2.15.
Then I create a DHCP range: 10.0.2.100 to 10.0.2.200 and DNS server is and I can see my scope in the DHCP view.
I boot up windows 8 on my VM to see it works.
I go back to server to refresh the address release but nothing happens.
In windows 8 , I command prompt the ipconfig /all
Ipaddress : 10.0.2.15 (which is server address?) subnet mask: 255.255.255.0 default gateway: 10.0.2.2 DNS server : 192.168.1.1
What am I doing wrong? Is the problem with my DNS configuration?
Hmm...It's not quite clear what steps you took to set up your server :(.
Exactly why is your DNS server (192.168.1.1) in a different Network? Are you using a relay Agent?
I will assume you have already installed DHCP server role and feature and
hence have DHCP manager up and running.
Go through the checklist below.
did you activate the scope?
did you specify the domain name server (006) IP and Router (003) IP?
did you check the 'Address Lease' column to see if DHCP is leasing any Add?
did you make sure DHCP guard is not enabled?
Install Network monitor to view DHCP transaction between Client and Server.
You should try runnning ipconfig /release and ipconfig /renew on client instead of server.
The site link below might also help.
https://technet.microsoft.com/en-us/library/hh831538.aspx
Since DHCP server is using broadcast method to release IP address, you might run into the situation where you have more than 1 DHCP server in your network. Run the IPCONFIG /ALL again to make sure you got the IP from the right DHCP server.