Thanks for your answer, all is good now.
Cannot connect to background rest server using port 5000 on hyper-v windows guest
I have a hyper-v windows 7 guest. I also have a Rest server listening to port 5000 on this guest.
From the windows 10 host I can ping this VM. And I can ping the host from this VM.
I have added a rule to the firewall on this VM.
I'm using nmap to see if port 5000 is open on the VM, but I keep getting the status "filtered".
I cannot get port 5000 to open on this VM.
Any idea why the port 5000 cannot be opened on this VM?
Windows for business Windows Client for IT Pros Storage high availability Virtualization and Hyper-V
12 additional answers
Sort by: Most helpful
-
Anonymous
2021-07-22T11:30:36.893+00:00 You could try with firewall off as a test to rule out or confirm a firewall problem.
--please don't forget to
upvote
andAccept as answer
if the reply is helpful-- -
Ab Himmit 96 Reputation points
2021-07-22T16:55:25.077+00:00 Yes, tried that. With firewall disabled, the port is showing to be closed.
-
Anonymous
2021-07-22T18:30:01.087+00:00 Sounds like the service either doesn't listen on expected port or possibly some other device in route is blocking.
--please don't forget to
upvote
andAccept as answer
if the reply is helpful-- -
Anonymous
2021-07-23T02:57:56.14+00:00 Hi,
There are several links mentioned similar issue as yours. Maybe you could try these solutions to see if any one could help resolve your problem.
Ports refuse to open with firewall on or off
Problem with open ports in Windows Firewall
Why won't windows firewall open port
Firewall rules not working properlyAlso, we suggested that you could use Telnet instead of nmap to test if the port is open or not.
Thanks,
If the Answer is helpful, please click "Accept Answer" and upvote it. Thanks.