Re: logon fails
- From: David Sherman <dshermin@xxxxxxxxxxxxx>
- Date: Wed, 11 Jan 2006 09:31:41 -0500
Thank you for you response. We figured and corrected the log on
question. We won't know for sure until we get info at the client
site. I will add more detail including the infomation that you need,
if future help is needed.
thanks again
On Wed, 11 Jan 2006 08:17:24 GMT, v-natliu@xxxxxxxxxxxxxxxxxxxx
("Nathan Liu [MSFT]") wrote:
>Hello David,
>
>Thank you for posting in the SBS newsgroup.
>
>According to your description, I understand that users cannot connected to
>the SBS 2003 Standard Server, and they received this error message "you
>don't have enough licenses to let me log on". If I have misunderstood the
>problem, please don't hesitate to let me know.
>
>In order to narrow down this issue, please kindly answer and perform the
>following questions and steps:
>
>1. For the current information, I would first like you to check the
>license information on your SBS server. Please click "Print License
>information" from Licensing node in the Server Management. Notice that
>there is a mention of maximum number of licenses number. This number is not
>real time and should be viewed as a high watermark of the highest number of
>licenses used on the server. Would you please let me know the license
>installed number and maximum number in the license information?
>
>2. Please run 'eventvwr.exe' (without the quotation marks) on the command
>prompt on the SBS 2003 Server, and check if there are any error messages
>about this issue, then save log file as .evt file and then email to my
>working mailbox: v-natliu@xxxxxxxxxxxxx
>
>To do so, please perform the following steps:
>a. Click Start -> Run, type EVENTVWR.MSC and click OK.
>b. Select the Application Event log, right click it and select "Save Log
>File As"
>c. Save it as .evt file and email to me.
>d. Export other Event Logs too.
>
>3. Please send me the screen shot of the error message as an email
>attachment.
>
>To do this, please follow the steps below:
>
>a) When the screen appears, press PrScrn (this key is located to the right
>of the
>F12 key on the keyboard)
>b) Create a new Word document and open it.
>c) Press Ctrl + V to paste the screen shot into the document.
>d) Send this document as the mail's attachment to me.
>
>4. As you mentioned, when the issue occurred, there are only 3 users
>were connecting to the SBS Server, please kindly note the following
>information:
>
>If you are using per user CAL, OWA does access Exchange resources and use a
>license so if you are logged into OWA in two places, or twice on the same
>workstation, or are logged into OWA and Outlook on the same system then you
>will be using two licenses. This should apply to the new Outlook over HTTP
>as well, because it is still connecting to, and using resources from, the
>Exchange server. In this newer version users will be less apt to use up
>multiple licenses by opening OWA, then navigating to another website and
>logging back into the original OWA session because the new OWA client
>automatically disconnects the session if you navigate away from the page or
>do not log out.
>
>If using Per user as long as they logon to RWW and from the internal device
>as the same user only 1 cal would be needed.
>
>If they are using Per Device, then the device the connect to RWW from would
>need 1 and if they connect to an internal device and then back to the
>server.. that internal device would also need a cal. Assuming I''m using
>Per Device CALS, meaning if I''m connecting to OWA from a device then my
>understanding is that device would need a CAL, then if I use Remote Desktop
>to connect to my XP desktop at work.. and then from there connect back to
>the server, the XP desktop would also need a Per Device CAL, which most
>likely the XP desktop at the office would already have one, but.. both
>should need one..
>
>More information from
>http://www.microsoft.com/windowsserver2003/sbs/techinfo/overview/licensingfa
>q.mspx
>
>
>5. Based on my research, this issue may occur if the licensing
>information may be the cause.
>
>Let''s try the following to reset licensing information:
>1) Stop the License Logging Service.
>2) Rename LLSUSER.LLS
>3) Start the License Logging Service.
>
>NOTE: It may also be necessary to rename licstr.cpa and autolicstr.cpa. If
>you do so, the client access licenses will need to be reactivated, so
>let''s wait to see if the steps above resolve this first.
>
>
>In addition, for all the licensing questions, you can call 1-800-426-9400
>(select option 4), Monday through Friday, 6:00 A.M. to 5:30 P.M. (PST) to
>speak directly to a Microsoft licensing specialist. Worldwide customers can
>use the Guide to Worldwide Microsoft Licensing Sites
>http://www.microsoft.com/licensing/index/worldwide.asp to find contact
>information in their locations.
>
>I appreciate your time and cooperation. Please do not hesitate to let me
>know if you have any further concerns, I am looking forward to hearing from
>you.
>
>Have a nice day!
>
>Best regards,
>
>Nathan Liu (MSFT)
>Microsoft CSS Online Newsgroup Support
>
>Get Secure! - www.microsoft.com/security
>======================================================
>This newsgroup only focuses on SBS technical issues. If you have issues
>regarding other Microsoft products, you'd better post in the corresponding
>newsgroups so that they can be resolved in an efficient and timely manner.
>You can locate the newsgroup here:
>http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
>
>When opening a new thread via the web interface, we recommend you check the
>"Notify me of replies" box to receive e-mail notifications when there are
>any updates in your thread. When responding to posts via your newsreader,
>please "Reply to Group" so that others may learn and benefit from your
>issue.
>
>Microsoft engineers can only focus on one issue per thread. Although we
>provide other information for your reference, we recommend you post
>different incidents in different threads to keep the thread clean. In doing
>so, it will ensure your issues are resolved in a timely manner.
>
>For urgent issues, you may want to contact Microsoft CSS directly. Please
>check http://support.microsoft.com for regional support phone numbers.
>
>Any input or comments in this thread are highly appreciated.
>======================================================
>This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
>
>--------------------
>>From: David Sherman <dshermin@xxxxxxxxxxxxx>
>>Subject: logon fails
>>Date: Tue, 10 Jan 2006 15:47:40 -0500
>>Message-ID: <i178s15d7n1lmksr29de55im73iucmmi12@xxxxxxx>
>>X-Newsreader: Forte Agent 2.0/32.640
>>MIME-Version: 1.0
>>Content-Type: text/plain; charset=us-ascii
>>Content-Transfer-Encoding: 7bit
>>Newsgroups: microsoft.public.windows.server.sbs
>>NNTP-Posting-Host: adsl-68-252-44-81.dsl.wotnoh.ameritech.net 68.252.44.81
>>Lines: 1
>>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
>>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:235560
>>X-Tomcat-NG: microsoft.public.windows.server.sbs
>>
>>I have a new client that is running a SBS 2003 Standard server. The
>>office has 5 machines. Each machine has a printer attached to it.
>>Once in a while, users can't get connected to the server. Error
>>message the basic "you don't have enough licenses to let me log on." I
>>can't understand this when there are only 3 users connected to the
>>machine.
>>
>>I have 2 question:
>>
>>1. How to correct this?
>>
>>2. Does SBS 2003 log the failed log on attempts so any attempt after
>>the failed log on gets the out of licenses message also?
>>
>>thanks
>>
.
- Follow-Ups:
- Re: logon fails
- From: "Nathan Liu [MSFT]"
- Re: logon fails
- References:
- logon fails
- From: David Sherman
- RE: logon fails
- From: "Nathan Liu [MSFT]"
- logon fails
- Prev by Date: Re: DNS does not resolve
- Next by Date: Re: ISA 2004 & companyweb
- Previous by thread: RE: logon fails
- Next by thread: Re: logon fails
- Index(es):
Relevant Pages
|
