UMIACS - User contributions [en]

Network/VPN/Windows

2020-10-15T17:53:06Z

Atavakol: /* Connecting through the Pulse Secure client (for computers WITH ARM processors) */

'''Please note that this tutorial assumes you already have a network connection established.'''
'''If you have a UMIACS account, you already have access.'''

The UMIACS VPN is accessible through the Pulse Secure Client. Alternatively, you can establish a connection through a web browser.

'''As of May 10th 2019, MFA Authentication is mandatory.'''

'''NOTE: If your computer is a Microsoft Surface laptop or any other computer with an ARM processor, you will need to proceed differently from the standard Windows instructions. Please refer to the [[#Connecting through the Pulse Secure client (for computers WITH ARM processors)|instructions here]].'''

==Prerequisites==
* Device enrolled with [[Duo | UMIACS Duo]]

== Connecting through the Pulse Secure client (for computers WITHOUT ARM processors) ==
#'''Download the client:'''
#:[[Media:PulseSecure9.1R8.2.x64.msi|Windows 64 bit Pulse Secure Client]] (preferred) 
#:[[Media:PulseSecure9.1R8.2.x86.msi|Windows 32 bit Pulse Secure Client]] 
#:''Upon starting the client for the first time it may ask to upgrade the client. This will pull an up to date version of the client with the most recent configuration.''
#'''Start the client if it is not already running - it usually starts by default on bootup.'''
#:[[Image:Pulse Secure Desktop App.jpg|thumb|center|280px|[Windows] Start the client from the Start Menu.]]
#'''If the client is already running, double click its icon from the status bar.'''
#:[[Image:Pulse Icon.jpg|thumb|center|280px|[Windows] Double click its status icon to open.]]
#'''and click 'Add' (+) under the connection section.'''
#:[[Image:Pulse Secure1.jpg|thumb|center|280px|[Windows] Click the 'Add' (+) button to create a new connection.]]
#'''Enter a name for your VPN connection and the server URL 'vpn.umiacs.umd.edu''''
#:[[Image:Pulse Connection.jpg|thumb|center|280px|[Windows] Enter the name of the VPN server.]]
#'''Enter your UMIACS credentials and hit connect.'''
#:[[Image:Pulse UserPass.jpg|thumb|center|280px|[Windows] Enter UMIACS credentials.]]
#'''Enter Secondary Password for [[Network/VPN/MFA | MFA]]. For example, if you wish to push a notification to your device, type the word "push" into the secondary password box.'''

:::[[Image:Vpnmfa6.png|thumb|center|280px|[Windows] Enter Secondary Password.]]

::The Pulse VPN multi-factor authentication implementation relies on a secondary authentication source to fulfill the MFA requirement. As a result, you will be prompted for credentials twice.

::{|class="wikitable"
!Second Credential Password Value:
! Result
|-
| push
| Send a push verification to your Duo connected device
|-
| phone
| Send a call verification to your Duo connected device.
|-
| <press YubiKey>
| If you have a physical token then you would press the YubiKey for the one time password.
|}

::Please note that registering a YubiKey for use with the VPN requires interaction with UMIACS Tech Staff. Please [[HelpDesk | contact us]] if you would like to register a YubiKey for this purpose.

{{Note|Pro-tip: Select ‘Save Settings’ on the secondary authentication prompt to have Duo automatically use your preferred method.}}

You should now be connected to the UMIACS VPN.

==Checking VPN Status==
# In the bottom right hand corner, in your status bar, you should see an S icon. If there's a green arrow, that means you are connected! If there is nothing, that means you are not.
#:[[Image:Pulseicon2.png|thumb|center|500px|]]
# You can hover over this icon and it will show you the status of your connection.
#:[[Image:PulseStatus2.png|thumb|center|500px|]]

 

== Connecting through the Pulse Secure client (for computers WITH ARM processors) ==
ARM processors cannot natively run x64 or x86 programs without special emulation. Microsoft Surface laptops do not have x64 emulation yet, but they do have x86 emulation. However, not all x86 programs run smoothly even with emulation. As such, the best course of action for these sorts of machines is using the version of Pulse Secure that is specifically made for ARM processors, which is offered on the Microsoft Store.

'''Installation Instructions:'''

#[https://www.microsoft.com/en-us/p/pulse-secure/9nblggh3b0bp Go to the Pulse Secure page on the Microsoft Store.]
#Click the "Get" button and wait for it to finish downloading. Once it's finished downloading, the Get button should now say "Install". Click "Install".
#Once Pulse Secure is installed, continue to the Configuration Instructions.
(will finish installation instructions at a later time)

'''Configuration Instructions:'''
#Open Pulse Secure. It should have a green- and black-colored icon in the shape of an S.
#You should now see a gray window. Click on the "VPN Settings..." button in that window.
#You should now see the VPN page in Windows Settings. Click "Add a VPN connection".
#The VPN provider should be Pulse Secure. You will now need to enter the following information:
##Connection name: UMIACS
##Server name or address: vpn.umiacs.umd.edu
##Username: You can put in your UMIACS username if you'd like, or you can leave it blank.
##password: Leave it blank for security reasons.
##Choose to remember sign-in info ONLY if the password field is blank, for security reasons.
##You should now be finished with adding the VPN connection.
#Now under "VPN" and "Add a VPN connection" at the top, you should see a button that says "UMIACS". Click on that button.
#You will now be prompted for your username (if you did not fill it out when adding the connection) and password. Enter your UMIACS credentials, then click the "OK" button.
#You will now be prompted for a "secondary password". This refers to the method of multi-factor authentication you would like to use. Typing in "push" into this field will send a notification to the Duo app on your smart device, whereas "phone" will send a call to your registered phone number. Enter your choice of authentication, then click the "Next" button.
#After completing the multi-factor authentication via push notification or call, you should now be connected to the UMIACS VPN!

In case you would like to manually disconnect from the VPN, go to the same "VPN Settings..."/VPN page in Windows settings, click on the UMIACS connection, and click the "Disconnect" button.

Network/VPN/Windows

2020-10-15T17:32:55Z

Atavakol: /* Connecting through the Pulse Secure client (for computers WITH ARM processors) */

'''Please note that this tutorial assumes you already have a network connection established.'''
'''If you have a UMIACS account, you already have access.'''

The UMIACS VPN is accessible through the Pulse Secure Client. Alternatively, you can establish a connection through a web browser.

'''As of May 10th 2019, MFA Authentication is mandatory.'''

