Notes on \\numiwinctr & \\numiserver1

jump ahead to menu

\\numiwinctr1 has been replaced by \\numiwinctr

\\numiwinctr1 has been replaced by a newer machine, named \\numiwinctr. This machine is running newer software & the desktop now resembles that one gets when running Windows NT4 (or Windows 95). The older machine is going to have a second life at the Sudan mine in Minnesota--as of the June, 2000 Minos Ely meeting.

Unchanged are user account names and passwords, as well as user files on the local disk. The local disks cannot be viewed in their entirety from Windows Explorer; this is a purposeful decision by Michael Li. Only the user areas and the Pcapps area on the local disk can be viewed. Unlike the older machine, users will be able to use Windows Internet Explorer on this machine. This is another of Michael's decisions. Like the older machine, MacIntosh service is disabled on this machine. Macs can access files on \\numiserver1. The disk(s) on \\numiserver1 can be network attached (for the current login session or at each login) to \\numiwinctr (or a Mac or any other Windows NT machine & probably any machine running Windows 95 or 98 on the network). To do a network attachment on \\numiwinctr do a right mouse click on the "My Computer" icon on the desktop.

There is a windowing FTP client available on \\numiwinctr (just as there was on the older machine). If it doesn't appear in your list of programs, ask Andy to activate it for you (he has to manually modify the profile for existing users).

When you network attach "\\numiserver1\Share" it has a drive letter on \\numiwinctr that is assigned to it (probably H:\). In the windowing FTP client you can change from drive letter W:\ to H:\ by using the "Chge Dir" button.

This document has been extensively modified--to update it to reflect the new machine. Please point out any remaining problems to (Alan Wehmann).


The following notes on the use of \\numiwinctr & \\numiserver1 are based upon e-mail exchanges, telephone conversations, and conversations in person with Michael Li. They are also based upon actual usage of both systems.

To use \\numiwinctr from the FNALU cluster:

rsh numiwinctr wincenter -display your_proper_screen

You can find out the value of "your_proper_screen" by using the command "echo $DISPLAY".

Michael stated that the command to start it on a X-terminal is : < rsh numiwinctr wincenter -display < your terminal name:0.0 >   >  . Tom Chase's experience on 8/31/98 was that he had to first say "xhost +" on his UM Unix box.

Direct Login from X Windows Terminal

Alternatively, one can choose "login" from the menu on a X-terminal that one gets by mouse clicking on a clear part of the screen and connect directly to, without first logging into a Unix box and using "rsh". Logging in directly clearly uses less resources.

Users trying to log in into \\numiwinctr from remote (i.e. not at Fermilab) X-Windows terminals may have to use the following construct as their username: "fnal\username". Surrounding parentheses may or may not be necessary (see remarks under FTP notes). You have to change your password when you login for the first time.


If you forget your password and make several unsuccessful tries at logging in while trying to remember it, you may eventually be told that you are locked out. This is a temporary situation that is cured by waiting long enough, so that the time-out clears itself. Several minutes should suffice, but I've forgotten what the exact number is.

Password Change

If your password (FNAL Windows NT domain) has expired, the way to change it is to try logging into \\numiwinctr from a X-Windows terminal, an X-Windows Emulator (see instructions for the Exceed X-Start Client), or an ICA client (see below). You will be presented with a window that asks for a new password. See the other notes below.

If your password hasn't expired and you wish to change it, log into \\numiwinctr, go to the Start Menu at the bottom left of the screen (pops up if not visible), choose "Windows NT Security", and you will have a choice to change your password. Users accessing \\numiwinctr from a PC running Windows NT (or Windows 95 or Windows 98) will have to be careful to get the right Start Menu (the wrong one would be the one on the local machine, which probably wouldn't have the FNAL domain as a choice of domain).

Files on \\numiwinctr get backed up every night.

System Manager

Andy Lego is the system manager; his e-mail address is "". His telephone extension at Fermilab is X2961 . He is the person who can add new users.

Andy's on-site pager # is 0758.

As of 7/2/01 Chris Brew will be the System Manager. His email address is ""; his Fermilab extension is X5216.

Descriptionn of \\numiwinctr

\\NUMIWINCTR is running MS Windows NT 4.

Accounts on FNAL domain

The use of NUMIWINCTR requires a dedicated account in the Windows NT FNAL domain. Creation of such accounts is done by Andy Lego or Andy Romero or Tim Doody. Users already having Windows NT machines will find it necessary to have a separate account to run NUMIWINCTR applications or access the NUMIWINCTR disks (see remarks on usage of \\numiserver1 from Windows NT machines).

Local Drives on \\numiwinctr

In my \\numiwinctr session I have the local drive letters U and W. The W drive points to \\numiwinctr\numiuser\wehmann, but is not a network connection (it is some sort of substitution slight of hand). The U drive points to \\numiwinctr\numiuser and is a network connection. Each user should have the equivalent of these two drives. In Windows NT explorer, use of the W drive button does not let you see or revise Security, Permissions.

Shortcuts and Starting Directory

A Shortcut to an application has an option "Start In", where you can specify your own start directory. For some applications you can customize them by copying a customization file to a directory for which you have write access, and then you can point to this directory with the "Start In" option in the Shortcut. An example is MS Project 98. The file "Global.mpt" is the customization file.

Description of \\numiserver1

\\NUMISERVER1 is a server machine running MS Windows NT 4. It can be used as a file server for desktop Macs, PCs, as well as serving files to \\numiwinctr. Both machines reside on the FNAL domain. Usernames and passwords on other domains at Fermilab (such as BEAMS) will not work on either machine. Instructions for attaching \\numiserver1 folders to \\numiwinctr are given later.

ICA Clients are available for machines running MS-DOS, MS Windows 3.1, and MS Windows Nt. They are also available for Macintosh machines. They can be downloaded from WinFrame.

The installer for the ICA client suitable for MS Windows NT has been downloaded and put at the location \\beamssrv1\\public\ica32.exe. For Windows NT users in the BEAMS domain, \\beamssrv1\ is automatically network mapped to your machine as the Y drive by the login script.

Networked disk connection

NUMISERVER1 disk areas can be reached from NUMIWINCTR by using the Windows Explorer, choosing the "My Computer" icon, clicking on the right mouse button, and then choosing from the context menu "Map Network Drive", "Microsoft Windows Network", "FNAL", "NUMISERVER1". Then "Share" can be chosen for shared files. There is a box labelled "Reconnect at logon" that should be checked, if this isn't to be a connection only for one logon session. Doing this once is sufficient to add an appropriate disk letter icon to Windows Explorer. The attachment of a network drive in this manner is "sticky", which means that the process doesn't have to be repeated each session. Network-attached drives also becomes visible to applications such as MS Word 7.

The \\numiserver1\USERS drive is meant for personal use; this area should be used for personal files, rather than having personal folders on \\numiserver1\Share. If you don't see a personal folder there, contact either Andy Lego or me (Alan Wehmann) to set one up. Any of the \\numiserver1 disk ares will be visible on a Mac, via use of the Mac Chooser. \\numiserver1 has Mac service running on it.

More on \\numiserver1

There is also a "Public" area on \\numiserver1, which is readable by anyone possessing a valid username and password on the Windows NT FNAL domain. Such users do not need to belong to one of the groups with permission to use the "Share" area. The groups of interest are "NUMI_USERS", and other such descriptors. Anyone outside one of these groups automatically allowed to use the Share folder on \\numiserver1, can be given access to Share by petitioning Andy Lego. One's username will then be given "RX" access to the Share folder. Once that access is given, access can be given to lower level folders and files as needed.

Numiserver1 from a Mac

\\numiserver1 can be reached from Macs by using the Mac Chooser, Appleshare, PPD/MAIN ETHERNET, NUMISERVER1, and then the folder of choice. The default use of the Chooser only allows an eight character password. There is a utility available which relaxes this limit (except if you want to change your password from the Chooser). \\numiserver1 knows about Mac file oddities, and allows for Mac storage and usage of files.

The provision for Mac file service from \\numiserver1 may change if and when the operating system on that machine is upgraded from Windows NT4 to Windows 2000. Read the Computing Division's 1/24/01 announcement and crystal-ball gaze into the future.

The utility for having longer passwords with the Chooser has the name "VMS UAM". It wants to be placed in a folder named "AppleShare Folder", which, in turn, lives in the System Folder. This utility is known to work with System 7.5 and 7.6; it may work with System 8, but there isn't an existence proof known to me. The utility may be found on the server "DCD\MAIN ETHERNET\PCKITS\DeskTop Tools\Mac Tools\UAM".

You can make an "alias" to preserve knowledge of this connection. In a later session you can use the alias to establish the connection. All you need supply in that case is the password.

It is not recommended to request automatic login for a server connection when using the Mac chooser. Nancy Grossman was doing this with one of the ES&H servers & was having problems as a result. Ask Nancy for more details.

Under fault conditions it is possible not to see one or more of the folders on a \\numiserver1 disk drive, on the Mac desktop. In this case call Andy Lego.

Numiserver1 from NT machines

\\numiserver1 can be reached from Windows NT machines, from the "My Network Neighborhood" icon, or by using the Windows NT Explorer. [In fact, a right button click of the mouse on "My Computer" will bring up a window that will allow a network drive connection.] As indicated earlier, the username used to make such a network drive connection must belong to the FNAL domain--even if one only wishes to access the "Public" folder. For some with existing usernames belonging to other domains (e.g. Beams Division), this will necessitate requesting and getting another username (which belongs to the FNAL domain). The sequence necessary to add \\numiserver drives to Windows NT machines is similar to the instructions already given for attaching a network drive to \\numiwinctr.

In the case of attempting to map a network drive from the FNAL domain (e.g. one of the folders on \\numiserver1) to a machine in another domain (e.g. BEAMS), the user must use his or her username and password for an account in the FNAL domain. The username should be preceded by the domain name in this case (e.g. fnal\wehmann). This goes in the form where it says "connect as". The folder names on \\numiserver1 are "Share", "Public", "USERS", "PCAPPS", "TEMP", "clients", "Scripts", & "Profile".

If this is the first use of a newly created username and password, there is a "Catch 22" involved. It will tell you that the password has to be changed, but it offers no ready way to change it. One solution is to go to a X-Windows terminal temporarily, log in to \\numiwinctr, and change to another password in that manner. This works even if one doesn't normally use \\numiwinctr and one doesn't have personal directories on that machine (technical term--lack of a "profile"). A password 8 or fewer characters is advisable, since I believe that the window accessing a Network Drive has that limitation for the password. If the Windows NT machine is not in the FNAL domain, then the username for the attachment of a \\numiserver1 drive becomes "fnal\username" (this indicates that the username belongs to the FNAL domain).

Another solution is to use an X Windows server running on the local PC (e.g. eXceed) or Mac (e.g. eXodus). One can log-in to \\numiwinctr as explained below and change the password.

A third solution is to use a Mac or Windows ICA client on the local machine to log into \\numiwinctr. As stated in the previous paragraph one doesn't need a \\numiwinctr "profile" to do this.

A similar situation occurs when one's password expires. One must then repeat the steps of the previous three paragraphs, in order to change the password. The system won't allow you to reuse old passwords. See also these other notes.

Initial login

One new user wanting to connect to \\numiserver1 from a Windows NT machine in the Beams Domain had available the X windows emulator "eXceed" for changing his initial password. In this case (or in the case of "eXodus" on the Mac) the command to be used (in the Client Editor) is "wincenter -display $$ME$$". The construct "$$ME$$" works for "eXodus"; for "eXceed" one puts in what "eXceed" needs to refer to the local display (see eXceed parameters below). The command processor choice is "RSH". The host is "" (from the lab, this can simply be "numiwinctr"). When one gets to the login screen for \\numwinctr1 the username to insert does not need "FNAL\" ahead of it, since the login screen has FNAL for the second field. The third field is the password. For the first time login, one is forced to change the password. After that, one can access \\numiserver1 directly from a Windows NT machine--as discussed above.

With eXceed on a Windows NT machine one can use the Xstart icon and use the Xstart Client Startup Application. The start method should be RSH. The Program Type is XWindow. The Host is (at Fermilab "numiwinctr" should suffice). Host Type need not be specified. The Command should be "wincenter -display @d&;". As explained in the previous paragraph, do not put "fnal\" ahead of the user name, since it is unnecessary.

File Permissions

When one creates a file/directory, one is the owner of the object. One may need to change the permission of the object to enable/disable others for access to it (see also remarks about the public area). I have been able to create a folder (sub-directory) in the SHARE area from my Mac (and create files there). New sub-directories can also be created from the Windows Explorer on NUMIWINCTR. It is worth checking the sub-directory/file access permissions with the Windows Explorer, to see if they accord with your wishes or pre-conceptions.

MS Word needs more than "Add & Read" access to a directory to create a new file. "Add" allows a user to add a file to a directory, but doesn't allow one to change it. "Change" allows one to delete a file, as well as write and execute it. MS Word first writes a zero-length file and then fills it in. This appears to require "Change" access, since one is effectively deleting the file and then writing it (there is also a temporary file involved in this process that eventually gets deleted). Other applications--such as MS Excel--probably behave in a similar fashion.

One could get around the limitation mentioned in the previous paragraph by having MS Word write to a folder where one had "Change" permission and later copy that file (with Windows Explorer) to the folder where one only has "Add & Read" permission.

Each \\numiwinctr user has his own area on NUMIWINCTR. That is where he should save his own documents. Files get backed up daily.

There is a shared area on NUMIWINCTR, which is analagous to the shared area on NUMISERVER1. It is "\\numiwinctr\temp", I believe. It will have a drive letter associated with it. I added SHARE as a sub-directory.

It is possible to "take ownership" of a file if one has "Full Control" over it. In File Manager there is a menu tab "Security". Under this there is a tab labelled "Permissions" and another labelled something like "Owner". The latter allows one to take ownership of a file.

An example where this might be appropriate is on \\numiwinctr\USERS. This is an area Michael Li created for people who are using \\numiwinctr, but who aren't using \\numiwinctr. However, I asked him for the ability to make sub-directories there for people who are also using \\numiwinctr. This allows them to move files there from \\numiserver1\Share, so that folder isn't so cluttered with personal areas. Since I create the sub-directories for such users and then give them Full Control over the sub-directory, they should seriously consider taking ownership of the sub-directory away from me--in order to keep things private.

Remarks on software

MS Project 98 is available on \\numiwinctr. There are five licenses (so there can be five simultaneous users). The working directory should be one's home directory. One can keep a local copy of "global.mpt" there.

Ghostview and Ghostscript are also present on the system.

Mac notes

Before reading what is below, it is suggested that you first read the entry under "mac_client". The notes below assume the use of an X-Windows emulator. With the advent of the Mac client software, this may no longer be advisable.

NUMIWINCTR can be accessed from a MacIntosh by using a X Windows Server emulator, like MacX or eXodus. In my experience eXodus is superior to MacX, because the cursor inside a MS Word document is more visible against the background. A company named Xoftware also markets a X Windows Server emulator for the MacIntosh. My experience with their product was not a good one. It is often confused with MacX, because I think they had an agreement with Apple for a while to describe it as the descendant of MacX. Configuration instructions for Mac X are given in Macintosh Remote Access. Configuration for "eXodus" is somewhat different, but comparable.

The Beams Division is not yet supporting eXodus in the same way that the Particle Physics Division is supporting it. The Beams Division people who support MacIntosh usage may still have left individual copies of the latest version of MacX, which they can give to interested users. The Particle Physics Division has a license key server for eXodus, which allows multiple users. Contact Al Forni for further information.

Several people have inquired if there is a way to cut and paste between a Mac and \\numiwinctr. This is possible with the ICA Mac Client. There is a mechanism in "eXodus" to transfer the contents of the Mac clipboard back and forth with an X-Windows selection. However, there is a problem with this mechanism (see 9/22/98 bulletin), and it was disabled for a while (see 5/14/99 bulletin).

It is possible via the Mac Chooser to gain access to disks directly attached to \\numiserver1. Such attachments are part of the mission of \\numiserver1. \\numiserver1 is set up to handle Mac file peculiarities, such as keeping the Resource Fork in memory when the file is open.


OSS Department Reorganization

The significance of the following message is that Andy Lego will no longer be System Manager for \\numiwinctr and \\numiserver1.

From: (Dane Skow)
Newsgroups: fnal.sys.farms.announce
Subject: OSS Department Reorganization
Date: 24 Aug 2000 17:41:08 -0500


I'm contacting you to let you know of an impending organizational change within Computing Division. Effective Sept 5, 2000 the Operating System Support department of the Computing Division will be reorganized into 3 groups to better align responsibilities, customer groups and staff skills. The global responsibilities of the department will not change substantially with the reorganization. However, the group responsible for a specific task will change in many cases and, in some cases, so will the individual primarily performing the work.

The present organization has successfully addressed many needs in the past. I'm confident that the good features and successes can be carried forward into the new organization, while addressing some of the imbalances and preparing for new activities. This reorganization relaxes the alignment of responsibilities by technical criteria (operating system, coding, etc.) and focus more on the commonalities of the customer populations. I expect an aspect of this will be to further enhance the efforts ongoing to improve communication and resource sharing between the Windows and Unix worlds.

There will be three groups: Core Servers and Infrastructure (includes the old UAS, Special Projects and elements of PCS and CSS), Business and Technical Computing (much of the old PCS and some CSS), and Scientific Computing Support (most of the old CSS and some PCS). Below I append an overview of the group responsibilities. This will described in further detail with individuals assigned and upcoming concentrations in the OSS Department web pages at coming soon.

You should expect followup contact through your normal course of liaison with the department to clarify what impact this will have on you directly and discuss sensitivities in schedule/transfer, etc. I expect the immediate impacts should be small, though some confusion/turmoil is inevitable with any reorganization. In particular, we have had a number of departures recently from the UAS group and we ask for particular patience and help in addressing issues with product support and distribution. As always, contact through the helpdesk is encouraged and we are working with the helpdesk staff to make sure routing is appropriately updated with the new structure.

If you do not have a regularly scheduled forum or would like to discuss concerns directly, please contact me ( x4730) or Mark Kaletka ( x2965) who is the new deputy department head.


Dane Skow, OSS Department Head

Core Servers and Infrastructure Group

(Mark Kaletka, Group Leader)


Day to day administrative and on call responsibility (24x7 where applicable) for the following systems:

Members of the infrastructure group will also be assigned as the team lead for various development and/or upgrade projects. The daily administrators of the systems will work with their team lead (the default design lead), when needed: for major upgrades, new purchases, new installations. The daily administrator and the design lead will work as a team to resolve these issues. The Design lead will be responsible for preparing Design and Implementation documentation for any project in which they are involved.

Technical and Office Computing Support Group

(Tim Doody, Group Leader)


Day to day administration and on-call responsibility for the
following systems:

The members of this group will act as the lead
administrators and coordinators for support of these
systems. Each group of systems will be assigned a
primary and secondary support person plus a design
lead. This group will support a 24x7 on call support
list for after hours support of any systems for which
they are responsible.

Experiment Support Group

(Lisa Giacchetti, Group Leader)


Day to day adminstration and on-call responsibility (as agreed) for the following systems:

  • Farms
  • PPD
  • Ktev Online and Offline
  • Fixed Target
  • BPhysics
  • SDSS
  • PPD and CDF WinCenter Server
  • NUMI(aka MINOS) Unix and NT
  • CMS
  • FNALU central Unix Cluster

    The members of this group will act as the lead administrators and coordinators for support of these systems. Each group of systems will be assigned a primary and secondary support person plus a design lead from the design group. This group will support a 24x7 on call support list for after hours support of any systems for which they are responsible.

    Dane Skow, OSS Dept. Head, Computing Division
    Fermilab, MS369, Kirk and Pine St., Batavia, IL 60510

    6/1/00, winmodems with Rockwell chipset

    For anyone with a winmodem with a Rockwell HCF chipset you may have experienced difficulty connecting via the ICA Client to \\numiwinctr or \\numiwinctr. If this applies to you, see advice for Rockwell HCF chipset (from the Citrix Solutions Knowledgebase). You may also have to update to the latest version of the ICA client (version 4.21.779).

    6/5/00, Trouble doing backwards delete

    The following message sent to Michael Li describes the problem.

    Wes Smart notices that a key he used for backwards delete in MS Word and in MS Excel (with \\numiwinctr) no longer works, now that we are switched to \\numiwinctr. His NCD terminal has a N108 keyboard on it. The key is the "< x|" key that is in the same postion as the "Backspace" key on a N101 keyboard. Debbie Harris has an NCD terminal with a N101 keyboard; in her case that key does do backwards delete. Adam Para has a N108 keyboard (like Wes's); in Adam's case the key in question does not do a backwards delete. That key on the N108 keyboard seems to do nothing in the two MS applications, yet does do backwards delete in windows like the Terminal window (and probably the HOST window).

    I did a bit of fooling, but found no cure for this problem. Do you have any suggestions?

    Michael came by the next day and thinks that choosing the right keyboard mapping might cure this. He clued me in to the following method of getting help (executed on a Telnet window to node Fsui03) from \\numiwinctr regarding options for connecting to \\numiwinctr via "rsh numiwinctr wincenter -display your_proper_screen ".

    > rsh x11 -help
    Usage for connecting to Unix Integration Services is:
      [-colors ]              Number of colors
      [-depth ]          Pixel color bit depth
      [-display ]     Display to use
      [-domain ]             Domain name to logon to
      [-exec ]           Pathname of application to run
      [-execwd ]        Working directory for application
      [-geometry ]       Frame geometry (size and/or offset)
      [-help or -?]                Display this message
      [-iconic]                    Iconify session initially
      [-keybd ]           Keyboard mapping file
      [-lang ]  Keyboard language
      [-new_session]               Always create a new session
      [-mcookie ]    MIT-MAGIC-COOKIE-1 authentication
      [-password ]       Password
      [-resolution ]   Screen resolution
      [-same_session]              Always use existing session
      [-user ]               User name to logon with
      [-shadow ]          Shadow an X11 WinStation
    If -exec is specified, it must be the last parameter.
    	rsh server x11 -display my_xserver -res 640x480 -depth 8
    	winstart server -display my_xserver -res 640x480 -depth 8

    Michael left, saying that he would try and figure out the right mapfile to use for the problem described above.

    Comments to: Alan Wehmann(
    Last modified: Thursday, 6/21/01