Skip to main content
added 247 characters in body
Source Link

I'm configuring a clientless VPN on an ASA 5505, and have a few questions:

  • I assume that, when accessing CIFS, if they delete a file it just goes bye-bye? (i.e. no recycle bin equivalent on the client side... I also can't find one on the server side for a regular Windows file server. Noticed a few NASs have some sort of CIFS recycle bin feature, but don't see a way to turn this on for Windows.)

  • Is it possible to have some sort of confirmation dialog before they can delete? I know they're irritating, but with no trash it seems a reasonable precaution.

  • I can add individual Windows file servers as CIFS addresses, and that works fine. However, if I click the "Network" button, I get the error "Failed to retrieve domains". Where would I start to look for this issue? It's definitely using the LDAP logins fine, seeing the files according to the user's permissions, etc... so I'm not sure where else to look to rectify this.

  • Is there a way to have links to pages on the VPN home page that don't get accessed through the VPN? One example would be our OWA. We use Office365 for our Exchange server. I'd like to have a link for the OWA login for this, that would ideally use SSO (but that might not be possible in this scenario). I want to have the SSL VPN be basically be a portal for them to see all of the links to our resources, and not have to log in multiple times, but not use our bandwidth when it's not necessary.

ETA: To clarify, by clientless VPN I'm referring to the Cisco VPN usable through a web browser - almost a sort of portal page. The one that looks basically like this, although the appearance has been updated slightly since - Cisco example screenshot

I'm configuring a clientless VPN on an ASA 5505, and have a few questions:

  • I assume that, when accessing CIFS, if they delete a file it just goes bye-bye? (i.e. no recycle bin equivalent on the client side... I also can't find one on the server side for a regular Windows file server. Noticed a few NASs have some sort of CIFS recycle bin feature, but don't see a way to turn this on for Windows.)

  • Is it possible to have some sort of confirmation dialog before they can delete? I know they're irritating, but with no trash it seems a reasonable precaution.

  • I can add individual Windows file servers as CIFS addresses, and that works fine. However, if I click the "Network" button, I get the error "Failed to retrieve domains". Where would I start to look for this issue? It's definitely using the LDAP logins fine, seeing the files according to the user's permissions, etc... so I'm not sure where else to look to rectify this.

  • Is there a way to have links to pages on the VPN home page that don't get accessed through the VPN? One example would be our OWA. We use Office365 for our Exchange server. I'd like to have a link for the OWA login for this, that would ideally use SSO (but that might not be possible in this scenario). I want to have the SSL VPN be basically be a portal for them to see all of the links to our resources, and not have to log in multiple times, but not use our bandwidth when it's not necessary.

I'm configuring a clientless VPN on an ASA 5505, and have a few questions:

  • I assume that, when accessing CIFS, if they delete a file it just goes bye-bye? (i.e. no recycle bin equivalent on the client side... I also can't find one on the server side for a regular Windows file server. Noticed a few NASs have some sort of CIFS recycle bin feature, but don't see a way to turn this on for Windows.)

  • Is it possible to have some sort of confirmation dialog before they can delete? I know they're irritating, but with no trash it seems a reasonable precaution.

  • I can add individual Windows file servers as CIFS addresses, and that works fine. However, if I click the "Network" button, I get the error "Failed to retrieve domains". Where would I start to look for this issue? It's definitely using the LDAP logins fine, seeing the files according to the user's permissions, etc... so I'm not sure where else to look to rectify this.

  • Is there a way to have links to pages on the VPN home page that don't get accessed through the VPN? One example would be our OWA. We use Office365 for our Exchange server. I'd like to have a link for the OWA login for this, that would ideally use SSO (but that might not be possible in this scenario). I want to have the SSL VPN be basically be a portal for them to see all of the links to our resources, and not have to log in multiple times, but not use our bandwidth when it's not necessary.

ETA: To clarify, by clientless VPN I'm referring to the Cisco VPN usable through a web browser - almost a sort of portal page. The one that looks basically like this, although the appearance has been updated slightly since - Cisco example screenshot

Source Link

Cisco ASA5505 Clientless VPN/CIFS config questions

I'm configuring a clientless VPN on an ASA 5505, and have a few questions:

  • I assume that, when accessing CIFS, if they delete a file it just goes bye-bye? (i.e. no recycle bin equivalent on the client side... I also can't find one on the server side for a regular Windows file server. Noticed a few NASs have some sort of CIFS recycle bin feature, but don't see a way to turn this on for Windows.)

  • Is it possible to have some sort of confirmation dialog before they can delete? I know they're irritating, but with no trash it seems a reasonable precaution.

  • I can add individual Windows file servers as CIFS addresses, and that works fine. However, if I click the "Network" button, I get the error "Failed to retrieve domains". Where would I start to look for this issue? It's definitely using the LDAP logins fine, seeing the files according to the user's permissions, etc... so I'm not sure where else to look to rectify this.

  • Is there a way to have links to pages on the VPN home page that don't get accessed through the VPN? One example would be our OWA. We use Office365 for our Exchange server. I'd like to have a link for the OWA login for this, that would ideally use SSO (but that might not be possible in this scenario). I want to have the SSL VPN be basically be a portal for them to see all of the links to our resources, and not have to log in multiple times, but not use our bandwidth when it's not necessary.