Unable to access <ip _ address>\myintranet - xampp

192.168.1.123\wordpresssite works fine, whether PC is awake or in sleep mode.
192.168.1.123\myintranet (a vanilla php-html thing) is only available when the host PC is awake.
Both sites are in C:\XAMPP\htdocs
Why the difference in accessibility?
How do I make \myintranet available, whatever state the host PC is in?

Related

Hyper-V - No Guest Internet

I'm using a Windows Server 2019 server from Microsoft Azure. I have installed Hyper-V with the management tools and am now trying to setup a Ubuntu 14.04LTS VM inside of Hyper-V. I create a new External Switch however when setting up the Ubuntu instance there it tells me that there is an issue with the DHCP server. When I check my network connections for the newly created switch there is IPV4 connectivity, with packets being sent and received.
Things that I have tried:
-Ensured that inside of the Virtual Switch Manager that in my newly created virtual switch, the external network is selected as my main internet adapter. And that the "Allow management os to share this network adapter".
-Tried selecting "Internal Network"
-Inside of the ubuntu server, tried dchlient -r and dhclient eth0 to try to retrieve a new IP (For internal network this has worked, but without internet access, for external ip it hangs on the command dhclient eth0)
-In Network Connections I have tried bridging the two connections (out of desperation, "bricks" the vps causing me to not be able to rdp, must create a new azure vm)
-I have tried right clicking the main "ethernet" inside the Network Connections and allowing sharing options to other users.
Please help as I'm quite lost as to why the Ubuntu Guest is not connecting to the internet with the new network switch
The virtual switch connection types are very confusingly named, and sharing is somewhat flaky. I've had best results with the Internal Network. Most of the time it just works but there are certain situations when the NAT service breaks and you will have to restart some combination of the host and guest machines, possibly both -- I've not found a way to just restart the virtual switch service without restarting the host OS.
If you need to use the External Network type, be aware that your actual physical router will be in the mix, so you must make sure that it is properly configured, especially if you're doing MAC filtering on your router and the guest is not using the hardware MAC. This usually happens because of the virtualisation process itself, even if it's not something you've configured in the guest.

Thin client vs. PC for RDP-only connection

Context : I'm switching my whole desktop environment, and after many thoughts, I'm going with a Virtual Machine hosted on a Google Cloud (Win Server 2016)
The server is a "Single User" machine, that will receive an RDP connection. The terminal must allow :
Dual Monitor
Port forwarding (USB, Local Printer)
What would be the best option :
Buying a refurbished PC, and use Native Remote Desktop
A proper thin client that supports RDP
Raspberry Pi 3 (Linux with a RDP session)
I'm looking for the best performance for general work (no 3d, Cad, ect.)
I used for this purpose a raspberry pi with Raspbian. For the remote sessions I use Vinagre.
It works very well and it's cheap.
But I am not sure about multimonitor and port forwarding...

Detect RDP Session on Remote WinXP machine (not on local network or domain)

I have set up a Win XP machine at work that we use as our server, to allow RDP connections. This allows all our staff to access the server from home when needed. As it is not a server OS, we are missing many of the terminal services features a regular server would have. The machine only allows one RDP session at a time (which is a minor inconvenience, but not a big deal).
What is bothersome, is that no one can tell if the server is currently being used in an RDP session, and we all keep booting each other off. Every solution I have found online assumes the remote computer is a Server OS or on a local network/domain. Our staff's home computers are not connected to the office network and we have no domain set up at the office.
Is there any way to tell if the server is in an RDP session before remoting onto the server from home? Ideally we would be able to detect which home computer is accessing the server. But if that is not possible, it would be extremely helpful to at least know that an RDP session is running.
We were previously using logmein, which could tell us if the remote computer keyboard and mouse were active and allow a chat with the user currently remoted on/physically on the machine. This was extremely convenient, but involves logging onto the logmein website and going through a semi-lengthy process of connecting. It is also much slower and resolution is much worse than RDP. Not super convenient for regular daily use.
This post deals with the same issue
https://superuser.com/questions/313390/ways-to-check-if-user-is-active-on-remote-machine-before-rdping
but the accepted response is to use qwinsta on cmd, which I believe is only available on server OS's. Other responses include using psexec (I've tried using psloggedon.exe, but this appears to only work for users on the same domain). Another suggests using the wmic.exe command, but when I try that I get the error: The RPC Server is unavailable (I think this also needs to be run on the same domain).
So basically - is there any way to check for active rdp sessions on a Win XP machine from a remote computer not on the local network/domain?
I'm open to outside-the-box solutions like writing a simple app to run on the xp server and tell remote machines what IP is connected in an RDP session.
Going on Harry Johnston's suggestion, I wrote an app which finds who is connected to the xp machine on port 3389, and relays that information by udp to receiving apps. Now we can check if someone is connected and who it is before unwittingly booting them off. Thanks Harry!