'''NOTE: If your computer is a Microsoft Surface laptop or any other computer with an ARM processor, you will need to proceed differently from the standard Windows instructions. Please refer to the [[#Connecting through the Pulse Secure client (for computers WITH ARM processors)|instructions here]].'''

==Prerequisites==
* Device enrolled with [[Duo | UMIACS Duo]]

== Connecting through the Pulse Secure client (for computers WITHOUT ARM processors) ==
#'''Download the client:'''
#:[[Media:PulseSecure9.1R8.2.x64.msi|Windows 64 bit Pulse Secure Client]] (preferred) 
#:[[Media:PulseSecure9.1R8.2.x86.msi|Windows 32 bit Pulse Secure Client]] 
#:''Upon starting the client for the first time it may ask to upgrade the client. This will pull an up to date version of the client with the most recent configuration.''
#'''Start the client if it is not already running - it usually starts by default on bootup.'''
#:[[Image:Pulse Secure Desktop App.jpg|thumb|center|280px|[Windows] Start the client from the Start Menu.]]
#'''If the client is already running, double click its icon from the status bar.'''
#:[[Image:Pulse Icon.jpg|thumb|center|280px|[Windows] Double click its status icon to open.]]
#'''and click 'Add' (+) under the connection section.'''
#:[[Image:Pulse Secure1.jpg|thumb|center|280px|[Windows] Click the 'Add' (+) button to create a new connection.]]
#'''Enter a name for your VPN connection and the server URL 'vpn.umiacs.umd.edu''''
#:[[Image:Pulse Connection.jpg|thumb|center|280px|[Windows] Enter the name of the VPN server.]]
#'''Enter your UMIACS credentials and hit connect.'''
#:[[Image:Pulse UserPass.jpg|thumb|center|280px|[Windows] Enter UMIACS credentials.]]
#'''Enter Secondary Password for [[Network/VPN/MFA | MFA]]. For example, if you wish to push a notification to your device, type the word "push" into the secondary password box.'''

:::[[Image:Vpnmfa6.png|thumb|center|280px|[Windows] Enter Secondary Password.]]

::The Pulse VPN multi-factor authentication implementation relies on a secondary authentication source to fulfill the MFA requirement. As a result, you will be prompted for credentials twice.

::{|class="wikitable"
!Second Credential Password Value:
! Result
|-
| push
| Send a push verification to your Duo connected device
|-
| phone
| Send a call verification to your Duo connected device.
|-
| <press YubiKey>
| If you have a physical token then you would press the YubiKey for the one time password.
|}

::Please note that registering a YubiKey for use with the VPN requires interaction with UMIACS Tech Staff. Please [[HelpDesk | contact us]] if you would like to register a YubiKey for this purpose.

{{Note|Pro-tip: Select ‘Save Settings’ on the secondary authentication prompt to have Duo automatically use your preferred method.}}

You should now be connected to the UMIACS VPN.

==Checking VPN Status==
# In the bottom right hand corner, in your status bar, you should see an S icon. If there's a green arrow, that means you are connected! If there is nothing, that means you are not.
#:[[Image:Pulseicon2.png|thumb|center|500px|]]
# You can hover over this icon and it will show you the status of your connection.
#:[[Image:PulseStatus2.png|thumb|center|500px|]]

 

== Connecting through the Pulse Secure client (for computers WITH ARM processors) ==
ARM processors cannot natively run x64 or x86 programs without special emulation. Microsoft Surface laptops do not have x64 emulation yet, but they do have x86 emulation. However, not all x86 programs run smoothly even with emulation. As such, the best course of action for these sorts of machines is using the version of Pulse Secure that is specifically made for ARM processors, which is offered on the Microsoft Store.

'''Installation Instructions:'''

#[https://www.microsoft.com/en-us/p/pulse-secure/9nblggh3b0bp Go to the Pulse Secure page on the Microsoft Store.]
#Click the "Get" button and wait for it to finish downloading. Once it's finished downloading, the Get button should now say "Install". Click "Install".
#Once Pulse Secure is installed, continue to the Configuration Instructions.
(will finish installation instructions at a later time)

'''Configuration Instructions:'''
#Open Pulse Secure. It should have a green- and black-colored icon in the shape of an S.
#You should now see a gray window. Click on the "VPN Settings..." button in that window.
#You should now see the VPN page in Windows Settings. Click "Add a VPN connection".
#The VPN provider should be Pulse Secure. You will now need to enter the following information:

I have already set up the base settings for the UMIACS VPN connection for you. As such, under "VPN" and "Add a VPN connection" at the top, you should see a button that says "UMIACS". Click on that button.
4) You will now be prompted for your username and password. Enter your UMIACS credentials, then click the "OK" button.
5) You will now be prompted for a "secondary password". This refers to the method of multi-factored authentication you would like to use. Typing in "push" into this field will send a notification to the Duo app on your smart device, whereas "phone" will send a call to your registered phone number. Enter your choice of authentication, then click the "Next" button.
6) You should now be connected to our VPN!

(In case you would like to manually disconnect from the VPN, go to the same "VPN Settings..."/VPN page in Windows settings, click on the UMIACS connection, and click the "Disconnect" button.)

Network/VPN/Windows

2020-10-15T17:08:38Z

Atavakol: /* Connecting through the Pulse Secure client (for computers WITH ARM processors) */

'''Please note that this tutorial assumes you already have a network connection established.'''
'''If you have a UMIACS account, you already have access.'''

The UMIACS VPN is accessible through the Pulse Secure Client. Alternatively, you can establish a connection through a web browser.

'''As of May 10th 2019, MFA Authentication is mandatory.'''

'''NOTE: If your computer is a Microsoft Surface laptop or any other computer with an ARM processor, you will need to proceed differently from the standard Windows instructions. Please refer to the [[#Connecting through the Pulse Secure client (for computers WITH ARM processors)|instructions here]].'''

==Prerequisites==
* Device enrolled with [[Duo | UMIACS Duo]]

