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!
Related
I set up my own VPN by installing OpenVPN on a Ubuntu server, then I download client.ovpn file from Ubuntu server to my Windows laptop. And then, I import that client.ovpn to OpenVPN GUI app on Windows and finally, I connect to my Ubuntu VPN server and everything work fine.
I installed OpenVPN on Ubuntu server using this instruction: https://github.com/angristan/openvpn-install
So i think traffic flow will be like this:
My computer (browser,...) --> Ubuntu OpenVPN server --> Internet.
My question is does OpenVPN GUI encrypt traffic between my computer to Ubuntu OpenVPN server?
And as always, thank you so much.
Yes, the point of OpenVPN is that the traffic is encrypted (unless you disable all security in the server's config file) between the client (your Windows laptop) and the Ubuntu Server. Your traffic to the internet is not encrypted though. You'd best use Tor if you want to hide your IP Address online.
ISPs as of 2020 use deep pack sniffers which although can't read the information can easily log source and destination. They do that to prioritize traffic. If you are able to change your IP on the fly that might buy you a couple of hours but in the end they choose how much and how long you can maintain that connection at the speed you want no matter what is advertised. If you have large files to move and are not happy with the speed your best bet is to experiment with different times of the day. ISP leaves that option open for those who move a lot of data. My window of opportunity is between 4:00 am and noon. That could vary based on geographic location. Streaming services have tasked servers quite a bit in the last decade.
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.
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.
Okay, so I'm hosting a VPS for someone using Virtualbox. I've setup a server for that guy with a NAT network type ( this way I could port forward the entire thing so it can be used for what the guy wants ). The guy can use remote desktop to connect to the server, however. Everyone who tries to join his game, gets the same IP. I guess this has something to do with the guest settings, if I'm not mistaken.
Could anyone provide me any more information about the reason behind these IP's?
I'm running on the latest version of Virtualbox with a windows 7 enterprise 64bit version where a SA-MP server is being hosted on.
Everyone who connects to his server gets the ip; 10.0.2.2. Any help would be really appreciated
If a machine is located behind NAT, then all of the incoming connection will always be recorded only from a single source, that is you router's IP. It's normal since all of the incoming connection will have to go to the router first.
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.