TechRepublic|Forums|Networks

Networks

General discussion

  • Creator
    Topic
  • July 5, 2000 at 12:46 am #2074919

    Netware/Windows client policy manager me

    Locked

    by kharrison · about 24 years, 10 months ago

    I have two Netware 5 servers, one 100-user license and two 5-user licenses. My users were using server 1, which was having problems. After moving most apps and data to server 2, I moved the 100-user license assignment also. The problem now is that there are still references on my Win95/98 workstations that are trying to connect to server 1 (for which there is now no license available). These clients now display Policy Manager error messages (no license available). I have determined that the reference is probably in the system.dat file. I have removed all other references such as print queues, ini files, other registry items that point to server 1. I am still unable to get rid of the policy manager message and am uncertain how I can remove references from the system.dat. I can’t remove server 1 yet because it does have some apps being used by the two 5-user licenses. The remainder of users don’t wish to connect to server 1, but their client (system.dat) wants to anyway.

    Topic is locked This conversation is currently closed to new comments.
  • Creator
    Topic

All Comments

  • Author
    Replies
    • July 5, 2000 at 1:31 am #3767687

      Netware/Windows client policy manager me

      by gnites · about 24 years, 10 months ago

      In reply to Netware/Windows client policy manager me

      Try checking their default server setting in NWAdmin. It’s under the enviroment button for the user object. See if that helps……….

      George

    • July 5, 2000 at 9:17 am #3767533

      Netware/Windows client policy manager me

      by jcparkerconsulting · about 24 years, 10 months ago

      In reply to Netware/Windows client policy manager me

      One important thing which has not been mentioned (checking client is one) is that the REPLY TO GET NEAREST SERVER setting on Server 1 is more than likely still active. reset this and see if you problem goes away.

      This setting allows any server to respond to any client to validate them with NDS. It also will cause your porblem when you are not able to maintain the same level of licenseing on all servers. If you are going to have this situation for some time, you should actully turn the Reply To Nearest Server off on both servers and have the authintication done by the client pathing ie: prefered server.

      Hope this helps your problem.

    • July 6, 2000 at 1:35 am #3765946

      Netware/Windows client policy manager me

      by kuiphoff · about 24 years, 10 months ago

      In reply to Netware/Windows client policy manager me

      Another reason why workstations will continue to access the old server is because of UNC references on their computer. Neil Rubenking from Zif-Davis Publishing wrote a great app called COA32 (available for download from PCMagazine Online) that willsearch the users PCs and change all UNC references from one server to another (registry settings, INI files, ProgMan groups, shortcuts, etc.).

      Not to disagree with my esteemed colleague but the ReplyToGetNearestServer is not a problem. If you look in Monitor at the Active Connections you will see connections marked with an asterisk (*). These are unlicensed connections (don’t consume a license) that can either be authenticated or not authenticated. An unlicensed, not authenticated connection has no rights at all. An unlicensed, authenticated connection has rights to the NDS database but not to the file system and doesn’t consume a license. It’s only when a computer attempts to use a resource on that server that they attempt to receive a licensed conne

      • July 6, 2000 at 8:08 am #3765745

        Netware/Windows client policy manager me

        by kharrison · about 24 years, 10 months ago

        In reply to Netware/Windows client policy manager me

        Thank you! I think COA will help immensely- it does what I had been doing manually. Although, I see it doesn’t touch .dat files. I can see the reference to server 1 in the system.dat- but not being a text file, I’m reluctant to change it with a text editor. I am well aware of the GetNearestServer (didn’t help) and the unlicensed connections. I know you’re right- my clients are actually trying to use (unknown) resources and gain licensed connections.

    • July 6, 2000 at 1:36 am #3765945

      Netware/Windows client policy manager me

      by kuiphoff · about 24 years, 10 months ago

      In reply to Netware/Windows client policy manager me

      Post Continued….

      It’s only when a computer attempts to use a resource on that server that they attempt to receive a licensed connection. Access to NDS alone (for login purposes) doesn’t use a license. If you’re running out of licenses it’s because people are attempting to use a resource other than NDS.

  • Author
    Replies
Viewing 3 reply threads