== Connecting through the Pulse Secure client (for computers WITHOUT ARM processors) ==
#'''Download the client:'''
#:[[Media:PulseSecure9.1R8.2.x64.msi|Windows 64 bit Pulse Secure Client]] (preferred) 
#:[[Media:PulseSecure9.1R8.2.x86.msi|Windows 32 bit Pulse Secure Client]] 
#:''Upon starting the client for the first time it may ask to upgrade the client. This will pull an up to date version of the client with the most recent configuration.''
#'''Start the client if it is not already running - it usually starts by default on bootup.'''
#:[[Image:Pulse Secure Desktop App.jpg|thumb|center|280px|[Windows] Start the client from the Start Menu.]]
#'''If the client is already running, double click its icon from the status bar.'''
#:[[Image:Pulse Icon.jpg|thumb|center|280px|[Windows] Double click its status icon to open.]]
#'''and click 'Add' (+) under the connection section.'''
#:[[Image:Pulse Secure1.jpg|thumb|center|280px|[Windows] Click the 'Add' (+) button to create a new connection.]]
#'''Enter a name for your VPN connection and the server URL 'vpn.umiacs.umd.edu''''
#:[[Image:Pulse Connection.jpg|thumb|center|280px|[Windows] Enter the name of the VPN server.]]
#'''Enter your UMIACS credentials and hit connect.'''
#:[[Image:Pulse UserPass.jpg|thumb|center|280px|[Windows] Enter UMIACS credentials.]]
#'''Enter Secondary Password for [[Network/VPN/MFA | MFA]]. For example, if you wish to push a notification to your device, type the word "push" into the secondary password box.'''

:::[[Image:Vpnmfa6.png|thumb|center|280px|[Windows] Enter Secondary Password.]]

::The Pulse VPN multi-factor authentication implementation relies on a secondary authentication source to fulfill the MFA requirement. As a result, you will be prompted for credentials twice.

::{|class="wikitable"
!Second Credential Password Value:
! Result
|-
| push
| Send a push verification to your Duo connected device
|-
| phone
| Send a call verification to your Duo connected device.
|-
| <press YubiKey>
| If you have a physical token then you would press the YubiKey for the one time password.
|}

::Please note that registering a YubiKey for use with the VPN requires interaction with UMIACS Tech Staff. Please [[HelpDesk | contact us]] if you would like to register a YubiKey for this purpose.

{{Note|Pro-tip: Select ‘Save Settings’ on the secondary authentication prompt to have Duo automatically use your preferred method.}}

You should now be connected to the UMIACS VPN.

==Checking VPN Status==
# In the bottom right hand corner, in your status bar, you should see an S icon. If there's a green arrow, that means you are connected! If there is nothing, that means you are not.
#:[[Image:Pulseicon2.png|thumb|center|500px|]]
# You can hover over this icon and it will show you the status of your connection.
#:[[Image:PulseStatus2.png|thumb|center|500px|]]

 

== Connecting through the Pulse Secure client (for computers WITH ARM processors) ==
ARM processors cannot natively run x64 or x86 programs without special emulation. Microsoft Surface laptops do not have x64 emulation yet, but they do have x86 emulation. However, not all x86 programs run smoothly even with emulation. As such, the best course of action for these sorts of machines is using the version of Pulse Secure that is specifically made for ARM processors, which is offered on the Microsoft Store.

'''Instructions:'''

#[https://www.microsoft.com/en-us/p/pulse-secure/9nblggh3b0bp Go to the Pulse Secure page on the Microsoft Store.]
#Click the Get button and wait for it to finish downloading. Once it's finished downloading, the Get button should now say Install. Click Install.

Network/VPN/Windows

2020-10-15T16:58:08Z

Atavakol: /* Connecting through the Pulse Secure client (for computers WITH ARM processors) */

Network/VPN/Windows

2020-10-15T16:51:51Z

Atavakol:

Network/VPN/Windows

2020-10-15T16:47:11Z

Atavakol:

Network/VPN/Windows

2020-10-15T16:42:08Z

Atavakol: /* Connecting through the Pulse Secure client */

UbuntuPrinting

2019-09-09T17:06:38Z

Atavakol: /* Connecting to a printer */

==Overview==
Printing from your personal Ubuntu laptop or desktop is supported. If you are sitting at a supported UMIACS Ubuntu LTS desktop then please see our common UNIX/Linux printing documentation for [[CUPS]]. This documentation may not work for all versions of Ubuntu.

