I have an older dedicated PC running on my home network as a webserver. Trying to retire it by replacing it with a VM on a brand new workstation Santa brought me. Simple home hobbyist network consists of router, 10Gb switch and of course computing devices off of that.
The new machine is running Windows11 Pro, and via Hyper-V I have a CentOS 7 VM. I've configured the firewall to enable http service (and port 80) being accessible from outside my network. I'm running httpd. From behind my router/switch I can access the web server with no problem, from the host machine and other machines on my network). Alas - I'm unable to access this web server remotely/externally - even after turning of the VM's firewall and ensuring port forwarding was properly pointing to IP:80 from my router. I have been scouring the web/forums/etc. for days now - nothing I've tried seems to work.
Also, I was careful in ensuring the Hyper-V settings for a virtual switch are pointing to my actual hardware NIC and set accordingly as found here and other forums (see attached image for details).
From all the "experimentations" I've tried - it's seems like the port is just not being forwarded from my router properly. So it's really pointing towards my router at this point. BUT - I can and have configured real hardware before (over decades) with no problem. Since I'm NEWB to Hyper-V and VM's - I'm worried some setting may not be correct.
Thus - reaching out to anyone with similar experience who's solved this problem. Thanks in advance.
Here's a graphic in which I captured some of the many things I've tried to no avail.
settings, etc.
Related
I am installing VMware vSphre ESXi 7.0.2. But I cannot use web client (http://<ip_address>/ui)
When installed first time, I can connect with https://<IP_address> (It will be redirect to https://<IP_address>/ui ) and can create VM. But I found I cannot use some SDD/HDD. So I have re-installed ESXi after created the RAID partitions.
Re-Install was look OK, and I can see DCUI and set IP, DNS etc... After all set, I've tried to use https://<IP_address>. But it was timed out. (I have checked several things, then I found the ping does not work.)
I restarted the server then ping is OK. But when I try to connect with https://<IP_address> then the ping became "Destination net unreachable". (I have confirmed it with "-t" option.)
I thought it is firewall settings. So, I changed "--default-action" and "--enabled" but it still not working. Just in case, I have stop to use RAID disks and re-install it again (it is same as first installation), but it was same results.
There's likely still a networking-related misconfiguration. Use DCUI to verify IP/subnet mask/gateway/VLAN tag (if necessary) and that the appropriate NIC has been configured.
If those are set correctly, the DCUI also has some built-in testing options which allows you to do some outbound ping testing. By default it will check 3 hosts, including the gateway and usually two DNS names, but those can be changed to other options.
I red lot of post about this question without find the good answer. The situation is simple, I have a server (Go) running on Ubuntu 14.04 (VMware Workstation 12.1.0 Pro). It listens on the 8001/8002 ports. From the host of the VM (Windows 10), I can access it from the host (Windows 10) but from my Xamarin Application or the others computers, I can't access this server.
I tried lot of things such as port transfer, edit of the NAT propreties (of the VM) and edit of the vmnetnnat.conf file as well. I tested about bridge connection but I didn't find the way to make it works with this way. etc
I also did transfer port from my internet box to get the access by IP instead of private network address (192.168.XXX.XXX) but it didn't works too.
If anyone can help, thank !
By default your Workstation configures your VM in either NAT or Host-only or event in Custom network configuration what means your host computer (you Windows 10) is the only endpoint which can access this box without any additional configuration in your router.
I would suggest you the easiest way is to use "Bridge" configuration what you mentioned below by getting (perhaps DCHP) IP schema from your parent router (the one gives your Windows 10). Thus your VM will be available across your "Home network", Once done, check your ICMP (pings) from Windows 10 to your VM, make sure you can see it.
Second point is that your 8001/8002 ports might be closed by firewall (iptables) in your ubuntu / Windows 10. You probably want to check your both firewalls as your traffic is being routes by "Virtual router" of Workstation.
I am a GIS tech trying to get migrate to Geoserver, unfortunately I am not very savvy on web hosting.
I installed the Windows version 2.3.1.
I was able to build by map and access it through localhost:8080\geoserver\www\
I take that to mean that the jetty server it working.
I understand that I should be able to replace my local IP address where "localhost" is and be able to access it from another computer via Http.
I can't figure out the next step. I have found great tutorials on every part of geoserver process except this. And the user guide does not get into this either.
My set up: Cable Modem > Router > PC with Geoserver
What I have tried: Setting up a virtual server on my router. I have tried changing by router to inbound port 8080 to private port 8080
I also tried 80 to 8080
and 80 to 80
I also tried windows firewall exception. and turning off windows firewall.
I read about using appache tomcat but I have not installed it because it seems that jetty is working (at least as a local host) and I don't want to put another program on 8080. And to my understanding it can work stand alone but I really honestly don't know no.
I am must be missing some vital piece of information on how to do this. I am hoping it is just so basic that it wasn't worth mentioning on tutorials.
Thanks
Karin
This would be a GeoServer configuration question, but since its deployed in jetty the solution is likely in the underlying jetty configuration. That being said it is a guess on my part (the jetty side of things) how they set up this distribution, but if you find a jetty.xml file, perhaps under an /etc directory then you should be able to edit that file and set a proper host in the configuration.
Seriously though, this has to be a pretty common GeoServer question so I bet they have some documentation floating around for setting this properly in their software distribution.
http://docs.geoserver.org/latest/en/user/webadmin/basics.html
That seems to indicate it might be dependent on your container configuration, in which case look through how ever they are configuring jetty for a Host setting that is likely hardcoded to 'localhost'
Win7 PC running Rails in an Ubuntu VM via VMWare Player. I'm working on a site and would like to show it to a friend who's outside my network.
I found this blog post, which got me very close: http://blog.fardad.com/2012/06/vmware-player-and-custom-nat-port-map.html
OK, so I have the VM that is using NAT. As I understand it, that means that the VM will appear to have the same IP address as the parent machine to outside traffic.
I went into NAT settings and added port forwarding:
Host Port: 8200 Type: UDP Virtual IP Address: 192.168.198.184:3000
OK so my understanding is that I should now be able to go to 192.168.1.1xx:8200 (the IP of my 'real' PC) and access the webserver running in the VM. But when I go to that address, I don't get anything. I can ping 192.168.198.184 (the VM) from the PC.
What I want to be able to do is go into my router and set up a port that will eventually forward into the VM.
It seems like I'm missing something very small but I don't know what that is. Help, please.
If anyone is curious how to get the Virtual Network Editor:
go to the vmware-directory and run in elevated cmd.exe-box
rundll32.exe vmnetui.dll VMNetUI_ShowStandalone
http://communities.vmware.com/message/2155960#2155960
Find the vmnetnat.conf file, usually located in
C:\ProgramData\VMware\vmnetnat.conf
or
C:\Users\Application Data\VMware\vmnetnat.conf
Edit vmnetnat, add similar line in the [incomingtcp] section
8200=192.168.198.184:3000
Restart VMware NAT Service.
Try using Bridged network option in vmware player instead of NAT. It replicates your physical network.
You can use an http proxy to do that, by doing that you don't need to expose your entire private network, check out this blog post for more information how to access docker containers from external devices
We have a multi-threaded process which makes multiple calls to multiple target machines from a source machine using NetApi’s eg. NetServerGetInfo, LSAOpenPolicy, NetShareEnum, NetWKstaGetInfo, NetWKstaUserEnum etc… We make quite significant number of calls and have observed that over a period of time these calls fail. For example NetServerGetInfo starts returning error 53 after a while. This issue persist until we restart Workstation service or the machine. Accessing the target shares directly also does not work after such error is returned by our process.
The source machine from where we are making calls is a Win 2k8 R2 and the target machines are 2k3 servers.
We are suspecting some kind of issue with NetApi calls or some kind of handle leak.
Has anyone faced similar issues while using these APIs and managed to figure out a solution?
I found few references online for similar issues:
http://social.technet.microsoft.com/Forums/en-US/windowsserver2008r2networking/thread/9f93508c-71fa-4807-b41a-8f558563afe3/
Snippet from above link:
Experiencing the exact same issue as stated about except we have 2 Windows Server 2008 R2's acting as Terminal Servers connecting to Server 2003 Shares. Rebooting the terminal servers seems to resolve the problem for about 2-4 days and then re-appears. The XP/Vista/Win7 workstations on the network has no problem accessing the shares on the 2003 Server, only the 2008 R2 servers.
Connecting the the 2003 Shares using the FQDN or IP address works, but using \servername returns network path not found. Setting up WINS on the network did not resolve this, or adding a static entry in the hosts file to the server.
There is no firewall software installed on the servers and we don't use Symantec products on the network (No Symantec Endpoint security).
Viewing of the eventlog also turned up the Event ID: 1006, could not validate DNS server, even though name resolution appears to be functioning without a problem.
http://support.microsoft.com/kb/816621
http://technet.microsoft.com/en-us/library/dd296694%28WS.10%29.aspx
https://serverfault.com/questions/205043/windows-share-the-specified-network-name-is-no-longer-available