skip to content
 

In most cases UMD devices will work on wireless networks, such as eduroam or a wired connection. Usually your own network, either via UDN wide private addressing or local addressing, is adequate providing network settings are assigned by DHCP and clients have internet access.

If you do not have an adequate subnet for UMD devices, please contact UIS Network Systems to request new network services ahead of any migrations. In most cases this will involve a new subnet, and depending on your UDN connection type and configuration, it will involve a change of routing or creation of a new VLAN. You can find more information on typical UDN connections and VLAN services.

If you are migrating from the MCS to the UMD please see the information at the bottom of this page.

UMD device setup 

In order to setup a UMD device you need to be connected to a suitable network. After the device has been configured then other networks can be used. 

Windows 

Single-user 

  • An internet connection (home or office)

Shared-use 

  • UDN connection via ethernet

macOS 

Single-user 

  • Any ethernet connection (adapter may be required) 
  • WPA2 Wi-Fi connection (e.g. home Wi-Fi)
  • UniofCam-IoT 

Shared-use 

  • UDN connection via ethernet 

 

Firewall Rules 

If an institutional firewall is in place, then rules may need to be amended to comply with these requirements. 

Windows 

  • All outbound traffic 

macOS 

No unsolicited inbound connections are required however opening up optional ports may make troubleshooting by UIS easier. 172.16.32.0/23 is the UIS staff network. 

  • All outbound traffic (required) 
  • Inbound to 22/tcp from 172.16.32.0/23 (ssh) (optional) 
  • Inbound to 3283/tcp & udp from 172.16.32.0/23 (ARD) (optional) 
  • Inbound to 5900/tcp & udp from 172.16.32.0/23 (ARD) (optional) 

 

MCS network migration

MCS devices require the use of an MCS network (VLAN and specific subnet) which is managed by UIS. These networks are being withdrawn as the MCS is wound down. UMD devices will not work on MCS VLANs as they will not attain network settings through the MCS DHCP servers. 

DHCP for UDN wide private addressing can be provided by your own DHCP service. If you do not have a local DHCP service UIS can provide this, more information can be found here: https://www.dns.cam.ac.uk/ipreg/dhcp.html