===Printer Accessibility===
In order to print you will '''need to be on the UMIACS internal network,''' either via a wired proxy drop or an [https://wiki.umiacs.umd.edu/umiacs/index.php/SecureShellTunneling SSH tunnel].

==Connecting to a printer==
In order for printing to function properly, you must complete '''ALL''' of the following steps:
#Open the 'Printing' dialog box and click 'Add'. You may have to click "Advanced settings" and ''then'' clicking "Add" in the box that pops up.
#Expand the 'Network Printer' dropdown list, and select 'Find Network Printer'.
#In the host field type "print.umiacs.umd.edu" and click find.
#:[[Image:UbuntuPrint01.png|thumb|none|300px|[3] Type 'print.umiacs.umd.edu' into the 'Host:' field and then click Find]]
#Select the print queue you wish to print to, click forward. If you are unsure which queue to use, see the [[PrinterQueueNaming| selecting a print queue]] page.
#:[[Image:UbuntuPrint02.png|thumb|none|300px|[4] Select the queue you wish to print to]]
#Name the printer. '''Take note of the model name listed in the Description. This will be used later!''' Then click 'Apply'
#:[[Image:UbuntuPrint03.png|thumb|none|300px|[5] Take note of the printer description, this will be used in later steps!]]
#In the printing dialog box, right click the newly added printer and select properties.
#In the 'Make and Model' line, click 'change'
#:[[Image:UbuntuPrint04.png|thumb|none|300px|[7] Click 'change' next the 'Make and Model' field.]]
#Ubuntu will now load a list of printers models (This will take a few moments). From that list, select the brand of the printer you are connecting to as noted in step 5.
#:[[Image:UbuntuPrint05.png|thumb|none|300px|[8] Select the brand of the printer as you noted in step 5]]
#Select the specific model of the printer as noted in step 5. Then click forward.
#:[[Image:UbuntuPrint06.png|thumb|none|300px|[9] Select the model of the printer as you noted in step 5]]
#Leave the "try to copy the option settings over from the old PPD" option selected and click forward.
#Select any additional features available for the printer (i.e. duplexing), and then click forward.
#Verify this process by printing a test page. You should get the default Ubuntu test page. If you just get a page with a string of text then the printer is not properly configured, and you should verify the settings.

Remote Desktop

2019-02-05T15:07:16Z

Atavakol:

=Introduction=

Remote Desktop allows you to connect to another computer from a network that is compatible. Currently, at UMIACS, this feature is only supported for Windows hosts using the Remote Desktop Protocol (RDP). If you need to remotely connect to a UNIX host, please see [[SecureShell]]. With RDP, you can control your Windows desktop environment through a graphical user interface. Mouse and keyboard movements are transferred over a network to a Windows host running an RDP server, which sends screen refreshes back.

To access an RDP enabled machine, you must be on the UMIACS physical network or [[VPN]]. You must also be authorized to access and remotely control the host you are requesting. If a remote session is active, it is not possible for another user to log onto the console in-person. Attempting to use RDP when a computer is in use by another user could force the existing user to logoff and lose their work. You should always quit RDP by logging off of the remote computer. Simply quitting the RDP client can cause you to stay logged in and prevent other users from accessing the remote host, even at the physical console.

=How to Connect=
*'''Prerequisites:'''
**Connected to the [[VPN | UMIACS VPN]] or be within the UMIACS network border.
**Be a member of the 'Remote Desktop Users' group on the remote machine.
==Windows==
For connecting to Windows client over RDP, we recommend the native Windows 'Remote Desktop Connection' client.

#To start the RDC client, click the "Start'" or "Windows" button on the taskbar. In the menu, navigate to "All Programs," "Accessories," then select "Remote Desktop Connection". Alternatively, you can search for "Remote Desktop Connection" in the Start menu's search field.
#Once RDC client starts, type the name of the RDP/Windows host you are trying to access. The name should be the Fully Qualified Domain Name (FDQN), e.g. "desktop.'''ad.umiacs.umd.edu'''". At this point, click "Connect" to initiate the RDP session.
#*[[File:RemoteDesktop-Connect.png]]
#After the connection is started, a warning message may alert you to an identity verification failure. For UMIACS machines, you can ignore this and proceed by selecting "Yes"
#*[[File:RemoteDesktop-SecurityWarning.jpg]]
#Upon reaching the Windows Security prompt, enter your UMIACS credentials. If the username is either not correct or not the desired account, select "Use another account". Click "Ok" when you are done.
#*[[File:RemoteDesktop-CredentialsPrompt-new.png]]
#You should now be viewing the remote computer. To terminate the session, you should logout of Windows.
To switch between your current host and the remote host, click the minimize or "-" button on the top connection bar. With RDC, the clipboard can be transferred between the remote and current host while the RDC client is running and logged in.

Alternatively, you can use the Microsoft Remote Desktop application from the Windows Store, which is available for download [https://www.microsoft.com/en-us/p/microsoft-remote-desktop/9wzdncrfj3ps?activetab=pivot%3Aoverviewtab here.]

#Open Microsoft Remote Desktop.
#Click "Add" in the top right corner.
#*[[File:Microsoft Remote Desktop Step 1.png]]
#Next, click "Desktop - Connect to a PC".
#*[[File:Microsoft Remote Desktop Step 2.png]]
#Type the name of the RDP/Windows host you are trying to access in '''PC Name'''. The name should be the Fully Qualified Domain Name (FDQN), e.g. "desktop.'''ad.umiacs.umd.edu'''". Once you have filled that out, click Save.
#*[[File:Microsoft Remote Desktop Step 3.png]]
#Now, you should be on a page where you will see the PC you have just added. '''Double-click the PC''' and enter your UMIACS credentials. Then, click Connect.
#*[[File:Microsoft Remote Desktop Step 4.png]]
#*[[File:Microsoft Remote Desktop Step 5.png]]
#If it asks to "Accept certificate and connect?", press Connect.

==macOS==
For connecting to Windows client over RDP, we recommend the 'Microsoft Remote Desktop' application. Another, although less preferred, options is the CoRD client.
#Open the 'Microsoft Remote Desktop Application' and select '+ New' to create a new device profile
#Fill in the 'Connection Name' and 'PC Name' fields with the name of the host remote host you wish to connect to. Then close the window.
#*[[File:OSX_MRD_connect.png |300px]]
#You will now see the device listed in the 'My Desktops' section of the 'Microsoft Remote Desktop' Application. Double click it to start the connection.
#*[[File:OSX_MRD_new.png | 300px]]

==UNIX==
===freerdp===
If you are trying to access a Windows host via RDP on a RHEL6 or Ubuntu machine, you should use the rdesktop client from the command line. This should be preinstalled, so there is no configuration that needs to happen.

To use rdesktop, open a shell prompt and type the following command, replacing any $REPLACEME with the requested value.

<pre> rdesktop -r clipboard:CLIPBOARD -g $GEOMETRY -d UMIACS -u $USERNAME $HOSTNAME </pre>

Key:

* <tt>$GEOMETRY</tt>: Percent of remote host's screen to mirror on the client
* <tt>$USERNAME</tt>: Your UMIACS username (Do not include domain name)
* <tt>$HOSTNAME</tt>: Fully Qualified Domain Name (FDQN) of the desired remote host

Once you have connected, you will be directed to a Windows login screen where you can complete the login process.

===xfreerdp===

Xfreerdp is the replacement for rdesktop included with newer Linux hosts, starting with RHEL7 and Ubuntu 12.04/14.04. Xfreerdp also has RHEL6. You should use the xfreerdp client from the command line. This is preinstalled on these newer hosts.

The command for xfreerdp is a bit different than rdesktop. To connect via RDP to a remote host with xfreerdp, type the following command, replacing values as appropriate:

<pre> xfreerdp -d UMIACS -u $USERNAME --plugin cliprdr -g $GEOMETRY $HOSTNAME </pre>

Similar to rdesktop, here is an explanation of the values above:

* <tt>$GEOMETRY</tt>: Percent of remote host's screen to mirror on the client
* <tt>$USERNAME</tt>: Your UMIACS username (Do not include domain name)
* <tt>$HOSTNAME</tt>: Fully Qualified Domain Name (FDQN) of the desired remote host

As with any of these RDP solutions, closing xfreerdp (using the top bar or using CTRL+C) without logging out could cause considerable problems for other users of the workstation. Please be sure to logout after you are finished with the remote machine using the Start menu.

Remote Desktop

2019-02-05T15:06:23Z

Atavakol: /* Windows */

=Introduction=

Remote Desktop allows you to connect to another computer from a network that is compatible. Currently, at UMIACS, this feature is only supported for Windows hosts using the Remote Desktop Protocol (RDP). If you need to remotely connect to a UNIX host, please see [[SecureShell]]. With RDP, you can control your Windows desktop environment through a graphical user interface. Mouse and keyboard movements are transferred over a network to a Windows host running an RDP server, which sends screen refreshes back.

To access an RDP enabled machine, you must be on the UMIACS physical network or [[VPN]]. You must also be authorized to access and remotely control the host you are requesting. If a remote session is active, it is not possible for another user to log onto the console in-person. Attempting to use RDP when a computer is in use by another user could force the existing user to logoff and lose their work. You should always quit RDP by logging off of the remote computer. Simply quitting the RDP client can cause you to stay logged in and prevent other users from accessing the remote host, even at the physical console.

=How to Connect=
*'''Prerequisites:'''
**Connected to the [[VPN | UMIACS VPN]] or be within the UMIACS network border.
**Be a member of the 'Remote Desktop Users' group on the remote machine.
==Windows==
For connecting to Windows client over RDP, we recommend the native Windows 'Remote Desktop Connection' client.

#To start the RDC client, click the "Start'" or "Windows" button on the taskbar. In the menu, navigate to "All Programs," "Accessories," then select "Remote Desktop Connection". Alternatively, you can search for "Remote Desktop Connection" in the Start menu's search field.
#Once RDC client starts, type the name of the RDP/Windows host you are trying to access. The name should be the Fully Qualified Domain Name (FDQN), e.g. "desktop.'''ad.umiacs.umd.edu'''". At this point, click "Connect" to initiate the RDP session.
#*[[File:RemoteDesktop-Connect.png]]
#After the connection is started, a warning message may alert you to an identity verification failure. For UMIACS machines, you can ignore this and proceed by selecting "Yes"
#*[[File:RemoteDesktop-SecurityWarning.jpg]]
#Upon reaching the Windows Security prompt, enter your UMIACS credentials. If the username is either not correct or not the desired account, select "Use another account". Click "Ok" when you are done.
#*[[File:RemoteDesktop-CredentialsPrompt-new.png]]
#You should now be viewing the remote computer. To terminate the session, you should logout of Windows.

Alternatively, you can use the Microsoft Remote Desktop application from the Windows Store, which is available for download [https://www.microsoft.com/en-us/p/microsoft-remote-desktop/9wzdncrfj3ps?activetab=pivot%3Aoverviewtab here.]

#Open Microsoft Remote Desktop.
#Click "Add" in the top right corner.
#*[[File:Microsoft Remote Desktop Step 1.png]]
#Next, click "Desktop - Connect to a PC".
#*[[File:Microsoft Remote Desktop Step 2.png]]
#Type the name of the RDP/Windows host you are trying to access in '''PC Name'''. The name should be the Fully Qualified Domain Name (FDQN), e.g. "desktop.'''ad.umiacs.umd.edu'''". Once you have filled that out, click Save.
#*[[File:Microsoft Remote Desktop Step 3.png]]
#Now, you should be on a page where you will see the PC you have just added. '''Double-click the PC''' and enter your UMIACS credentials. Then, click Connect.
#*[[File:Microsoft Remote Desktop Step 4.png]]
#*[[File:Microsoft Remote Desktop Step 5.png]]
#If it asks to "Accept certificate and connect?", press Connect.

To switch between your current host and the remote host, click the minimize or "-" button on the top connection bar. With RDC, the clipboard can be transferred between the remote and current host while the RDC client is running and logged in.

==macOS==
For connecting to Windows client over RDP, we recommend the 'Microsoft Remote Desktop' application. Another, although less preferred, options is the CoRD client.
#Open the 'Microsoft Remote Desktop Application' and select '+ New' to create a new device profile
#Fill in the 'Connection Name' and 'PC Name' fields with the name of the host remote host you wish to connect to. Then close the window.
#*[[File:OSX_MRD_connect.png |300px]]
#You will now see the device listed in the 'My Desktops' section of the 'Microsoft Remote Desktop' Application. Double click it to start the connection.
#*[[File:OSX_MRD_new.png | 300px]]

==UNIX==
===freerdp===
If you are trying to access a Windows host via RDP on a RHEL6 or Ubuntu machine, you should use the rdesktop client from the command line. This should be preinstalled, so there is no configuration that needs to happen.

To use rdesktop, open a shell prompt and type the following command, replacing any $REPLACEME with the requested value.

<pre> rdesktop -r clipboard:CLIPBOARD -g $GEOMETRY -d UMIACS -u $USERNAME $HOSTNAME </pre>

Key:

* <tt>$GEOMETRY</tt>: Percent of remote host's screen to mirror on the client
* <tt>$USERNAME</tt>: Your UMIACS username (Do not include domain name)
* <tt>$HOSTNAME</tt>: Fully Qualified Domain Name (FDQN) of the desired remote host

Once you have connected, you will be directed to a Windows login screen where you can complete the login process.

===xfreerdp===

Xfreerdp is the replacement for rdesktop included with newer Linux hosts, starting with RHEL7 and Ubuntu 12.04/14.04. Xfreerdp also has RHEL6. You should use the xfreerdp client from the command line. This is preinstalled on these newer hosts.

The command for xfreerdp is a bit different than rdesktop. To connect via RDP to a remote host with xfreerdp, type the following command, replacing values as appropriate:

<pre> xfreerdp -d UMIACS -u $USERNAME --plugin cliprdr -g $GEOMETRY $HOSTNAME </pre>

Similar to rdesktop, here is an explanation of the values above:

* <tt>$GEOMETRY</tt>: Percent of remote host's screen to mirror on the client
* <tt>$USERNAME</tt>: Your UMIACS username (Do not include domain name)
* <tt>$HOSTNAME</tt>: Fully Qualified Domain Name (FDQN) of the desired remote host

As with any of these RDP solutions, closing xfreerdp (using the top bar or using CTRL+C) without logging out could cause considerable problems for other users of the workstation. Please be sure to logout after you are finished with the remote machine using the Start menu.

File:Microsoft Remote Desktop Step 5.png

2019-02-05T14:59:03Z

Atavakol:

File:Microsoft Remote Desktop Step 4.png

2019-02-05T14:56:24Z

Atavakol:

File:Microsoft Remote Desktop Step 3.png

2019-02-05T14:51:44Z

Atavakol:

File:Microsoft Remote Desktop Step 2.png

2019-02-05T14:48:23Z

Atavakol:

File:Microsoft Remote Desktop Step 1.png

2019-02-05T14:46:09Z

Atavakol:

Remote Desktop

2019-02-05T14:37:00Z

Atavakol:

=Introduction=

Remote Desktop allows you to connect to another computer from a network that is compatible. Currently, at UMIACS, this feature is only supported for Windows hosts using the Remote Desktop Protocol (RDP). If you need to remotely connect to a UNIX host, please see [[SecureShell]]. With RDP, you can control your Windows desktop environment through a graphical user interface. Mouse and keyboard movements are transferred over a network to a Windows host running an RDP server, which sends screen refreshes back.

To access an RDP enabled machine, you must be on the UMIACS physical network or [[VPN]]. You must also be authorized to access and remotely control the host you are requesting. If a remote session is active, it is not possible for another user to log onto the console in-person. Attempting to use RDP when a computer is in use by another user could force the existing user to logoff and lose their work. You should always quit RDP by logging off of the remote computer. Simply quitting the RDP client can cause you to stay logged in and prevent other users from accessing the remote host, even at the physical console.

=How to Connect=
*'''Prerequisites:'''
**Connected to the [[VPN | UMIACS VPN]] or be within the UMIACS network border.
**Be a member of the 'Remote Desktop Users' group on the remote machine.
==Windows==
For connecting to Windows client over RDP, we recommend the native Windows 'Remote Desktop Connection' client.

'''If it is not on your computer, please download the Microsoft Remote Desktop application from the Windows Store [https://www.microsoft.com/en-us/p/microsoft-remote-desktop/9wzdncrfj3ps?activetab=pivot%3Aoverviewtab here]'''
#To start the RDC client, click the "Start'" or "Windows" button on the taskbar. In the menu, navigate to "All Programs," "Accessories," then select "Remote Desktop Connection". Alternatively, you can search for "Remote Desktop Connection" in the Start menu's search field.
#Once RDC client starts, type the name of the RDP/Windows host you are trying to access. The name should be the Fully Qualified Domain Name (FDQN), e.g. "desktop.'''ad.umiacs.umd.edu'''". At this point, click "Connect" to initiate the RDP session.
#*[[File:RemoteDesktop-Connect.png]]
#After the connection is started, a warning message may alert you to an identity verification failure. For UMIACS machines, you can ignore this and proceed by selecting "Yes"
#*[[File:RemoteDesktop-SecurityWarning.jpg]]
#Upon reaching the Windows Security prompt, enter your UMIACS credentials. If the username is either not correct or not the desired account, select "Use another account". Click "Ok" when you are done.
#*[[File:RemoteDesktop-CredentialsPrompt-new.png]]
#You should now be viewing the remote computer. To terminate the session, you should logout of Windows.

To switch between your current host and the remote host, click the minimize or "-" button on the top connection bar. With RDC, the clipboard can be transferred between the remote and current host while the RDC client is running and logged in.

==macOS==
For connecting to Windows client over RDP, we recommend the 'Microsoft Remote Desktop' application. Another, although less preferred, options is the CoRD client.
#Open the 'Microsoft Remote Desktop Application' and select '+ New' to create a new device profile
#Fill in the 'Connection Name' and 'PC Name' fields with the name of the host remote host you wish to connect to. Then close the window.
#*[[File:OSX_MRD_connect.png |300px]]
#You will now see the device listed in the 'My Desktops' section of the 'Microsoft Remote Desktop' Application. Double click it to start the connection.
#*[[File:OSX_MRD_new.png | 300px]]

==UNIX==
===freerdp===
If you are trying to access a Windows host via RDP on a RHEL6 or Ubuntu machine, you should use the rdesktop client from the command line. This should be preinstalled, so there is no configuration that needs to happen.

To use rdesktop, open a shell prompt and type the following command, replacing any $REPLACEME with the requested value.

<pre> rdesktop -r clipboard:CLIPBOARD -g $GEOMETRY -d UMIACS -u $USERNAME $HOSTNAME </pre>

Key:

* <tt>$GEOMETRY</tt>: Percent of remote host's screen to mirror on the client
* <tt>$USERNAME</tt>: Your UMIACS username (Do not include domain name)
* <tt>$HOSTNAME</tt>: Fully Qualified Domain Name (FDQN) of the desired remote host

Once you have connected, you will be directed to a Windows login screen where you can complete the login process.

===xfreerdp===

Xfreerdp is the replacement for rdesktop included with newer Linux hosts, starting with RHEL7 and Ubuntu 12.04/14.04. Xfreerdp also has RHEL6. You should use the xfreerdp client from the command line. This is preinstalled on these newer hosts.

The command for xfreerdp is a bit different than rdesktop. To connect via RDP to a remote host with xfreerdp, type the following command, replacing values as appropriate:

<pre> xfreerdp -d UMIACS -u $USERNAME --plugin cliprdr -g $GEOMETRY $HOSTNAME </pre>

Similar to rdesktop, here is an explanation of the values above:

* <tt>$GEOMETRY</tt>: Percent of remote host's screen to mirror on the client
* <tt>$USERNAME</tt>: Your UMIACS username (Do not include domain name)
* <tt>$HOSTNAME</tt>: Fully Qualified Domain Name (FDQN) of the desired remote host

As with any of these RDP solutions, closing xfreerdp (using the top bar or using CTRL+C) without logging out could cause considerable problems for other users of the workstation. Please be sure to logout after you are finished with the remote machine using the Start menu.

WebSpace

2018-09-07T17:41:09Z

Atavakol: /* Hosting websites in UMIACS Object Store (preferred method) */

UMIACS provides web space hosting for research/lab pages and user pages.

== '''Hosting websites in UMIACS Object Store ''(preferred method)''''' ==
Please refer to the [https://obj.umiacs.umd.edu/obj/help UMIACS Object Store Help Page] for details on hosting a website in the UMIACS Object Store. This is currently our most updated and reliable method for hosting websites.

==Main Website and Lab Pages==

<pre>http://www.umiacs.umd.edu</pre>

Users can access the main website and lab sites for editing in two ways:
* From Unix as /fs/www - and can be remotely accessed by [[SFTP]] to a supported Unix host (eg. [[OpenLAB]])
* From Windows as \\fluidfs.ad.umiacs.umd.edu\www-umiacs - and remotely accessed by the same file share over the [[VPN]]

Faculty members and authorized users can modify their own public profiles on the main UMIACS homepage. For instructions, see [[ContentManagement]].

==Personal Web Space==

<pre>http://www.umiacs.umd.edu/~username</pre>

Users can access their website for editing two ways:

* From Unix as /fs/www-users/username - and can be remotely accessed via [[SFTP]] to a supported UNIX host (eg. [[OpenLAB]])
* From Windows as \\fluidfs.ad.umiacs.umd.edu\www-users\username - and remotely accessed by the same file share over the [[VPN]]

In general, large datasets related to a Labs research should go into the specific lab's web tree, not the individual users. Remember that users' webpage is not permanently maintained once the user leaves UMIACS.

==Adding A Password Protected Folder To Your Web Space==

1) Create the directory you want to password protect or <tt>cd</tt> into the directory you want to password protect

2) Create a file called ''.htaccess'' (<tt> vi .htaccess</tt>) in the directory you wish to password protect.

3) In the file you just created type the following lines

<pre>
AuthUserFile "/your/directory/here/".htpasswd
AuthName "Secure Document"
AuthType Basic
require user username
</pre>

For example, if you were going to protect the <tt>/fs/www-users/username/private</tt> directory and you want the required name to be <tt>class239</tt>, then your file would look like this:
<pre>
AuthUserFile /fs/www-users/username/private/.htpasswd
AuthName "Secure Document"
AuthType Basic
require user class239
</pre>

4) Create a file called ''.htpasswd'' in the same directory as ''.htaccess''. You create this file by typing in <tt>htpasswd -c .htpasswd ''username''</tt> in the directory area to be protected.

