|
||||||||
|
|
|||||||
![]() |
|
|
Thread Tools | Display Modes |
|
#1
|
|
I have seen alot about this issue (its an all too common
thread on this board). The Problem: Win 98 machines losing their connection to a 2003 Server. I myself have had and am still having this problem. Nothing has fixed the problem - this seems to be the general concensus with everyone looking for a fix or at least no one has said they solved the problem. - First, in every occurance of this lost connection all I needed to do was to START>>RUN type:winipcfg Release ALL then Renew All. By renewing the lease I was able to reestablish the connection without logging back in or restarting the computer. NOTE: This is what worked for me to get the connection back, this did not fix anything as these computer would later lose their connection again. - I've tried increasing the account logon threshold to 15 or more(this seemed to fix the problem initially but it is reoccuring in all machines spuradically) Richard Mueller [MVP] stated in a reply in a different thread that Microsoft recommends that the lockout threshold be set to at least 10. Partly, this is because sometimes a single logon attempt will result in 2 or 3 attempts, as the client tries several protocols to authenticate. - I've tried re-installing the client, removing the client, tried to find the 2003 client (still not sure if that actually exists). This did nothing. - I've been instructed by an MVP here to contact Microsoft in order to acquire the 2003 client and have been given this link. This does not lead to the update but ultimately to Microsoft paid support: http://support.microsoft.com/default.aspx?scid=kb;en- us;323466 I have found an article here that states the support call will be be free as long as you refer to the Knowledge Base Article number (Q323466) and ask for nothing more. More info here: http://groups.google.com/groups?threadm=%23Neh% 23nmwCHA.2352%40TK2MSFTNGP09 - Here is an interesting link about the subject: http://support.microsoft.com/default.aspx? scid=http://support.microsoft.com:80/support/kb/articles/Q2 83/2/61.ASP&NoWebContent=1 - I've seen a suggestion about changing user ticket lifetime the Kerberos settings under group policy/security in 2003. But according to the dsclient specification for 98, Kerberos is not included as a feature so why would changing that setting affect a 98 machine? - Followed links, in submitted feedback, to specific Microsoft documents (like the one below)that promised an updated client for 98 but was not. In fact the 98 client, to my knowledge, is not available online (the old client) - This link has been given as a fix for a 98 machine recently, but contains only the nt client download. It makes mention that the 98 client is available but never gives a link or location (i.e. 2000 server CD) to acquire it (again this is a reference to the old 98 client) http://www.microsoft.com/downloads/details.aspx? FamilyID=7c219dcc-ec00-4c98-ba61- fd98467952a8&DisplayLang=en - In the Community Solutions article below there is reference to installing the 2003 client (not to install the client off the 2000 server CD) - no mention is made as to the location of this "2003 Client". It also makes mention about disabling SMB signing - stating that this should not be done as some articles and threads have suggested doing. http://support.microsoft.com/default.aspx?scid=kb;en- us;555038 David |
|
#2
|
|||
|
|||
|
Have since called that support number and they are going
to email a link & passwd to acquire the 2003 client upgrade. Link to number: http://support.microsoft.com/default.aspx?scid=fh;en- us;Prodoffer32&sd=GN Called: (800) 936-5700, followed instructions (choices), reference support article: http://support.microsoft.com/default.aspx?scid=kb;en- us;323466 Let you know if it does anything! >-----Original Message----- >I have seen alot about this issue (its an all too common >thread on this board). The Problem: Win 98 machines losing >their connection to a 2003 Server. I myself have had and >am still having this problem. Nothing has fixed the >problem - this seems to be the general concensus with >everyone looking for a fix or at least no one has said >they solved the problem. > >- First, in every occurance of this lost connection all I >needed to do was to START>>RUN type:winipcfg Release ALL >then Renew All. By renewing the lease I was able to >reestablish the connection without logging back in or >restarting the computer. NOTE: This is what worked for me >to get the connection back, this did not fix anything as >these computer would later lose their connection again. > >- I've tried increasing the account logon threshold to 15 >or more(this seemed to fix the problem initially but it is >reoccuring in all machines spuradically) Richard Mueller >[MVP] stated in a reply in a different thread that >Microsoft recommends that the lockout threshold be set to >at least 10. Partly, this is because sometimes a single >logon attempt will result in 2 or 3 attempts, as the >client tries several protocols to authenticate. > >- I've tried re-installing the client, removing the >client, tried to find the 2003 client (still not sure if >that actually exists). This did nothing. > >- I've been instructed by an MVP here to contact Microsoft >in order to acquire the 2003 client and have been given >this link. This does not lead to the update but ultimately >to Microsoft paid support: >http://support.microsoft.com/default.aspx?scid=kb;en- >us;323466 > I have found an article here that states the support >call will be be free as long as you refer to the Knowledge >Base Article number (Q323466) and ask for nothing more. >More info here: >http://groups.google.com/groups?threadm=%23Neh% >23nmwCHA.2352%40TK2MSFTNGP09 > >- Here is an interesting link about the subject: >http://support.microsoft.com/default.aspx? >scid=http://support.microsoft.com:80/support/kb/articles/Q 2 >83/2/61.ASP&NoWebContent=1 > >- I've seen a suggestion about changing user ticket >lifetime the Kerberos settings under group policy/security >in 2003. But according to the dsclient specification for >98, Kerberos is not included as a feature so why would >changing that setting affect a 98 machine? > >- Followed links, in submitted feedback, to specific >Microsoft documents (like the one below)that promised an >updated client for 98 but was not. In fact the 98 client, >to my knowledge, is not available online (the old client) > >- This link has been given as a fix for a 98 machine >recently, but contains only the nt client download. It >makes mention that the 98 client is available but never >gives a link or location (i.e. 2000 server CD) to acquire >it (again this is a reference to the old 98 client) >http://www.microsoft.com/downloads/details.aspx? >FamilyID=7c219dcc-ec00-4c98-ba61- >fd98467952a8&DisplayLang=en > >- In the Community Solutions article below there is >reference to installing the 2003 client (not to install >the client off the 2000 server CD) - no mention is made as >to the location of this "2003 Client". > It also makes mention about disabling SMB signing - >stating that this should not be done as some articles and >threads have suggested doing. >http://support.microsoft.com/default.aspx?scid=kb;en- >us;555038 > > >. > |
![]() |
| Tags |
| connections, losing, thread |
| Thread Tools | |
| Display Modes | |
|
|