This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

RED's cant connect to certain site

Hello,

I have a internal ip address of 192.168.3.245, its my vcenter. Is resolves fine to vcenter.xxxxxx.local However any office on a red device can ping the ip and vcenter, but when they try to go to the vcenter.xxxx.local or the ip address its giving them an error of host not found. Anyone at the home office not on a red can access it fine. Any ideas'

Thanks.

This thread was automatically locked due to age.

Parents

0 Alexander Busch over 6 years ago

Yes ICMP is handled by the UTM. Your other traffic needs routing and firewall rules.

-
Cancel
Vote Up 0 Vote Down

Cancel
0 Todd Poynton over 6 years ago in reply to Alexander Busch

Hello,

I have red's configured with routing and firewall rules. I can get to other ip address via a web browser, just not the vcenter.
Cancel
Vote Up 0 Vote Down

Cancel
0 Alexander Busch over 6 years ago in reply to Todd Poynton

Anything in the logs? See Rule #1 in

-
Cancel
Vote Up 0 Vote Down

Cancel
0 Todd Poynton over 6 years ago in reply to Alexander Busch

ttpproxy[5911]: id="0002" severity="info" sys="SecureWeb" sub="http" name="web request blocked" action="block" method="CONNECT" srcip="192.168.70.128" dstip="" user="todd" group="" ad_domain="" statuscode="502" cached="0" profile="REF_DefaultHTTPProfile (Default Web Filter Profile)" filteraction="REF_HttCffAllowAll (Allow All)" size="2510" request="0x22018a00" url="vcenter.alliance321.local/" referer="" error="Host not found" authtime="1" dnstime="2" cattime="106" avscantime="0" fullreqtime="226306" device="0" auth="6" ua="" exceptions="" category="9998" reputation="unverified" categoryname="Uncategorized"
Cancel
Vote Up 0 Vote Down

Cancel
0 Alexander Busch over 6 years ago in reply to Todd Poynton

How is DNS resolved at the REDs? I think the REDs are not bridged, right?

-
Cancel
Vote Up 0 Vote Down

Cancel
0 Todd Poynton over 6 years ago in reply to Alexander Busch

Correct, they are not bridged. I think it has to do with DNS, as when I go to the ip address it pulls up but when you go to log in, it takes you to vcenter.alliance321.local which does resolve, but I think the red can not see the FQDN of vcenter.alliance321.local.

If I add, vcenter.alliance321.local to Add DNS Request Route, then use target as domain controller which is running my dns role would that fix the issue?
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 Todd Poynton over 6 years ago in reply to Alexander Busch

Correct, they are not bridged. I think it has to do with DNS, as when I go to the ip address it pulls up but when you go to log in, it takes you to vcenter.alliance321.local which does resolve, but I think the red can not see the FQDN of vcenter.alliance321.local.

If I add, vcenter.alliance321.local to Add DNS Request Route, then use target as domain controller which is running my dns role would that fix the issue?
Cancel
Vote Up 0 Vote Down

Cancel

Children

0 BAlfson over 6 years ago in reply to Todd Poynton

Todd, please compare your setup to DNS best practice.

Cheers - Bob

Sophos UTM Community Moderator
Sophos Certified Architect - UTM
Sophos Certified Engineer - XG
Gold Solution Partner since 2005

MediaSoft, Inc. USA
Cancel
Vote Up 0 Vote Down

Cancel
0 Alexander Busch over 6 years ago in reply to Todd Poynton

Sorry for late answer. Like Bob wrote please follow best practice. But I think yes. The devices behind the RED should resolve the name for the vcenter. DNS is essential for vcenter. What would be the best approach depends on your DNS setup, but try a req route.

Alex

-
Cancel
Vote Up 0 Vote Down

Cancel