XAUTH With Windows XP?

Hi there, here is my situation:

My corporate FW is a 3com superstack 3 firewall; it is also our VPN server and hosts all VPN connections to our network. Aside from its standard encryption and authentication, it offers XAUTH authentication. Our clients that are using Windows 2000 machines get a windows login prompt when they try to use the VPN from a remote location, but with the XP machines, we have to disable XAUTH, as no prompt appears and the connection cannot be validated.

When Xauth is off, then the XP machines connect fine. But with our setup we need to be able to offer this extra form of authentication.

Any ideas or opinions would be greatly appreciated.

Thank you,

Mike
LVL 2
UnifiedITAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

ewtaylorCommented:
I do not think you caqn use xauth, can you setup radius or tacacs?
http://www.microsoft.com/windowsserver2003/techinfo/overview/vpnfaq.mspx
Q.  Why doesn't Microsoft implement IPSec tunnel mode with XAUTH and mode config?
   
A.  There are several key reasons for this.

XAUTH contains serious security flaws for which no known fix is available and has been rejected for IETF standardization. Given this, Microsoft believes that it would be irresponsible for us to endorse this technology, especially when IETF standards-based technology is under development.
XAUTH is incompatible with existing IETF authentication frameworks such as EAP and GSS-API. This means that developers who want to develop authentication techniques for the Windows platform would need to develop their methods using multiple, incompatible APIs. This prevents customers from using existing authentication methods within remote access scenarios. For developers, it increases the complexity and cost of developing a new authentication method. Rather than introducing another authentication framework to the detriment of customers and developers, Microsoft endorses efforts within IETF and IEEE to extend the applicability of EAP. This allows customers and developers to leverage their efforts, developing authentication methods with universal applicability, such as in wireless scenarios (via 802.1X).
Because of the poor interoperability of XAUTH and mode config, Microsoft could not implement the technology and have it work with more than one vendor.
L2TP/IPSec is already an interoperable standard that is supported in commercial products from leading networking companies and can be implemented in models similar to XAUTH with IPSec but with much stronger security, reliable accounting, and standards-based configuration.
The IETF rejected XAUTH and mode config and has a more appropriate IPSec tunnel mode-based remote access solution in development through the IPSRA working group.
 

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
UnifiedITAuthor Commented:
Thanks.. It looks like I missed that link when searching the Net. Thank you for the find.

Mike
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
OS Security

From novice to tech pro — start learning today.