Enhanced Security Measures in Place:   To ensure a safer experience, we’ve implemented additional, temporary security measures for all users.

Unable to access some of the LAN IDRACs Via GP VPN

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Unable to access some of the LAN IDRACs Via GP VPN

L2 Linker

Hello There,


I'm new to the field of firewalls, and I'm currently working with a PA 850 firewall, a Nexus switch, and four Dell PowerEdge R630 servers on my site. I've configured a GlobalProtect (GP) VPN on the firewall and set up subinterfaces for different types of traffic. However, I'm encountering an issue where I can't access the IDRAC (Integrated Dell Remote Access Controller) of two out of the four servers via the VPN. The IDRACs are in the 10.100.24.0/24 network, and interestingly, I can access the problematic server IDRAC IPs directly from the firewall. The issue only occurs when trying to access the IDRACs via the VPN.

Here are the details of the servers:

  • Server 1 IDRAC IP: 10.100.24.21 (working)
  • Server 2 IDRAC IP: 10.100.24.22 (not working)
  • Server 3 IDRAC IP: 10.100.24.23 (working)
  • Server 4 IDRAC IP: 10.100.24.24 (not working)

To summarize:

  • Via VPN: Able to access IDRACs of Servers 1 and 3, but not Servers 2 and 4
  • Firewall to Servers IDRACs: Able to access IDRACs of all servers

The firewall policies are configured to allow access via VPN to the corresponding subnet, but I'm unsure what is causing me to be unable to access the IDRACs of Servers 2 and 4. I've attached a sample network diagram of the LAN for reference. Any assistance would be greatly appreciated.

Thanks,

Punkn

1 accepted solution

Accepted Solutions

L7 Applicator

I see no diagram….  Is the 10.100.24.0/24 directly attached to the firewall… if so.. may be worth checking the gateway and subnet mask of the troubled servers,,,  

 

I would use monitor/packet capture on the firewall and add the servers to the filter to see if packets are being allowed… it may help…

 

last resort.. add a last place policy to deny all traffic from VPN to 10.100.24.0/24 to see if not allowed by your current policies and monitor session start

View solution in original post

2 REPLIES 2

L7 Applicator

I see no diagram….  Is the 10.100.24.0/24 directly attached to the firewall… if so.. may be worth checking the gateway and subnet mask of the troubled servers,,,  

 

I would use monitor/packet capture on the firewall and add the servers to the filter to see if packets are being allowed… it may help…

 

last resort.. add a last place policy to deny all traffic from VPN to 10.100.24.0/24 to see if not allowed by your current policies and monitor session start

Hello MB2222,

 

The problem was actually on the server itself. Someone had configured the wrong IDRAC gateway on the server. Thanks for the suggestions; I appreciate it.

 

Thanks,

Punkn

  • 1 accepted solution
  • 1134 Views
  • 2 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!