why isnt my internal IP address 192.168.1.xxx?

iWerli

Reputable
Mar 10, 2014
41
0
4,530
so when i type in the ipconfig command, it comes up with "192.168.247.128" as my ip. and arent IPs supposed to be 192.168.1.xxx? im using Kali Linux in a VMWare virtual machine so is that why its weird? and if so how can i make the 3rd set a 1? its important that my stepdad sees the IP as 192.168.1.xxx.
 
Solution


IInuyasha74 is INCORRECT because he over looked a key thing I outlined, do NOT change anything in Windows.
What your not understanding is a Virtual Machine is a OS wrapped INSIDE of the real OS on the REAL PC. So it isn't actally 'running' the PC hardware directly (what you BOOT to when you turn on the PC is Windows not the VM). So a 'Virtual' NIC is created to software emulate the same function as your...
IP addresses can be anything between 0 and 255 for each section. I'm not sure if all routers support switching the "192.168." portion, but its not uncommon to switch the last two. You should be able to go into the router and set it, as well as change it in your computers internet settings.
 


thanks, so how would i change my ip from 192.168.247.128 to something like 192.168.1.128 *without* going into the router?
 


how can i check whether its static or DHCP?
and is there a way to make it static without going into the router? because that would be best
 
Without going to the router, you can try it may not work.
Under Windows 7
Start/Control Panel/Network and Internet/Change Adapter Settings. Right-click the network device you are using, go to Properties. Click Internet Protocol V4 (TCP/IPv4). Properties

Use IP address 192.168.1.6
Subnet Mask 255.255.255.255
Default Gateway 192.168.1.1

Primary DNS: 192.168.1.1
Alternative DNS: 8.8.8.8
 


ill have to try this when im home in 30 minutes, ill let you know if it works! thanks
 


IInuyasha74 is INCORRECT because he over looked a key thing I outlined, do NOT change anything in Windows.
What your not understanding is a Virtual Machine is a OS wrapped INSIDE of the real OS on the REAL PC. So it isn't actally 'running' the PC hardware directly (what you BOOT to when you turn on the PC is Windows not the VM). So a 'Virtual' NIC is created to software emulate the same function as your network card, BUT not to confuse 'WHOSE' NIC it is (Windows or a VM) it is set to it's own network IP, then NAT translated to the core OS (Windows) to then make the 'real' network connection.

To help illustrate:

<<((VM 192.168.247.128)) Virtual NIC translates to / from>>
\==>> Windows NIC (Wifi/Network Card) 192.168.1.95 {IP Provided by router}
\==>> Router (192.168.1.1) ---> To World

OP Needs to go back to RTFM on VMs first before messing with a Linux OS and understand the 'basics' of computers (how each part works, what is OSI, what are the 7 Layers, etc. ) or will keep being lost doing very technical things. This is where taking the CompTIA A+ Certification classes will help teach you 'the basics' FYI.
 
Solution
I am guessing that the rest of the computers (Physical computers not VM's) are using the 192.168.1.0/24 subnet to get DHCP addresses from the DSL router between 192.168.1.1 and 192.168.1.254. and your VM is picking up the 192.168.247.128 address automatically. If this is the case the reason is most likely that the VM is set to use 'NAT' networking where a virtual switch is installed and assigns a DHCP address to all the VM's attached to the NAT VLAN switch. and from there all the network traffic will appear to come from the host computer.

If you wish to leave your VM connect to the DSL router to get a IP address then you will have to go to the VM's settings (Varies depending on VMware, Virtual PC, Hyper-V etc) and set the networking mode for that VM to 'Bridged'. This will then connect your VM to a different virtual switch which connects directly to the Ethernet port with no NAT or routing and it will then use the DHCP from the DSL router.