Windows server 2019 Unable to communicate with public ip

Souri Bhowmick 96

I have a Windows Server 2019 running IIS, AD, and DNS services. It is able to communicate perfectly in the internal network but not able to communicate with public IP. I have forwarded the required ports in the modem and configured firewall rules. Is there something else which I need to do?

Lex Li (Microsoft) 5,582 Reputation points Microsoft Employee

2021-07-04T04:58:49.437+00:00

Try to draw a network diagram so that you can review what's missing, https://blog.lextudio.com/self-hosting-series-why-cannot-my-web-server-iis-be-reached-from-anywhere-else-8da0e0b252ef
Jiang Zhang 786 Reputation points

2021-07-08T11:41:18.82+00:00

Hi，

You could accept the useful reply as answer if you want to end this thread up.
If there is anything else i can do for you, please feel free to post in the forum.

Mulder

Accepted answer

Souri Bhowmick 96 Reputation points

2021-07-10T13:28:56.97+00:00

I am working with a co-worker on this. Port 3389 works now, No other port is working. I have tested with a windows server 208 and it works on that.
I am trying to host multiple websites and access them through the internet with the help of a domain name. I already have a domain name so I just require to create a subdomain internally and host the wesites.
Please sign in to rate this answer.
MotoX80 33,636 Reputation points

2021-07-10T14:56:00.997+00:00

What does CanYouSeeMe.org report for port 80 and 443?

Are you using IIS? Have you checked the IIS and HTTPERR logs?

Have you run a network trace? Network Monitor has been archived, but I still like to use to troubleshoot network activity.

https://www.microsoft.com/en-us/download/details.aspx?id=4865

Souri Bhowmick 96 Reputation points

2021-07-10T15:18:38.963+00:00

Thank you for your help. It is working fine now except port 53 which is blocked by ISP.

MotoX80 33,636 Reputation points

2021-07-10T16:01:58.307+00:00

So what was the problem?

Souri Bhowmick 96 Reputation points

2021-07-10T16:04:08.527+00:00

i reset the modem to factory defaults and then configured port forwarding and it started working.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

3 additional answers

MotoX80 33,636 Reputation points

2021-07-03T16:36:50.183+00:00
I have forwarded the required ports in the modem and configured firewall rules.

So are you trying to allow other machines on the internet to access this WS2019 server? (As a server to respond to inbound connections using port forwarding settings on your internet connected router.)

Is your server able to browse web sites on the internet?

To verify your port forwarding settings, use https://canyouseeme.org/ to verify that internet based machines can connect to the port that you are trying to expose. Use the netstat command to verify that some process is listening on that port.

netstat -aon | findstr -i listen

Temporarily turn the firewall off to verify that the rule you defined is correct.
Please sign in to rate this answer.
Souri Bhowmick 96 Reputation points

2021-07-04T05:22:51.907+00:00

Yes. I am trying to allow other machines on the internet to access this WS2019 server. I have disabled the firewall and checed. It is the same. I am able to browse from the server. Internet-based machines cannot connect to the port that I am trying to expose.

MotoX80 33,636 Reputation points

2021-07-04T11:40:16.15+00:00

Well then you have 3 things to verify.

Use netstat to check that a process is listening on that port.

On the router/modem check to see that you have the correct local IP address and port of your server defined in the forwarding rule.

Use Canyouseeme.org while on the server to test the forwarding rule.

Souri Bhowmick 96 Reputation points

2021-07-06T06:50:11.003+00:00

I have disabled firewall and checked also on the modem end ip and port details are correct but still I am not able to reach the dns port form outside. Process is listening on the port.
Forwarding input are ok but modem not forwarding to the port. Also same rules I have configured with a centos VM and it works without any issues.

MotoX80 33,636 Reputation points

2021-07-06T12:11:57.507+00:00

I am not able to reach the dns port form outside

What port are you trying to reach? DNS? What are you trying to accomplish?

Is your rule set for UDP port 53?

https://www.networkstraining.com/what-is-dns/
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Jiang Zhang 786 Reputation points

2021-07-06T05:51:25.02+00:00

Hi,

You may try MotoX80’s method, by checking listening port, firewall and forwarding rule stuff, or you can check if the gateway/router in your server is configured properly as well. If everything is fine, it’s better to forward an error message when the server is unable to communicate with public ip. Is that total Blank, Time Out, Bad Request, Cant Open The Page or anything else? More details will help for sure.

Accurately the most precise way is to run some Wireshark traces to confirm what is happening.

Best Regards,
Mulder Zhang

--------------------------------------------------------------

If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Souri Bhowmick 96 Reputation points

2021-07-10T05:28:50.243+00:00

It seems to be an issue with the firewall as the firewall is not allowing the ports to communicate with the public network. I have disabled the firewall and tried but still same error. Somehow by changing some firewall rules(allow edge traversal), I was able to make RDP work but other ports are still not accessible. I get site can't be reached error.
Please sign in to rate this answer.
MotoX80 33,636 Reputation points

2021-07-10T13:09:46.497+00:00

as the firewall is not allowing the ports to communicate with the public network. I have disabled the firewall and tried but still same error.

Well if you've disabled the firewall, I don't see how it could be the problem. Since it's disabled.

When I've gotten into situations like this, where I have a problem that I just can't figure out, I've had success in reaching out to a co-worker and have them sit down with me where I explain the problem to them. In more than one instance while I was explaining "here look at this, this is where I defined the setting", I realized the mistake that I had made. Other times, my co-worker would notice something that I did not recognize as a problem. Do you have someone who can help you?

You comment that you have defined the forwarding rules, but forum users can't see your screen. We don't know if you put in the correct IP or if there is some other setting in your modem/route that also needs enabled. Someone else might see something that you don't notice.

The best that us forum users can do is make suggestions to try to help you identify your problem.

So you defined port 3389 in a forwarding rule? And that works? What about port 80 or 445? Does CanYouSeeMe.org work for those ports? What about testing with a different machine?

You have not replied to my questions: What port are you trying to reach? DNS? What are you trying to accomplish? Is your rule set for UDP port 53?

Souri Bhowmick 96 Reputation points

2021-07-10T15:57:11.207+00:00

Thank you for your help. It is working fine now except port 53 which is blocked by ISP.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Windows server 2019 Unable to communicate with public ip

3 additional answers

Your answer