In the example above, the username is <tt>class239</tt> so you would type <tt>htpasswd -c .htpasswd class239</tt>

You will be prompted to enter the password you want. The ''.htpasswd'' file will be created in the current directory and will contain an encrypted version of the password.

To later change the username, edit the ''.htaccess'' file and change the username. If you want to later change the password, just retype the above line in step 4 and enter the new password at the prompt.

==Restricting Content based on IP address==
It is possible to have pages on your webspace only accessible to clients connecting from certain IP addresses. In order to accomplish this, cd in to the directory you wish to restrict, and edit your ''.htaccess'' or ''httpd.conf'' file. The example below shows how to make content only viewable to clients connecting from the UMD wifi in Apache 2.2.

<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">SetEnvIF X-Forwarded-For "^128\.8\.\d+\.\d+$" UMD_NETWORK
SetEnvIF X-Forwarded-For "^129\.2\.\d+\.\d+$" UMD_NETWORK
SetEnvIF X-Forwarded-For "^192\.168\.\d+\.\d+$" UMD_NETWORK
SetEnvIF X-Forwarded-For "^206\.196\.(?:1[6-9][0-9]|2[0-5][0-9])\.\d+$" UMD_NETWORK
SetEnvIF X-Forwarded-For "^10\.\d+\.\d+\.\d+$" UMD_NETWORK
Order Deny,Allow
Deny from all
Allow from env=UMD_NETWORK
</pre>

