PEAP Logon under windows 2000

Hi
I use MS Peap on windows 2k with all the 802.1x patches and so on. every think works fine. the only thing is that the logon process takes tooo long so the logon scripts are not able to complet sucessfully bc the client doesnt have an ip address. is there any solution for that problem?
regards Bernhard

We had a similar problem. During the boot up process the client would start the EAP authentication but the AP would disassociate the client before the client finished booting up. The user had to wait until the PEAP authentication started again (approx 1 minute) before they could login.
We finally solved the problem by applying the MS patches 313664 & 823859 (install in that order) and upgrading the AP firmware (we are still Vxworks) to 12.03T. 12.02T does not work! Also make sure computer authentication is check on the client. Im not sure if MS has released patch 823859I had to call them to get it. Now our users can login as soon as the login screen appears and successfully run the login scripts, etc..

Similar Messages

FAQ: Fix for Problem Printing PostScript "to file" Under Windows 2000

PROBLEM
A number of Acrobat users under Windows 2000 have reported a problem in which printing via the PostScript driver fails when printing "to file" instead of to a standard printer port (such an LPT, USB, TCP/IP port, or even Acrobat's internal port). Printing "to file" refers to the ability to check an option in programs such as FrameMaker or Microsoft Word that causes the PostScript that would have gone to a "real" printer port, to go to a specified file name, prompted for by the driver or application itself. The symptom of the failure may be either (1) no file produced and/or (2) a nondescript error message about "unable to print."
Although we have not yet heard of this problem occurring under Windows XP, we have no reason to believe it couldn't given the extreme similarity in architecture and software components. If you are seeing this with Windows XP, please advise me of this via email and simply substitute "Windows XP" for "Windows 2000" for your purposes in this posting.
CAUSE
The problem is caused by a missing printing port named "FILE:" used by the driver whenever it, guess what, prints "to file." This port is automatically created when Windows 2000 is installed and normally would never disappear. What seems to be happening, based upon reports that I have received from several end users, is that under some conditions yet unidentified, uninstalling one version of Acrobat in preparation for installation of another (newer) version of Acrobat causes the "FILE:" port to be deleted from the system. This printing port deletion does not appear to be caused by any end-user error.
Adobe's Acrobat Quality Assurance group has been alerted to the problem, but to date has been unable to internally reproduce the problem. We would appreciate any information from any user who encounters this problem in terms of exactly how the Acrobat Distiller printer instance was being used prior to an uninstall of Acrobat (for example, were you printing a FrameMaker book "to file" with the
Acrobat Distiller printer instance for purposes of subsequently distilling the whole book manually?)
FIX
Fortunately, it is very easy to add the "FILE:" port back into the operating system:
(1) Logon to Windows 2000 as a user with Administrator privileges.
(2) Go to Start=>Settings=>Printers.
(3) Select File=>Server Properties.
(4) Click the "Ports" tab.
(5) Click "Add Port".
(6) Select "Local Port" and click "New Port".
(7) In response to "Enter a port name:" respond "FILE:" (without the surrounding quote marks, of course) and click OK.
(8) The "FILE:" port should now be in the list of available ports. You may close the remaining dialogs.
At this point, printing "to file" should work correctly. Most likely, you will not see the problem reoccur unless you do another round of uninstalls of Acrobat.
- Dov

You need to download and install the ADPDF9.PPD printer description and use it instead of Device Independent.

README: Fix for Problem Printing PostScript "to file" Under Windows 2000

