[Chirpy]

[url]https://www.afp548.com/forum/viewtopic.php?showtopic=10720[/url]

Here’s the complete thread, I couldn’t get things to resolve on the internal side of the gateway until I killed the asterisk described here…

[Chirpy]

Have you checked Web|Sites|Settings to make sure there isn’t still an asterisk there?

Before I removed that I couldn’t resolve from my local network.

[Chirpy]

FWIW,

I appeared to have solved my problem. The Gateway Assistant appears to not open up the needed ports in the firewall to allow DNS and web requests through. Or I somehow donked them up after the fact, although I hadn’t touched them.

In Server Admin I went to “Firewall”, then “Setting” and then the Services tab. Both DNS – Inbound queries and DNS – responses to outbound queries (Port 53) were unchecked. So I checked those. Also, and what first drew my attention, HTTP aka port 80 was also unchecked. I checked it. This was on the “Allow only traffic for “any” on these ports” option.

Then I had a friend last night, and the wifey this morning try both sites. They now both work!

Maybe this will help you.

[Chirpy]

Oddly, I’m in your exact situation.

I’ve also fired up and configured DNS services, have removed the star in Web setup, and everything is working fine from my side of the gateway (set up with the assistant). However no one from anywhere outside can get webpages. Pings work, and the DNS names resolve to the IP address of the server.

I need to doublecheck, but I’m reasonable sure that a filemaker database I was playing around with on that server was accessible via direct IP addressing. That was a couple of weeks ago.

This one has me a little perplexed.

[Author]

Posts