Netware login takes multiple tries before logging in.

I have a Netware quirk that I'm curious about. I have Netware 6.5 running IP only. I've introduced Vista Business 32bit into the mix. I get them to work just fine with the Netware Client for Vista.

However, It's now a several step process to login. What's odd is that this is completely repeatable. At first I thought it was me, but after testing at least 10 machines it repeats almost identically on each machine.

After initially setting all the login configuration (tree, context, server) I am able to login after several tries. As it should it saves that information and here's what happens on all logins after that.

1) Enter password (username is already there)
2) "play Jeapardy theme" It sits here for a full minute or two or three waiting to login
3) It finally bombs out with an error.
4) I press OK on the error and enter password again.
5) This time I get the Welcome screen and it logs into both Netware and Vista as it should.

There are occasionally slight variations depending on whether the username has a password or not, but this is the most common description. While things work, it's extremely annoying and takes my users a long time to login. This happens on restarts as well as shutdowns and I'd like to streamline this to a normal login.

Thanks in advance

I am a CNE. Do you have the latest Novell Client, SLP services loaded, Hosts file on workstaton, DNS with Netware server entries installed?

There's only one Vista client available and I have it.

I don't think I even use SLP.

It's a brand new Vista system with all available updates applied. The Hosts file is whatever the default is after a Spybot Search and Destroy install. I know SS&D modifies it, but I don't modify it otherwise.

All DNS and IP information is attained via DHCP which is setup on another Windows 2003 server. The server is manually chosen during the initial login and that login profile is saved upon a successful login.

Corey...

Its in the ETC folder on the workstation. You can add the IP and server name. It helps resolve it. Add both DNS entries for server name and IP. Can you ping the server from the workstation? Did you try the formal context login? Can you see the tree and context and server on the login when you click on the boxes?

I added the server IP and name into the Hosts file. That allowed me to ping my servers, which wasn't necessary with XP. However, this did work on all usernames that have a password. Thank you. Can't believe it was so simple.

I do have one other question to toss out on this. I have several generic usernames that do NOT have passwords. The Hosts fix cuts down one password attempt. From three tries to two short ones. There is also a 30 second delay from the time the login screen appears until it will accept a login attempt. Anything before that 30 seconds gets rejected with an error immediately. I wait out the 30 seconds and it accepts the login which then takes me to the local workstation login. It's quick and I just have to press enter a few times, but would like to make it just one try if possible. This must be something to do with the lack of password. Any ideas?

First rule of networking, All usernames have passwords. Passwords don't affect login times. Just stops hackers.

My Novell servers all have DNS (forward and reverse) on the server. I also use SLP services to speed up logins. Make sure each workstation can see the tree and context with no issues. Check your network performance. Do you have the correct NIC drivers installed and configured? Hosts file is used in place of DNS. Try changing the server name to its IP address. Use distinguished logins.