Windows Forum

Ask something
Discussion Locked

IPX/SPX protocol prevents domain logon

0 helpful
7 replies

by pigshot

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I installed a Windows 2000 Server using AD and setting the server as a DHCP, DNS, and WINS provider in mixed mode, and making all users members of DHCP, Domain, Pre-Windows 2000, Wins, and Users. IP and IPX/SPX compatible protocols were installed on the file server.

The user environment was Windows 98se using DHCP for connectivity. The client also had an application requiring IPX/SPX. As long as only TCP/IP was installed, all was well with the world. After IPX/SPX was installed, a very frequent error occured: Invalid user name or password when logging on to domain.

In the world of Netware using NDS, this error occurs if NT4 has lost the everyone group or it has become corrupted. Unfortunately, this is a Windows 2000 Server, andthe group everyone is assumed, can not be created or destroyed.

The windows 98se workstations also have Office 97 Pro (SP1) with SP2b applied. Inconsistant logons keep occuring, sometimes you do, sometimes you don't. I performed a fresh w98se install on a P4 1600 workstation, using both protocols. Success at last, NO. As soon as I installed Office 97 Pro, i immediatly lost connectivity. This is not to say that i lost the ability to ping by friendly name, or browse the internet, only that I could not log on to the domain. As soon as I unloaded Office 97 Pro, I was able to logon again.

Does anyone know what evil lurks in the heart of IPX/SPX and/or Office 97 Pro?

One more thing, all patches, drivers, and updates or in place both on the server, and on the workstations. The problem exists whether SP2 or SP3 is installed on the server.

7 replies

by pacalealaathotmail.c

a protocol can Not prevent a domain logon!

you have a conflict between two concurent services:
DNS and WINS.

in a similar environment we use DNS
and have no problems with domain logins.

it is time to do some software upgrades too
(Office 97 and 'an application requiring IPX/SPX').

p.s "friendly names" (?!)
Haha!

by pierrejamme

This may be a long shot but check out the mapi32.dll. If I remember from Office 97 days, it uses a very puny mapi32.dll that caused me all kinds of wierd headaches before I found that I could fix it by restoring the correct version. The REAL mapi32.dll should be approximately 600kb.
Working in a NetWare environment myself but M$ does funky things sometimes.

by nettek

On 9x clients that have both IPX and IP installed, the logon request may time out before TCP/IP responds from the server. On the server, try binding IPX as the primary protocol to its NIC card.

by pigshot

After using only ipx/spx to try and logon to the domain controller, I was again receiving the following error: The domain passoword you supplied is not correct, or access to your logon server has been denied. This troubled me, as I did not have TCP/IP involved. Searching MS tech support, I found the solution in article Q260399. This problem only affects Windows 2000 servers not NT4 servers and has been confirmed by MS to be a problem in MS Windows 2000. Fortunatly, they provided a work around. First, add Netbios support to the IPX protocol on MS 95/98 workstations; then add the string DirectHost=0 to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Vxd\VNETSUP.

This discussion is closed to new replies.