Resources

CEU

DPHPC

School

University

Footnotes

  1. Network drives

    U:>net use

    New connections will be remembered.

     Status       Local     Remote                    Network

 -------------------------------------------------------------------------------
 OK           K:        \\me-stata3\stata14       Microsoft Windows Network
 OK           L:        \\me-stata3\stata15       Microsoft Windows Network
              S:        \\me-filer1\groups$\MGEU\Factors\High_dimensional_genetics\Olink\INF1
                                                  Microsoft Windows Network
              U:        \\me-filer1.medschl.cam.ac.uk\home$\jhz22
                                                  Microsoft Windows Network
              V:        \\ME-FILER1\GROUPS$\MEU   Microsoft Windows Network
              W:        \\ME-FILER1\GROUPS$\MGEU  Microsoft Windows Network
              X:        \\me-filer1\groups3$\CEU-Biobank data
                                             Microsoft Windows Network
 The command completed successfully.

    The user profile is available from \\me-filer2.medschl.cam.ac.uk\profiles$\CRSid.v#, and is again handy to map it to a drive, e.g., via MS-DOS,

    net use Z: \me-filer2.medschl.cam.ac.uk\profiles$\CRSid.v#

    The AppData/Roaming directory can be used when appropriate. In case of error(s), a run as administrator from a cmd session with sfc/scannow to fix.

    ↩

  2. An example output from getmac -v.

     U:\>getmac -v

 Connection Name Network Adapter Physical Address    Transport Name
 =============== =============== =================== ==========================================================
 vEthernet (nat) Hyper-V Virtual 00-15-5D-23-52-3D   \Device\Tcpip_{1B4E8617-BC29-4833-A456-C0C64A493AFE}
 VirtualBox Host VirtualBox Host 0A-00-27-00-00-0B   \Device\Tcpip_{53CCE470-7C3C-40AB-91B0-A892285AA122}
 Ethernet 2      TAP-Windows Ada 00-FF-DF-42-55-EB   Media disconnected
 vEthernet (Defa Hyper-V Virtual 00-15-5D-25-8F-34   \Device\Tcpip_{79500A5B-7A98-4CAC-8879-4439AD68046C}
 Ethernet        Intel(R) Ethern 54-BF-64-81-E7-29   \Device\Tcpip_{29441362-9902-493B-A2DE-BAF0BC3FB153}

    In this case, the last line is what is needed.

    ↩

  3. To check for the active status, ping from a CLI (Linux/Windows MS-DOS prompt, invoke with Windows key + r, type in "cmd" in the box and hit the return key) and issue

    ping CMPCxxx.medschl.private.cam.ac.uk

    where (xxx is the serial number, e.g., 357, on the desktop at the office). Equivalently, one can use ping 172.27.11.159. The IP address is also the one in the remote desktop connection dialog box. It appears helpful when the computer is restarted for updates.

     Pinging CMPC357.medschl.private.cam.ac.uk [172.27.11.159] with 32 bytes of data:
 Reply from 172.27.11.159: bytes=32 time=16ms TTL=127
 Reply from 172.27.11.159: bytes=32 time=16ms TTL=127
 Reply from 172.27.11.159: bytes=32 time=16ms TTL=127
 Reply from 172.27.11.159: bytes=32 time=24ms TTL=127

 Ping statistics for 172.27.11.159:
      Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
 Approximate round trip times in milli-seconds:
      Minimum = 16ms, Maximum = 24ms, Average = 18ms

    However, the following message shows that the computer is down.

     Pinging 172.27.11.159 with 32 bytes of data:
 Request timed out.
 Request timed out.
 Request timed out.
 Request timed out.
 Ping statistics for 172.27.11.159:
      Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

    ↩