The SetEnvIF directive will modify one's environment if the specified attribute matches the provided regular expression. In this example, IP addresses that are forwarded from an IP within UMD's IP space are tagged with UMD_NETWORK. Then, all traffic to the example directory is blocked unless it has the UMD_NETWORK tag. See the following pages for a more in depth explanation of the commands used.

[https://httpd.apache.org/docs/2.2/howto/htaccess.html .htaccess], [https://httpd.apache.org/docs/2.2/mod/mod_setenvif.html#setenvif SetEnvIf], [https://httpd.apache.org/docs/2.2/mod/mod_authz_host.html#order Order], [https://httpd.apache.org/docs/2.2/mod/mod_authz_host.html#deny Deny], [https://httpd.apache.org/docs/2.2/mod/mod_authz_host.html#allow Allow]

WebSpace

2018-09-07T17:39:02Z

Atavakol:

UMIACS provides web space hosting for research/lab pages and user pages.

== '''Hosting websites in UMIACS Object Store ''(preferred method)''''' ==
Please refer to the [https://obj.umiacs.umd.edu/obj/help | UMIACS Object Store Help Page] for details on hosting a website in the UMIACS Object Store. This is currently our most updated and reliable method for hosting websites.

==Main Website and Lab Pages==

<pre>http://www.umiacs.umd.edu</pre>

Users can access the main website and lab sites for editing in two ways:
* From Unix as /fs/www - and can be remotely accessed by [[SFTP]] to a supported Unix host (eg. [[OpenLAB]])
* From Windows as \\fluidfs.ad.umiacs.umd.edu\www-umiacs - and remotely accessed by the same file share over the [[VPN]]

Faculty members and authorized users can modify their own public profiles on the main UMIACS homepage. For instructions, see [[ContentManagement]].

==Personal Web Space==

<pre>http://www.umiacs.umd.edu/~username</pre>

Users can access their website for editing two ways:

* From Unix as /fs/www-users/username - and can be remotely accessed via [[SFTP]] to a supported UNIX host (eg. [[OpenLAB]])
* From Windows as \\fluidfs.ad.umiacs.umd.edu\www-users\username - and remotely accessed by the same file share over the [[VPN]]

In general, large datasets related to a Labs research should go into the specific lab's web tree, not the individual users. Remember that users' webpage is not permanently maintained once the user leaves UMIACS.

==Adding A Password Protected Folder To Your Web Space==

1) Create the directory you want to password protect or <tt>cd</tt> into the directory you want to password protect

2) Create a file called ''.htaccess'' (<tt> vi .htaccess</tt>) in the directory you wish to password protect.

