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

Split-DNS and RED15

We are using a RED15 in Standard/Unified Mode. It connects up with our SG 125 fine and we can access MOST things. We can access the Internet, DNS is working, able to access Shares, etc.. but for some reason we can't access some servers we have setup via Split-DNS (RDS and Exchange).

I'm unable to Ping the IPs in Split-DNS whereas I can Ping other IPs on our network fine. I'm unable to use Remote Desktop to get to the servers in the Split-DNS or access anything else on them (i.e. Shares, Services.) Anything (PCs/laptops/etc..) that aren't behind the RED15 are able to access everything in Split-DNS so I don't believe we have anything setup incorrectly from that "side".

I feel like it should be something simple but I've been able to figure it out. I'm willing to start from scratch and take any recommendations from the Community.

I hope I've included enough information for at least a starting point.

Thank you for your time.

This thread was automatically locked due to age.

Parents

0 BAlfson over 6 years ago

Hi Ryan and welcome to the UTM Community!

What do you learn from doing #1 in Rulz?

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 Ryan Ingman over 6 years ago in reply to BAlfson

Thank you for the Reply Bob.

As you can see in the screenshot I see the SYN entry from Remote Desktop to 192.168.10.6 (one of the Servers in Split-DNS) but that is it. The entries for 192.168.10.4 are a successful connection with Remote Desktop to a Server not in our Split-DNS.

I do have a Firewall Rule setup that allows ANY Service from Source (RED15) to Destination (SG 125) and vice versa that I forgot to mention in my original Post.
Cancel
Vote Up 0 Vote Down

Cancel
0 BAlfson over 6 years ago in reply to Ryan Ingman

Actually, Ryan, your post contains two pics of the Interface definition.

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 Ryan Ingman over 6 years ago in reply to BAlfson

Well I feel like an idiot. My apologies for not paying attention, I've corrected the Post.
Cancel
Vote Up 0 Vote Down

Cancel
0 BAlfson over 6 years ago in reply to Ryan Ingman

What does route print on the client behind the RED? Show the route for 192.168.10.0 255.255.255.0 if there is one.

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 Ryan Ingman over 6 years ago in reply to BAlfson

There is no Route for 192.168.10.0 255.255.255.0 in Active or Persistent
Cancel
Vote Up 0 Vote Down

Cancel
0 BAlfson over 6 years ago in reply to Ryan Ingman

If you do a tcpdump n the RED interface, do you see the DNS request come from the remote client?

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 Ryan Ingman over 6 years ago in reply to BAlfson

I wasn't seeing any DNS traffic generated when I tried to just use Remote Desktop (no DNS traffic even to a Server I know I can get into) so I just did some NSLookups. I have attached the file with that traffic.

One thing I did think about. The couple of servers I'm having trouble access are virtual machines on Hyper-V. I'm able to access the Hyper-V Hosts okay but not the virtual machines themselves.
Cancel
Vote Up 0 Vote Down

Cancel
0 BAlfson over 6 years ago in reply to Ryan Ingman

Ryan, try making a static route in the UTM to the subnet of the VMs - I bet you have a virtual switch in there that the UTM doesn't have a route for.

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 Ryan Ingman over 6 years ago in reply to BAlfson

Do you have any pointers on how the Static Routes need to be setup? I haven't been able to make it work.
Cancel
Vote Up 0 Vote Down

Cancel
0 BAlfson over 6 years ago in reply to Ryan Ingman

"Current Topology:

"Client<-->[RED15]<-->[Cable Modem]<--Internet-->[Cable Modem]<-->[UTM]<-->Internet Network"

What private IP is on the Client? Where is the subnet with the DNS server? What does a failed ping look like?

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 Ryan Ingman over 6 years ago in reply to BAlfson

That is our current Topology

Private IP is 192.168.30.130

Subnet with the DNS Server is 192.168.10.XXX

A failed ping comes back as "Request timed out"
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 Ryan Ingman over 6 years ago in reply to BAlfson

That is our current Topology

Private IP is 192.168.30.130

Subnet with the DNS Server is 192.168.10.XXX

A failed ping comes back as "Request timed out"
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data