Grass Valley Aurora Browse v.6.0b Installation - Manual (Page 50)

50 Aurora Browse Installation and Configuration Guide September 22, 2006
Chapter 3 Configuring the system
From a Windows networking perspective, when a user account is defined on a local
computer rather than a Domain Controller, the account is a “local” account, whose
complete name is \, rather than
\. For example, with an encoder named Encoder1, a
MediaFrame server named Server1, and a NAS named NAS1, there are three separate
local accounts: Encoder1\nbadmin, Server1\nbadmin, and NAS1\nbadmin.
The Windows network automatically maps a local account from one computer onto
the local account of another computer—as long as both the account name and the
password are identical. To enable this mapping to occur, the Windows Domain
Controller “synchronizes” the local accounts on computers at the time they join the
Domain. Therefore, if the nbadmin account is added to the NAS machine after the
Windows NAS has joined the Windows Domain, this synchronization does not occur.
This should not be a problem on factory-prepared Aurora Browse machines, as they
come with the nbadmin account pre-configured. However, if the proper sequence is
not followed and the problem does occur, the workaround is to remove the NAS from
the Windows Domain and then re-add it immediately thereafter.
Accessing services
Software components are distributed among the machines that make up the system.
These software components run as Windows services. A machine has the services that
correspond to the software components it hosts.
When you change the configuration for a particular software component through the
configuration pages, you must restart that software component’s service to put the
changes into effect. Click
Start | Settings | Control Panel | Administrative Tools |
Services to access the services. All service names start with “Thomson…”, so they
group together in the services list.
Refer to “Ports and services mapping” on page 36 for a list of services.
Accessing system configuration pages
Use Internet Explorer to browse to port 280 of a machine to access its configuration
pages. You must have administrator permissions on the machine. For example, to log
on to the configuration pages on the MediaFrame server with administrator
permissions, use the following:
Username: root-nb-svr\nbadmin
Password: *****
The settings you find on a particular computer’s configuration pages depend on the
software installed on the computer. For example, if the Proxy MDI component is
hosted on a single-channel encoder, you find the Proxy Managed Device
configuration settings at port 280 of that single-channel encoder. However, if the
Proxy MDI component is hosted on a dedicated MDI server, you find the Proxy
Managed Device configuration settings at port 280 of the MDI server machine.
You can access a computer’s configuration pages as follows:
• From the local computer, use the following URL:
http://localhost:280
• For configuration pages on the MediaFrame server, you can also open the Aurora
***** Contact Grass Valley
Support for password.