3) In the file you just created type the following lines

<pre>
AuthUserFile "/your/directory/here/".htpasswd
AuthName "Secure Document"
AuthType Basic
require user username
</pre>

For example, if you were going to protect the <tt>/fs/www-users/username/private</tt> directory and you want the required name to be <tt>class239</tt>, then your file would look like this:
<pre>
AuthUserFile /fs/www-users/username/private/.htpasswd
AuthName "Secure Document"
AuthType Basic
require user class239
</pre>

4) Create a file called ''.htpasswd'' in the same directory as ''.htaccess''. You create this file by typing in <tt>htpasswd -c .htpasswd ''username''</tt> in the directory area to be protected.

In the example above, the username is <tt>class239</tt> so you would type <tt>htpasswd -c .htpasswd class239</tt>

You will be prompted to enter the password you want. The ''.htpasswd'' file will be created in the current directory and will contain an encrypted version of the password.

To later change the username, edit the ''.htaccess'' file and change the username. If you want to later change the password, just retype the above line in step 4 and enter the new password at the prompt.

==Restricting Content based on IP address==
It is possible to have pages on your webspace only accessible to clients connecting from certain IP addresses. In order to accomplish this, cd in to the directory you wish to restrict, and edit your ''.htaccess'' or ''httpd.conf'' file. The example below shows how to make content only viewable to clients connecting from the UMD wifi in Apache 2.2.