PROBLEM
A number of Acrobat users under Windows 2000 have reported a problem in which printing via the PostScript driver fails when printing "to file" instead of to a standard printer port (such an LPT, USB, TCP/IP port, or even Acrobat's internal port). Printing "to file" refers to the ability to check an option in programs such as FrameMaker or Microsoft Word that causes the PostScript that would have gone to a "real" printer port, to go to a specified file name, prompted for by the driver or application itself. The symptom of the failure may be either (1) no file produced and/or (2) a nondescript error message about "unable to print."
Although we have not yet heard of this problem occurring under Windows XP, we have no reason to believe it couldn't given the extreme similarity in architecture and software components. If you are seeing this with Windows XP, please advise me of this via email and simply substitute "Windows XP" for "Windows 2000" for your purposes in this posting.
CAUSE
The problem is caused by a missing printing port named "FILE:" used by the driver whenever it, guess what, prints "to file." This port is automatically created when Windows 2000 is installed and normally would never disappear. What seems to be happening, based upon reports that I have received from several end users, is that under some conditions yet unidentified, uninstalling one version of Acrobat in preparation for installation of another (newer) version of Acrobat causes the "FILE:" port to be deleted from the system. This printing port deletion does not appear to be caused by any end-user error.
Adobe's Acrobat Quality Assurance group has been alerted to the problem, but to date has been unable to internally reproduce the problem. We would appreciate any information from any user who encounters this problem in terms of exactly how the Acrobat Distiller printer instance was being used prior to an uninstall of Acrobat (for example, were you printing a FrameMaker book "to file" with the
Acrobat Distiller printer instance for purposes of subsequently distilling the whole book manually?)
FIX
Fortunately, it is very easy to add the "FILE:" port back into the operating system:
(1) Logon to Windows 2000 as a user with Administrator privileges.
(2) Go to Start=>Settings=>Printers.
(3) Select File=>Server Properties.
(4) Click the "Ports" tab.
(5) Click "Add Port".
(6) Select "Local Port" and click "New Port".
(7) In response to "Enter a port name:" respond "FILE:" (without the surrounding quote marks, of course) and click OK.
(8) The "FILE:" port should now be in the list of available ports. You may close the remaining dialogs.
At this point, printing "to file" should work correctly. Most likely, you will not see the problem reoccur unless you do another round of uninstalls of Acrobat.
- Dov

You need to download and install the ADPDF9.PPD printer description and use it instead of Device Independent.

Error installing Sun ONE Directory Server 5.2 under Windows 2000 SP3

Hi,
When I attempt to install the Sun ONE Directory Server 5.2 under Windows 2000 Server SP3, I get the following errors:
Installing Sun ONE Server Basic System Libraries
Installed:C:\WINNT\system32\icudt2.dll
Installed:C:\WINNT\system32\icuin2.dll
Installed:C:\WINNT\system32\icuuc2.dll
Installed:C:\WINNT\system32\libadminutil52.dll
Installed:C:\WINNT\system32\libadmsslutil52.dll
Uninstalling C:\WINNT\System32\icudt2.dll
Uninstalling C:\WINNT\System32\icuin2.dll
Uninstalling C:\WINNT\System32\icuuc2.dll
Uninstalling C:\WINNT\System32\libadminutil52.dll
Uninstalling C:\WINNT\System32\libadmsslutil52.dll
Uninstalling C:\WINNT\System32\libnspr4.dll
Uninstalling C:\WINNT\System32\libplc4.dll
Uninstalling C:\WINNT\System32\libplds4.dll
Uninstalling C:\WINNT\System32\nsldap32v50.dll
Uninstalling C:\WINNT\System32\nsldappr32v50.dll
Uninstalling C:\WINNT\System32\nsldapssl32v50.dll
Uninstalling C:\WINNT\System32\nss3.dll
Uninstalling C:\WINNT\System32\sasl32.dll
Uninstalling C:\WINNT\System32\smime3.dll
Uninstalling C:\WINNT\System32\ssl3.dll
Product Install Failed: java.io.FileNotFoundException: C:\WINNT\System32\libnspr4.dll (Access is denied)
I've checked, and this file does not pre-exist under WINNT\System32.
Any ideas why I'm getting this error? Is this a bug in the installer?
Cheers,
Scott

IIRC this file, sasl32.dll, should get installed onto %WINDIR%\system32 when you install DS5.2 windows version.
You may run WinZIP and File/Open "d52diu.zip" (DS5.2 zip image) and look for "nsbasesys.zip", double click to Open it and you should find "sasl32.dll" there.
Gary

Has anyone had success with Messaging Server 5.2 under Windows 2000 Server?

