Recommended Posts

hi I am having some issues with ESXi .... I am trying to connect my virtual machines to the rest of my LAN but I honestly have no idea how.... its not like the desktop version its a little trickier O.o just saying encase people think they know the answer because they used a desktop version ....any ideas? PLEASE :D

Link to comment
https://www.neowin.net/forum/topic/1119130-need-esxi-help/
Share on other sites

And what physical nic did you connect to your vswitch that you put your vms on?

So for example

post-14624-0-82429300-1352813119.png

I have a Lan vswitch that the physical nic in the host is connected to my real world lan switch

Then I have a wan vswitch that host nic is connected to my cable modem so that my VM router can route and firewall traffic between internet and my vms and my physical devices as well.

it really isn't that difficult....it is actually more difficult working with the desktop version....you are probably over complicating your networking.

Can you access your host from a computer on your network?

Is your guests on the same network?

Did you load the vmtools on the guest os?

What ip do you get in your vm?

If you can get outside access through your vm, you should be able to get on the network if it is on the same subnet.

it really isn't that difficult....it is actually more difficult working with the desktop version....you are probably over complicating your networking.

Can you access your host from a computer on your network?

Is your guests on the same network?

Did you load the vmtools on the guest os?

What ip do you get in your vm?

If you can get outside access through your vm, you should be able to get on the network if it is on the same subnet.

my VM gets local address 127.0.0.1 .... my server which is hosting the VM has an ip to the network and I use vsphere to connect to the server and the VMs but I cant connect to the VMs obviously any other way ... I do not see anything about the Vswitch on esxi or the vsphere I may just be blind and its and switch option is blanked out on the physical ESXi interface.... so what you suggest is changing the VMs 255.0.0.0 subnet to 255.255.0.0 manually ?

And what physical nic did you connect to your vswitch that you put your vms on?

So for example

post-14624-0-82429300-1352813119.png

I have a Lan vswitch that the physical nic in the host is connected to my real world lan switch

Then I have a wan vswitch that host nic is connected to my cable modem so that my VM router can route and firewall traffic between internet and my vms and my physical devices as well.

I have never seen that kind of layout on my vsphere :s ? also the NIC i have no idea what one its connected to xD i just connected al my E001 thing on the vnetwork

Here!

post-14624-0-16525700-1352815119.png

If your clients are not getting an IP - how and the hell do you think there going to be on an network

127.0.0.1

Is LOCAL loopback - that is not anything, changing mask is not going to do anything.

What network should your VMs be on? Is this esxi box located somewhere colo or something - or is on your local network?

What IP do you use to access your esxi box via client? Is it public or private address?

Here!

post-14624-0-16525700-1352815119.png

If your clients are not getting an IP - how and the hell do you think there going to be on an network

127.0.0.1

Is LOCAL loopback - that is not anything, changing mask is not going to do anything.

What network should your VMs be on? Is this esxi box located somewhere colo or something - or is on your local network?

What IP do you use to access your esxi box via client? Is it public or private address?

I know that im not stupid ;( I guess I didnt explain my self enough (you have seen my posts im not very good at explaining ) .... I know 127 is a loop back I use it every day when testing server scripts ;( its just I didnt know why the DHCP was not giving it an IP ... then i realised the DHCP was not working ... so I have manually set it a IP and the subnet and now im just trying to connect to my linux server but I do not think it has SSH or FTP installed / running and I cant do that as this is an isolated network (I am currently within a lab at university with the isolated network )

also I found the Vswitch its all on the same NIC2 so thats all gravy

"I know that im not stupid"

Going to keep my mouth shut on that one, I didn't say it ;)

So if you know 127.0.0.1 is loopback -- WTF did you bring it up for?

You manually set its IP to what? Didn't you have a post a while back asking how subnets work? Why did you mention /16 vs /8 when all you had mentioned was a loopback address?

Can not HELP you if don't know what your seeing!! When asked how your esxi is connected you state that you have NEVER even seen the networking tab? Then you throw out a loopback address and wonder why your not able to talk on a network. How are we suppose to help you with this sort of information?

edit: sc302, if he did not have nic assigned to the VM - how would it even have a loopback address?

"but I do not think it has SSH or FTP installed"

What your VM? Or some server on you schools network? If a VM - how would you not know if? You stated its "my linux server"

So are you VM's on your network or not? Do they have a IP on your segment? You do understand esxi has a firewall built into it that could be causing you some grief depending on what your wanting to do exactly as far as ssh, ftp, etc.

Tons of paperwork involved behind upgrade as well as research to verify that the change will not effect current production in any negative way. Basically it is much easier to leave it sit until a absolutely detrimental upgrade is required. Call it lazy but it could be a couple of months before I can do a simple upgrade.

****s not broke why fix it I guess, same reason you don't go around upgrading firmware on your routers and switches every time new one comes out. Production works - don't break it ;) Unless its a security issue or feature that is required, let it work. I hear ya.

Until I noticed the name on top frontoffice.local figured it might of been your home setup, etc.

edit: sc302, if he did not have nic assigned to the VM - how would it even have a loopback address?

"but I do not think it has SSH or FTP installed"

What your VM? Or some server on you schools network? If a VM - how would you not know if? You stated its "my linux server"

So are you VM's on your network or not? Do they have a IP on your segment? You do understand esxi has a firewall built into it that could be causing you some grief depending on what your wanting to do exactly as far as ssh, ftp, etc.

It could be assigned to the wrong network. he may have some other form of networking, doesn't 1394 get assigned a network adapter? or he imaged some crap back on and it is trying to retain some old settings from the old computer...whoknows, we sure don't have much to go on.

well I think linux would show loopback even without a nic? but I don't believe a windows box would?

Hey one good reason to update to 5.1 - they fixed the autostart featured that was broken. In 5.0 autostart of VMs did not work, you had to use a script to get around the issue. But now in 5.1 it works again.

Here is what I got

http://www.newegg.co...N82E16833106036

Comes with low profile bracket you use. Also notice they have a bulk version here

http://www.newegg.co...N82E16833106033

For like $5 cheaper - prob get that one if i were you. $5 is free pint at your local taphouse ;)