<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">SetEnvIF X-Forwarded-For "^128\.8\.\d+\.\d+$" UMD_NETWORK
SetEnvIF X-Forwarded-For "^129\.2\.\d+\.\d+$" UMD_NETWORK
SetEnvIF X-Forwarded-For "^192\.168\.\d+\.\d+$" UMD_NETWORK
SetEnvIF X-Forwarded-For "^206\.196\.(?:1[6-9][0-9]|2[0-5][0-9])\.\d+$" UMD_NETWORK
SetEnvIF X-Forwarded-For "^10\.\d+\.\d+\.\d+$" UMD_NETWORK
Order Deny,Allow
Deny from all
Allow from env=UMD_NETWORK
</pre>

The SetEnvIF directive will modify one's environment if the specified attribute matches the provided regular expression. In this example, IP addresses that are forwarded from an IP within UMD's IP space are tagged with UMD_NETWORK. Then, all traffic to the example directory is blocked unless it has the UMD_NETWORK tag. See the following pages for a more in depth explanation of the commands used.

[https://httpd.apache.org/docs/2.2/howto/htaccess.html .htaccess], [https://httpd.apache.org/docs/2.2/mod/mod_setenvif.html#setenvif SetEnvIf], [https://httpd.apache.org/docs/2.2/mod/mod_authz_host.html#order Order], [https://httpd.apache.org/docs/2.2/mod/mod_authz_host.html#deny Deny], [https://httpd.apache.org/docs/2.2/mod/mod_authz_host.html#allow Allow]

WebSpace

2018-09-07T17:38:27Z

Atavakol:

UMIACS provides web space hosting for research/lab pages and user pages.

== Hosting websites in UMIACS Object Store (preferred method) ==
Please refer to the [https://obj.umiacs.umd.edu/obj/help | UMIACS Object Store Help Page] for details on hosting a website in the UMIACS Object Store. This is currently our most updated and reliable method for hosting websites.

==Main Website and Lab Pages==

<pre>http://www.umiacs.umd.edu</pre>

Users can access the main website and lab sites for editing in two ways:
* From Unix as /fs/www - and can be remotely accessed by [[SFTP]] to a supported Unix host (eg. [[OpenLAB]])
* From Windows as \\fluidfs.ad.umiacs.umd.edu\www-umiacs - and remotely accessed by the same file share over the [[VPN]]

Faculty members and authorized users can modify their own public profiles on the main UMIACS homepage. For instructions, see [[ContentManagement]].

==Personal Web Space==

<pre>http://www.umiacs.umd.edu/~username</pre>

Users can access their website for editing two ways:

* From Unix as /fs/www-users/username - and can be remotely accessed via [[SFTP]] to a supported UNIX host (eg. [[OpenLAB]])
* From Windows as \\fluidfs.ad.umiacs.umd.edu\www-users\username - and remotely accessed by the same file share over the [[VPN]]

In general, large datasets related to a Labs research should go into the specific lab's web tree, not the individual users. Remember that users' webpage is not permanently maintained once the user leaves UMIACS.

==Adding A Password Protected Folder To Your Web Space==

1) Create the directory you want to password protect or <tt>cd</tt> into the directory you want to password protect

2) Create a file called ''.htaccess'' (<tt> vi .htaccess</tt>) in the directory you wish to password protect.

3) In the file you just created type the following lines

<pre>
AuthUserFile "/your/directory/here/".htpasswd
AuthName "Secure Document"
AuthType Basic
require user username
</pre>

For example, if you were going to protect the <tt>/fs/www-users/username/private</tt> directory and you want the required name to be <tt>class239</tt>, then your file would look like this:
<pre>
AuthUserFile /fs/www-users/username/private/.htpasswd
AuthName "Secure Document"
AuthType Basic
require user class239
</pre>

4) Create a file called ''.htpasswd'' in the same directory as ''.htaccess''. You create this file by typing in <tt>htpasswd -c .htpasswd ''username''</tt> in the directory area to be protected.

In the example above, the username is <tt>class239</tt> so you would type <tt>htpasswd -c .htpasswd class239</tt>

You will be prompted to enter the password you want. The ''.htpasswd'' file will be created in the current directory and will contain an encrypted version of the password.

To later change the username, edit the ''.htaccess'' file and change the username. If you want to later change the password, just retype the above line in step 4 and enter the new password at the prompt.

==Restricting Content based on IP address==
It is possible to have pages on your webspace only accessible to clients connecting from certain IP addresses. In order to accomplish this, cd in to the directory you wish to restrict, and edit your ''.htaccess'' or ''httpd.conf'' file. The example below shows how to make content only viewable to clients connecting from the UMD wifi in Apache 2.2.

<pre style="white-space: pre-wrap;
white-space: -moz-pre-wrap;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;">SetEnvIF X-Forwarded-For "^128\.8\.\d+\.\d+$" UMD_NETWORK
SetEnvIF X-Forwarded-For "^129\.2\.\d+\.\d+$" UMD_NETWORK
SetEnvIF X-Forwarded-For "^192\.168\.\d+\.\d+$" UMD_NETWORK
SetEnvIF X-Forwarded-For "^206\.196\.(?:1[6-9][0-9]|2[0-5][0-9])\.\d+$" UMD_NETWORK
SetEnvIF X-Forwarded-For "^10\.\d+\.\d+\.\d+$" UMD_NETWORK
Order Deny,Allow
Deny from all
Allow from env=UMD_NETWORK
</pre>

The SetEnvIF directive will modify one's environment if the specified attribute matches the provided regular expression. In this example, IP addresses that are forwarded from an IP within UMD's IP space are tagged with UMD_NETWORK. Then, all traffic to the example directory is blocked unless it has the UMD_NETWORK tag. See the following pages for a more in depth explanation of the commands used.

[https://httpd.apache.org/docs/2.2/howto/htaccess.html .htaccess], [https://httpd.apache.org/docs/2.2/mod/mod_setenvif.html#setenvif SetEnvIf], [https://httpd.apache.org/docs/2.2/mod/mod_authz_host.html#order Order], [https://httpd.apache.org/docs/2.2/mod/mod_authz_host.html#deny Deny], [https://httpd.apache.org/docs/2.2/mod/mod_authz_host.html#allow Allow]

File:WindowsMailApp6.png

2018-06-26T23:16:01Z

Atavakol:

File:WindowsMailApp5.png

2018-06-26T23:13:52Z

Atavakol:

File:WindowsMailApp4.png

2018-06-26T23:11:46Z

Atavakol:

File:WindowsMailApp3.png

2018-06-26T23:10:33Z

Atavakol:

File:WindowsMailApp2.png

2018-06-26T23:09:24Z

Atavakol:

File:WindowsMailApp1.png

2018-06-26T23:03:06Z

Atavakol: