Kyocera Ai5555 NC-2 Instruction Hand Book - Page 72

Confirming Bindery Context

Page 72 highlights

NetWare Configuration Configure Using NetWare 4.x Bindery Emulation Using PCONSOLE Confirming Bindery Context Perform the following steps to determine if the server has Bindery Context: 1. Login to the server as ADMIN. 2. At the prompt, perform a DOS TYPE of Z:\SYSTEM\AUTOEXEC.NCF. 3. When the file displays, look to see if you have a statement similar to SET BINDERY CONTEXT=O= Where =O= is a sample name for the file server context. Use your own file server context in place of =O=. is the designation for the Server Context, and is obtained by starting PCONSOLE. The Server Context name is displayed in the upper left corner of the Available Options menu screen. 4. If no such name statement in on the screen, you must add that statement to enable the NC-2 to work. In that case, exit from PCONSOLE and use a DOS text editor to add the following statement to the AUTOEXEC.NCF file: SET BINDERY CONTEXT =O=LOCAL 5. After adding the statement to the AUTOEXEC.NCF file, you must power down the server and restart it for the changes to take effect. Or, as an alternative method, the network administrator can type the SET command at the Server console to make changes immediately. In this case, any changes will be in effect until the server is powered down and restarted again. Important: The command at the console prompt takes effect immediately, whereas, the definition in the autoexec file takes effect only when the server is shut down and then restarted. NetWare Configuration 3-51

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167

NetWare Configuration 3-51
NetWare Configuration
Configure Using NetWare 4.x Bindery Emulation
Using
PCONSOLE
Confirming Bindery Context
Perform the following steps to determine if the server has Bindery Context:
1. Login to the server as ADMIN.
2. At the prompt, perform a DOS TYPE of Z:\SYSTEM\AUTOEXEC.NCF.
3. When the file displays, look to see if you have a statement similar to
SET BINDERY CONTEXT=O=<Name>
Where =O=<Name> is a sample name for the file server context.
Use your own file server context in place of =O=<Name>.
<Name> is the designation for the Server Context, and is obtained by
starting PCONSOLE. The Server Context name is displayed in the upper
left corner of the
Available Options
menu screen.
4. If no such name statement in on the screen, you must add that statement to
enable the NC-2 to work. In that case, exit from PCONSOLE and use a DOS
text editor to add the following statement to the AUTOEXEC.NCF file:
SET BINDERY CONTEXT =O=LOCAL
5. After adding the statement to the AUTOEXEC.NCF file, you must power
down the server and restart it for the changes to take effect.
Or, as an alternative method, the network administrator can type the SET
command at the Server console to make changes immediately. In this case,
any changes will be in effect until the server is powered down and restarted
again.
Important: The command at the console prompt takes effect immediately,
whereas, the definition in the autoexec file takes effect only when the server
is shut down and then restarted.