|
|
All AS/400 Tip Categories
/
Client Access
/
Client Access device descriptions
Question:
I just installed about 8 new NT 4 workstations. They're all using Client
Access (with the lastet Service Pack) and NS/Router.
When the 400 creates the workstation ID's for these machines, it makes two
of them. One ID displays correctly (ex. JMM520). On the second ID, it
appends an A to the end of the ID (ex. JMM520A).
Has this happened to anyone else? Does anyone know why it's doing this?
Does anyone know how to stop this?
Any help is appreciated.
Thanx!
Answer(s):
Basically the First device is a Device Controller Description (JMM520). The
second device is a Device Description (JMM520A). If you create another
device it will called JMM520B and will be assosiated with the same
controller
The first device (JMM520) is the device for your router connection
(NS/Router). The other one (JMM520A) is created by the emulator connection
(PC5250). You need both of them if you're using an 5250-emulator on SNA.
Other tips in this category:
Click here to see all categories.
Capturing RMTCMD Results
How to omit the first user/password under NT
How To Get Rid Of Client Access Network Drives
SYSTEM32 folder opening after CA install
Can't get rid of Personal Communications (PCOM)!
Installing Client Access For NT Workstation Users
Validating password against OS/400
How to omit the first user/password under NT
Enabling print screen key
How to copy 5250 screens into MS Word
Operations Navigator - File Systems Not Displaying
Data Transfer, WinNT 4.0, Novell Client for NT
Client Access through the Public Internet
Selective Setup keeps coming up
What ports do I open for Client Access?
Client access password dialog - go away!
How to get Client Access from AS/400 to PC
Client Access download of DBF files
File transfer using CA and TCP/IP
Scheduling file transfers
Client Access device descriptions
DDS and Client Access (PC5250)
Client Access Through A Proxy
Client Access Lockup
DLC Driver location
Automated File Transfer
Changing max # of sessions in CA
Exchanging Word documents with OfficeVision
Client Access Win95/98 Shutdown problems
cwbnw6101-error: network drives could not.....
RUNRMTCMD not working
Connection Error CWBSY1000 Discussion
NT Remote Command password problems
Single Signon Possible?
Troubleshooting connections
Automated NT to AS/400 xfer
Transferring DBF files
CA/400 DOS Security problems
Accessing Network drives hangs PC
SNA Connection Troubleshooting
RMTCMD to a specific PC
SNA Server Over Twinax
Windows 95 OSR2
CA95/NT Password Incorrect
Client Access File transfer all x'40'
Telnet5250 (TN5250) wanted for Win 95/NT
Windows AS/400 Access via RAS
No Client Access Signon! Help!
PC5250: As shipped - no file transfer?
Client Access connect brings up Dialup
Client Access and IE4.0
ODBC Problem SQL0104 - Token * not valid
CA Receives Illegal Operation In DIAGSVR
Accessing The "I:" drive from CA 95/NT
How to download all file members at once
Transferring AS/400 spool files to the PC
PC5250 Crashes On Exit!
Hiding AS/400 In Network Neighborhood
Client Access ODBC Performance
Win95/AS400 Print Screen Problems
Client Access TCP/IP Setup Troubleshooting
Client Access IFS Security
Creating Client Access Install Diskettes
Stop Netsoft Log File Growth
|