sure if all your doing is internet its not that big of issue. But what about lan device to lan device, or pulling a file off one of my Vms - if at 100 its like watching paint dry to move a 700MB iso.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • lots of people us facebook for stuff, threads though no
    • Can you read? I've said I'm willing to pay more for a notchless (no notch) 3:2 screen.
    • Not even an OLED display on the laptops. Also it seems that the laptop design isn't the same as the Surface Ultra model. Looks like bargain bin at high prices.
    • make your own notch - it's not that hard
    • VirtualBox 7.2.10 by Razvan Serea VirtualBox is a powerful x86 and AMD64/Intel64 virtualization product for enterprise as well as home use. Targeted at server, desktop and embedded use, it is now the only professional-quality virtualization solution that is also Open Source Software. Presently, VirtualBox runs on Windows, Linux, macOS, and Solaris hosts and supports a large number of guest operating systems including but not limited to Windows (NT 4.0, 2000, XP, Server 2003, Vista, 7, 8, Windows 10 and Windows 11), DOS/Windows 3.x, Linux (2.4, 2.6, 3.x, 4.x, 5.x and 6.x), Solaris and OpenSolaris, OS/2, OpenBSD, NetBSD and FreeBSD. Some of the features of VirtualBox are: Modularity. VirtualBox has an extremely modular design with well-defined internal programming interfaces and a client/server design. This makes it easy to control it from several interfaces at once: for example, you can start a virtual machine in a typical virtual machine GUI and then control that machine from the command line, or possibly remotely. VirtualBox also comes with a full Software Development Kit: even though it is Open Source Software, you don't have to hack the source to write a new interface for VirtualBox. Virtual machine descriptions in XML. The configuration settings of virtual machines are stored entirely in XML and are independent of the local machines. Virtual machine definitions can therefore easily be ported to other computers. VirtualBox 7.2.10 changelog: VMM: Fixed issue when CentOS 10 VM was not booting due to the message "Fatal glibc error: CPU does not support x86-64-v3" (​github:gh-642) Devices/EFI: Fixed booting issue when ARM VM had less than 1024 MiB of RAM assigned (​github:gh-679) USB: Fixed issue when it was not possible to attach USB device to headless VM on Apple Silicon/macOS 26.4.1 (​github:gh-631) Storage: Fixed issue when VIRTIO-SCSI device was not recognized as SSD device by guest system (​github:gh-634) Network: Fixed issue in E1000 emulation code which triggered debug log creation (​github:gh-645) Network: Fixed issue in E1000 emulation code which prevented OS/2 guest from booting (​github:gh-683) Linux Host: Fixed issue when VMs could not be started due to kernel oops (​github:gh-639) Linux Host and Guest: Fixed issue when kernel modules were failing to build with openSUSE 16.0 kernel Linux Host and Guest: Added initial support for kernel 7.1 Linux Host and Guest: Added extra fixes for RHEL 9.8 kernel (​github:gh-676) Linux Host and Guest: Added possibility to build source code using NASM instead of YASM as the assembler (​github:gh-520) Linux Guest Additions: Added initial support for Extended Data Control Protocol for clipboard sharing with Plasma on Wayland guests (​github:gh-33) Linux Guest Additions: Added extra fixes for preventing vboxvideo kernel module build with kernel version 7.0 and newer (​github:gh-655) OS/2 Guest Additions: Fixed issue when Shared Folders automount and clipboard sharing stopped working (​github:gh-551) Download: VirtualBox 7.2.10 | 170.0 MB (Open Source) Download: VirtualBox 7.2.10 Extension Pack | 19.1 MB View: VirtualBox Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Week One Done
      suprememobiles48 earned a badge
      Week One Done
    • One Month Later
      Windows Guy earned a badge
      One Month Later
    • One Month Later
      Prasann earned a badge
      One Month Later
    • Week One Done
      Prasann earned a badge
      Week One Done
    • First Post
      Dys Topia earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      510
    2. 2
      +Edouard
      174
    3. 3
      PsYcHoKiLLa
      100
    4. 4
      Steven P.
      87
    5. 5
      ATLien_0
      70
  • Tell a friend

    Love Neowin? Tell a friend!