Just to be up front - we MUST use Windows 2000 - they're not giving me a choice to move to Solaris or Sun Hardware. Linux isn't even a choice, nor is WinNT. (I know, it's annoying).
I've managed to get Directory Server 5.1 to run under windows 2000 without active directory installed. I found that I needed to modify the ims_dssetup.pl script that comes with the Messaging Server 5.2 to reference the full path to my ldapsearch and ldapmodify executables. Apparently, this is a win2k specific problem, and is not necessary on WinNT. This made ims_dssetup.pl work and the install of Messaging Server 5.2 work on a windows 2000 machine.
However, at reboot, the job controller and dispatcher do not automatically start. When I try to start the services manually, I get "Error 1067: The Service terminiated unexpectedly".
Any ideas? I'm desperate here - they're gonna make us use exchange if I can't get >>something<< working. Even a 4.x version of messaging server will do.
Thanks

Well, I do understand that.
However, I've installed iMS 5.2 on win2k several times (I admit, w2k pro, not server), and i've never installed AD.
If you can get it installed and working for your default domain, but not for other domains, then most likely it has nothign to do with AD or AD domains. iMS idea of domains is very different from AD's idea of domains. We need to be very clear about such.
for iMS, you have to create additional domains through Delegated Admin, as either "Hosted Domains" or as "Vanity Domains". We do not suggest using "Vanity Domains", and support for such is deprecated.
Once you have created "Hosted Domains" through Delegated Admin, you can add users to those domains, and they should work, just fine.

AC97 onboard sound DOES NOT WORK under Windows 2000

Just an FYI, the AC97 Audio on your MSI mainboard will not work under Windows 2000, for which the AC97 hardware is not certified. If you try to use it, your audio output will be intermittant at best and will crash your audio applications at worst. A maddening and disheartening problem for people like me who didn't realize the problem existed and spent many hours trying to getting it to go away.

hiya -
I am have this trouble as well!
Are you useing professional, or Advaced server?
I have done EVERY kind of update... so dice.
*sniff *

Install Error Under Windows 2000

I get an error when I try to install Server 7.3 (it's old, I know) under Windows 2000 Server:
obackup.vrf(379) OS_ERROR "while getting service startup pormap."
Anyone know what this means and I how get beyond it?
Thanks.

I get an error when I try to install Server 7.3 (it's old, I know) under Windows 2000 Server:
obackup.vrf(379) OS_ERROR "while getting service startup pormap."I have the same problem. Can anybody help?
TIA,
Vladimir Antropov
[email protected]

Starting Dsigner V6.0 under Windows 2000 Beta 3

Each timme when i try to start any of the function of D     signer
V6.0 under Windows 2000, i have the following error :
RME-00011 : Op     ration 'open' on ACTIVITY has failed
RME-00011 : Op     ration on 'INS' on ci_application_systems has
failed
How can i solve this problem
Thanks for your answer
Tcheng
null

TCHENG Loc Hong (guest) wrote:
: Each timme when i try to start any of the function of D     signer
: V6.0 under Windows 2000, i have the following error :
: RME-00011 : Op     ration 'open' on ACTIVITY has failed
: RME-00011 : Op     ration on 'INS' on ci_application_systems has
: failed
: How can i solve this problem
: Thanks for your answer
: Tcheng
Tcheng,
This is a Headstart forum only. Please refer to
metalink.oracle.com for more information about Oracle Designer.
By the way I think Oracle Designer is not certified against
windows 2000 beta 3.
Regards,
Ton
null

How do i "when the ACPI mode is enabled (by default) under Windows 2000. To fix the problem, replace the gpibpci.sys file on your machine" Where do i go to do this?

I keep getting an error message on the blue screen of death. Beginning dump of physical memory. To fix it a messgae board said "when the ACPI mode is enabled (by default) under Windows 2000. To fix the problem, replace the gpibpci.sys file on your machine with the one that is attached below and then reboot the machine." Where do i go to add this file?

I will get this error randomly, once when I was opening a file on another computer on my network, once when I was logging onto to my bank website on the internet, and another when I was searching through my d drive. Nothing to difficult, I do not even have other programs running when it happens sometimes. Thanks for any help!

Install Problems under Windows 2000

I have recently upgraded my machine from WinNT4 SP6 to Windows 2000 Professional, and now I cannot install JDeveloper. I have tried 3.1, 3.2 and 3.2.2 and all of them hang at different stages during the installation. There is no error message, the install application just stops responding.

I haven't had problems with any other products installing. I have tried installing JDeveloper 3.2.2 with the bare minimum of components as well as trying the typical installation and nothing seems to work, Im not running anything in the background. The system is a HP Kayak XM600 with an intel PIII 800Mhz 256Mb RAM and an ELSA Synergy graphics card. Someone else I know tried to install it on a Dell machine with a different setup, but under Win2000 Professional, and the install failed on them as well.
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by JDev TEam (Laura):
Shaun,
We only support Windows 2000 for release 3.2, so I wouldn't bother with anything earlier. We are not aware of any issues with Windows 2000 Professional.
Have you had any problems installing other applications since your upgrade?<HR></BLOCKQUOTE>
null

Oracle 8.1.7 client installer won't work under windows 2000

I am trying to run the latest oracle client install of 8.1.7 on my windows 2000 PC and when I double click on it, it show the hour glass for a few seconds, then nothing happens. No screens come up at all. I have a Dell PC with an ATI rage 16 MB ultra card and I have dowlnloaded the latest jre 1.1.8 and nothing helps. If I try another kind of PC like my ibm, the installer works fine. Dell has no answers??

I found the solution on another discussion group and it worked for WinNT4 SP6a:
First copy your CD content to your hard disk (by example c:\temp), then rename file "symcjit.dll" (by example "symcjit.old") in directory "c:\temp\Stage\Components\Oracle.swd.jre\1.1.7.30\1\DataFiles\Expanded\jre\win32\bin".
Finally, run Setup.exe in directory "c:\temp\Install\Win32".

GPIB-ENET driver 1.10 no longer works under Windows 2000 service pack 2

I have used my GPIB-ENET adapters with Windows 2000. However, since I installed service pack 2, the GPIB driver 1.10 no longer works. It seems to install correctly and puts the GPIB icon in the Control Panel. After a reboot, however, the icon is gone from the control panel ! It is even gone from the install/remove programs box. I have tried this on two PC's with the same result. This is really bad as my GPIB-ENET boxes are now useless. Can you help with this?

Thanks for the advice, but the 1.20 drivers cannot be downloaded. They must be purchased for $80 US. I have already paid many thousands of dollars for three GPIB-ENET adapters plus LabVIEW. This is really shabby. I know of no other company that charges for driver updates once you have bought the hardware. I should have bought the Tektronix adapters instead.

Instrument I/O assistant isn't installed properly under windows 2000 and xp

after the complete installation of Labview 7express (FDS),the instrument I/O assistant does not work. An error mesage pops up saying that the assistant is not completely installed and that labview 7 should be installed prior to the assistant and that I should reinstall the assistant. I tried to reinstall the I/O assistant directly from the device driver reference CD but it has no effect. What could I do to have the assistant installed correctly ? ( I tried under windows xp same problem)

I forgot the screenshot.
Attachments:
untitled1.gif ‏13 KB

Can't upgrade under Windows 2000

I'm trying to upgrade my existing AIR 1.0 installation, in response to a Secunia PSI security threat warning. When I try, I get the message "The procedure entry point GetAdaptersAddresses could not be located in the dynamic link library IPHLPAPI.DLL." When I close the message, I get the message "This application requires a version of Adobe AIR which cannot be found. Please download the latest version of the runtime from http://www.adobe.com/go/getair, or contact the application author for an updated version." Of course, the link doesn't help, since it just sends me back to where I got the version I'm trying to install.
My system is running Windows 2000 SP 4.

A lot of software companies have built programs in the last few years that don't work out of the box with Win2k. I attribute this to laziness as it is pretty much the same core system as Windows XP 32bit. You might be able to get a later version to work, but you are going to need to hack around a bit.
This guy has a whole blog on it: http://blog.livedoor.jp/blackwingcat/
I was able to install Framework 3.5 SP1 and Zonealarm 8 with his instructions. If you have a hard time following, use google translate.

Trouble installing LabView 7.1 / 8.0 under Windows 2000

When attempting to install LabView 7.1 on a PC running Windows 2000,
the installer produces the message
"Fatal Error. Unhandled MSI Error"
and fails.
I believe my PC account has full administrative privileges; furthermore, the Windows Installer
is version 3.1.4000.1823, ie. it should be up-to-date.
When attempting to install LabView 8.0 instead, the installer fails with the
message "Fatal Error!! Required NIPathsDir property LV80DIR is undefined".
Strangely enough, both installers appear to work on a different, but similarily configured PC;
however, I am unable to see what, if any, configuration differences there may be.
Ideas, anyone?

[quote]
didn't purchase the SSP, so I guess I can't even call NI for Installation assistance.
[/quote]
Sorry I cant help with the installation issue itself, but this part is incorrect. Installation assistance is technically free. SSP is used for development questions/ issues. If it will not install at all this is a valid reason to contact NIs engineers.

PEAP Logon under windows 2000

Similar Messages

Maybe you are looking for