dkwymer
asked on
Login error 8819
Hello, I am an IT tech and we are running 2 Nw servers with version 6 sp5. We have about 50 remote users in 10 locations, and everyone is working fine except one computer. We have a plant in Monett, Mo. and they have 4 users. All users can access the servers except one. To back track a little, I told you we have 2 servers. One server is for applications and programs while the other is for internet access. The computer in Monett can access the application server but cannot access the internet server. Whenever they login they get connected to SWAN (the application server) IFP (the NDS tree) but not BORDER (the internet server). Then we try to do a manual login to BORDER, However the message I get is error 8819 :cannot login to specified server will attempt to login as a Bindery. If I haven't mentioned it, the PC is using NW client 4.90. Another bit of info is we are located in St. Louis and as I said we have remote locations. So in order for us to service these PC's we use a program called PC anywhere which allows us to remotely take control of their PC. I cannot connect to PC anywhere from this computer. I believe it is related to the login error. Thank you for your help
I have another thought. Depending on your WAN configuration and your server configurations, it might be possible they are connecting using IPX instead of IP. If your WAN allows IPX through, your SWAN server has both IPX and IP configured, and your BORDER BM server is not configured with both protocols and the IPX/IP gateway, they wouldn't necessarily be able to connect there properly, and if they don't have IP running and pcAnywhere is configured for IP connection, then that would explain not having pcAnywhere functionality. The same for the reverse - if they are running IP only and you're configured to use IPX for pcAnywhere and to only use the IPX/IP gateway on BORDER.
You might want to check that. If you are using both protocols, you might want to consider paring things back to IP only. NW6 prefers IP.
You might want to check that. If you are using both protocols, you might want to consider paring things back to IP only. NW6 prefers IP.
ASKER
How do I check my license object? Is this something I can check in Client Properties or do I need to logon to the server to check this.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You might want to verify how they're logging in - specifically, what context are they logging in to - and make sure the license certificate that is assigned to that user object is at or above that container level in the tree, and not associated to any specific server. It might help to remove the license association to the user object (from the license certificate - not the user object) and let the user grab a license fresh.
While your checking your license objects, you might want to verify that none of the user licenses are associated to a server - they shouldn't be. Only server licenses should be associated to servers.
You might also want to consider updating the client to 4.90 SP2D.
If they get in far enough to log in to one server but not the other, I don't see how it could be related to your inability to access the PC with pcAnywhere.
That should just be an IP connection.