I am not able to host my own Web site

I have a high speed cable internet connection at home. I have D-link router, and I connect 2 computers, one is a desktop running Windows XP, the other is a laptop running Windows 7. I am perfectly able to use internet on both computers.
Now I want to host my personal web site from my home computer. I have already built the site that is running on my home network. Now I want to make it accessible from internet. I did all the procedures to open the appropriate ports on my router, allow incoming connections, and port forwarding setup, using the router's guide : http://www.dlink.com/-/media/Consumer_Products/DIR/DIR%20826L/Manual/DIR_826L_MANUAL_EN_UK.pdf .
However I am still not able to see my web site from public internet.
When I try to go to my site using my local IP address (192.168.0.103) or computer name, the site is loaded on other home computer, but when I try the same using my public IP address (found with "what is my ip" on google search), I get "Page cannot be loaded" error.
Can someone please help me telling what I am doing wrong, and how the problem can be fixed?
Thanks in advance.
Are you attempting to hit your WAN IPaddress from inside your house, aka, on the lan that the WAN would hit? It could be NAT Reflection/lack thereof getting in your way. Make sure you're trying to hit your WAN IP from a network outside of your local network. If you have a phone, turn off wifi, and use your phone.
Besides that, you've listed all of the basic steps necessary. Should the above not be the problem, I would start by checking your PCs firewall. In particular on Windows 7 checking to make sure you click real hard on that "public networks" button. Then just try and ping port 80, not load the webpage. If you can't ping, it suggests configuration issues with your router/connection. If you can, there's just some configuration that's effed up with your webserver.

getaddrinfo() returns 127.0.0.1 for remote host

I have an application which uses getaddrinfo() to translate from the hostname of a PC in a Windows Workgroup to the IPV4 address for that PC on the LAN. (Note, I don't mean getting the address of the PC the code is running on, I mean the address of another PC on the LAN!) This has been working in the field as well as in the lab for quite some time but now I have a Windows 7 (32 bit) PC that behaves anomalously. The hostname for this PC is "elbow".
I compiled the sample code provided by Microsoft for getaddrinfo() at http://msdn.microsoft.com/en-us/library/windows/desktop/ms738520%28v=vs.85%29.aspx
When I run this sample code on any PC on my LAN and specify "elbow" as the hostname, getaddrinfo() returns the loopback address 127.0.0.1 instead of the correct one (192.168.1.110). However, if I specify any other hostname getaddrinfo() returns the correct address!
At some point in the past "elbow" did NOT exhibit this behavior, so clearly something about that PC has changed to cause this behavior. I have tried restoring the PC disk image to a point where I think it did not cause this behavior, but that made no change.
It also makes no difference whether the PC is hardwired or wirelessly connected to the LAN. DHCP is enabled for all PCs on the LAN. The behavior is persistent even with a complete power-down of all PCs, routers and switches.
Hit a similar problem and wanted to post just in case someone else found this thread.
The same thing happened on our side with a customer installed computer. We found that the customer changed their hosts file to associate 127.0.0.1 with the pc's name... a separate program using getaddrinfo to find a certain subnetwork kept failing...they ended up renaming the computer temporarily to use this function but they also could have fixed their host file.
The hosts file on that Win 7 computer was found in /windows/system32/drivers/etc.
I wanted to update this with the answer. The elephant in the room was the ISP's DNS. I was under the mistaken impression that my subnet was isolated from the ISPs DNS but that was not the case. For whatever reason, their DNS is returning 127.0.0.1 for the hostname "elbow" but as soon as I renamed it to something else my problem went poof! I also uncovered another PC that had the same problem, and renaming it fixed it too. The thing both PCs have in common is that both had undergone OS reloads, but the problem did not become apparent until some time after those OS reloads.

Resources