I had installed WSO2 Identity Server V5.2 on a VirtualBox machine, and it was working fine.
Then, I was doing some network testing/reconfiguration on my home network, where I was trying to separate my development (virtual) machines from my main in-home LAN by having the machine that was hosting VirtualBox connect wirelessly to a small router (a TPLink TL-WR702N) in a Bridge configuration, where the TPLink is connecting to my main WIFI network and then also exposing itself as a different WIFI network).
I was doing this testing because I am going to be working from a different location for awhile, and I wanted to isolate my dev machines while I was there and I only will have WIFI, and no hardwired connection, so I wanted to see if I could bridge wirelessly.
That machine hosting VBox started up ok and actually, the WSO2 machine also came up ok, but then when I tried to start the WSO2 IS (./wso2server.sh), it would output the 1st 3 lines and then hang on the 3rd line which was "User Java memory...".
If I move the hosting machine back to my normal LAN (i.e., not on the "bridged" network), everything works fine.
I noticed that when the hosting machine was on the bridged network, I couldn't ping the network gateway (192.168.0.1) from the VBox guest machines.
Would that cause the WSO2 to hang during startup? What else might be causing this problem?
Thanks,
Jim
I think that the problem was that WSO2 IS seems to need to be able to resolve the hostname during startup, and that was combined with needing to (apparently) bounce the machine to get the networking working. After the bounce, the networking seemed to get straightened out and then the WSO2 IS was able start ok.
Related
First I must say that I have no idea what kind of problem it is (Ubuntu/Windows/vmware/secureW2), so I hope anyone can select the necessary information from this mess.
I am running an Ubuntu 15.04 guest on a Windows 10 host using the vmware Virtual Machine. The Ubuntu internet icon in the right hand corner claims that it has a (wired) connection, yet I can't browse or ping google. Windows 10 is successfully connected by wi-fi, vmware uses a bridged connection (automatic) and my router enables DHCP. I can successfully ping my router from within the VM (at least, I assume 192.168.1.1 still refers to my actual router, and not some virtual router). In windows I can see two network adapters running (VMnet1 and VMnet8), both of which say they're enabled but have no internet access. I tried installing the bridge protocol in them, I tried using NAT instead of a bridge, but all to no avail. I was still connected just a few days ago when I was at school, which makes me think SecureW2 (a program responsible for connecting me to the school wi-fi) could also be involved somehow.
Everyone thanks in advance!
Turns out it was DNS related, caused by Ubuntu and SecureW2. The /etc/resolv.conf file was set up specifically for the LAN at school, for which I blame SecureW2. I "solved" it by adding my router IP to (the top of) the name server list, though I know this is only a practical solution.
we have been trying to solve a strange problem for the last 2 days but after a lot of searching we are stuck at the same point. We previously had Windows Server 2012 and it was working great, no problems, but decided to upgrade to R2 and that's where all our problems started.
Server:
HP PorLiant ML310e Gen8
2 Network cards ( Broadcom NetExtreme Gigabit Ethernet )
Windows Server 2012 R2
Clients:
Windows 8.1 Pro
We use one of the network cards for the server and the other for a virtual machine in Hyper-V. When the server was updated, all users, groups and permissions where created and assigned, so every member of the network could join their computers with their new users and passwords (no problem here), but when clients try to access the shared folders of the network they are unable to do so. And they can't ping the server.
So, the deal is that when the server is just started (or restarted) every client can see the network directories, can ping the server, everything works just fine for 2 or 3 minutes, then the network falls apart and there is no way for us to bring it back up other than restarting the server, but again it only works for like 3 minutes.
If we try to ping the server's IP address we get the 'General Failure' Message.
We have tried:
Enabling and disabling network adapters
Changing the order of the network adapters
Hyper-V is not being started
Disabling Network Load Balancing (NLB)
Disabling Large Send Offload (LSO) both with netsh and in the card's properties
Change the network adapter static IP
Disabling IPv6
Disabling the 'Allow the computer to turn off this device to save power'
Also noted that the server is getting several IP addresses from the DHCP. We have Microsoft Dynamics CRM 2013, and SQL Server 2012 installed.
Can any of you guys please help us with this situation? we'll be very grateful :)
Thanks in advance!
Greetings!
Ok,so this was an ol' windows trick... no matter what configuration we tried, windows server kept taking down the network minutes after it was started, so we:
Completely uninstall both network adapters
Restarted the server
Did the standar network adapter configuration (static IP addres, network, gateway, set the virtual switching for Hyper-V)
And everything started working again. So we kept the same configuration as before; Windows just needed to install the network adapters again.
Greetings!
I am using OSX Mavericks and VMWare Fusion v6.0.2.
I am running two Virtual machines, one Windows 7 Pro, and the other Debian Sid.
I do not wish to use NAT networking through the Host, I prefer to have the VMs sitting directly on the network, but I am having a problem getting the bridged networking functionality of VMWare Fusion working correctly. I have set the VMWare Network preferences page to Bridge the VMs to the Mac internal WiFi adapter.
Both VMs can ping the router, and they both get valid DHCP assigned IP addresses for the LAN. They can both connect to the Internet over the network bridge and browse and download files.
My problem is when I wish to communicate between the VM->Host, Host->VM, or VM->VM over other ports. For example if I try to SSH from OSX Host to the Debian VM, the request times out. The Windows 7 VM has a SQL Server running on it, but I cannot connect to it from the OSX host, or from the Debian VM. The Debian VM has a xsp4 web-server running on port 8080, but neither the OSX host nor the Debian VM can access it.
I can ping from Host->VM, VM->Host, and VM->VM with no issue, they can all see each other on the network, and the OSX host is sharing network folders to the Windows 7 VM without a hitch. It seems like it is allowing some communication, such as DHCP requests, Ping requests, Windows Network Shares, and Web Browsing, but is not allowing anything else.
I have turned off the Windows Firewall, OSX Mavericks firewall is turned off, and the Debian VM doesn't have selinux or iptables firewalls installed.
I have found several similar question threads while researching this problem, but a lot of them are for much older versions of VMWare Fusion, or are for VMWare Workstation which has different network preferences.
I can get these scenarios working to a degree if I switch VMWare's network settings to use NAT instead of bridging, but that messes up the IP addresses of the VMs, I want to keep them on the same network.
For what its worth, I did eventually come up with an answer for this.
There are two different versions of VMWare Fusion 6.x, Standard and Professional.
I was using the Standard version.
I changed the licence for a Professional licence, which allows you to add new network configurations in VMWare Preferences (and other cool things like that).
I added a new network with the default options, then assigned all of my VMs to that new network interface. I also turned on Promiscious mode in settings, but that might not have changed anything.
I then rebooted the VMs, set them up correctly to work on their new IP addresses, and Lo and Behold, I was able to establish connections between VM->Host and VM->VM. Exactly what I wanted.
I realize that this post is several years old, but since I had such a hard time with an issue similar to this, I wanted to post my answer as well, though I am not positive it really solved my issue. No problems still.
My setup:
MacBook Pro (Retina, 15-inch, Mid 2015)
OS X El Capitan
My problem:
In order to allow me to clone my private school git repository using ssh keys, I have to run a bridged network connection for my Windows 10 Eduction VM using VMWare Fusion.
What I've Tried:
http://www.kapilarya.com/windows-sockets-registry-entries-required-for-network-connectivity-is-missing
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1016466
And several other blog posts and forum replies, all attempting to do somewhat the same thing.
Answer:
After numerous attempts to reset just about everything you could, I took a step back and brainstormed. Then I thought, if my host machine (Macbook Pro) could connect wirelessly to the internet, this bridged connection should still work. I checked the Network Adapter's MAC Assigned to the VM's Network Adaptor and it was different from my host computer's wifi address (MAC Address). I then entered my host machine's wifi network address (MAC Address) in as the effective MAC Address for the Windows VM Network Adaptor and..voila, internet.
I can't seem to figure this out and hoping someone can give me some pointers. I'm unable to open a port on a Azure VM. After a fresh provision of a Windows 2008 VM I've disabled the Windows Software Firewall for all networks. Next i went to the azure management portal and added a TCP endpoint for port 9090 (both public and private).
While connected to the server via RDP i visit http://www.canyouseeme.org/ to test if port 9090 is open. But it comes back as error cannot see the port 9090.
As far as I can tell this is a standalone VM not connected to any domains or special networks.
Any ideas what is missing?
This was a strange problem that i "fixed" by changing the VM size from extra small > small and back again. For some reason something was reset and i could open the port again.
I am using VMWare Player 3.1.0 on Host OS Windows 7 Professional 64-bit. My guest is is SUSE Linux ES 10. My guest OS (SUSE) runs JBoss App Server which I access from host using HTTP. I used a "Bridged" connection to set up all this.
My problem:
When I am connected to network on the Host (using wired network adapter) I can connect to the http server on the Guest OS and browse the application. However, when I am disconnected from the network on Host (unplugged the wire), I cannot access to the guest OS app server and browse the application. I use the guest OS ifconfig command to find out ip address of the guest OS. This ip address does not change whether connected or disconnected. I have even tried using Wireless Data card, but that does not work either.
I have tried "NAT" as well as "Host Only" connection and rebooted the guest but it does not work either. I think for some reason the guest OS can only recognize the physical network card (which is disconnected).
I need to run this machine (my laptop) independently of the network because I use this for demo and need to be able to connect from my host OS to Guest OS.
I am not sure I understand exactly what you are trying to do, but I do know setting up a working NAT configuration will offer you the most flexibility.
Click the networking icon and select settings, Select NAT.
Follow these steps on your Unix OS
cd /etc/sysconfig/network-scripts
Make a backup of your ethernet adapter configuration
cp ifcfg-eth0 ifcfg-eth0.bak
Next modify the settings to look like the following:
DEVICE="eth0"
BOOTPROTO="dhcp"
HWADDR="What ever was here on your system"br/>
NM_CONTROLLED="yes"
ONBOOT="yes"
Save your changes
Restart your network adapters
/etc/init.d/network restart
Try nslookup www.google.com
You should now be able to connect back and forth from your Windows Host and Linux guest.
theJay28
-p.s. I had screenshots, but I do not have the 10 points yet to post images.
I figured that the solution is to restart the VM after making the changes to the NetWork setting on the VMWare. I selected Network for the VM as "Host Only" shutdown the VM and started it again. After that I was able to do what I wanted to do (i.e. browse the web application on guest from the browser in the host machine) without connecting the host to the network.
So key to the solution in my case was to make the network changes and restart the VM.
Any comments suggestions welcome...