Novell client for Vista won't find tree

[9iron]

I'm trying to login to my Novell 6.5 server with my newly installed client for Vista, but I'm getting a constant message that it cannot find the tree or server. Funny thing is, when I clicked the browse "Trees" button in the client advanced settings, it found the tree on its own. It just won't cooperate when I try to browse to the context or server.

Anyone dealt with this before?

 

[marvhuffaker]

Sounds like an SLP problem. You'll need to configure an SLPDA and push the settings out, preferably using DHCP, to the workstations so they know where to look for your novell tree.

you could also put the IP address of the server in the Server field and see if that helps. If it does, its definitely an SLP issue.

Marvin Huffaker, MCNE
Marvin Huffaker Consulting, Inc.
A Novell Platinum Partner

http://www.redjuju.com

 

[9iron]

Hi, Marv. I turned off the windows firewall, and that took care of it. Does this strike you as odd?

 

[marvhuffaker]

That makes sense too. Yes its odd, but Windows doesn't know what NCP is, so you need to configure the firewall to allow it (Port 524).. Some firewalls don't recognize NCP and others don't. I haven't worked with Vista to really understand how the firewall works.

Marvin Huffaker, MCNE
Marvin Huffaker Consulting, Inc.
A Novell Platinum Partner

http://www.redjuju.com

 

[9iron]

Marv, I guess I jumped the gun a little when I said that turning off the firewall worked. I can't get back in again, and I double-checked to make sure the firewall was still off and it is. ARRRRGHHH!

Can you explain a little more about that SLPDA and how to save it on my machine?

 

[IRudebwoy]

I don't think the SLP tools in the Vista client are availible as in previous incarnations. I installed it a few months ago to test vista in my environment. There is no way to test SLP, slpinfo is gone. I could still log in but I had to enter in all the connection info (tree & context), no browsing. I could be mistaken but I'm pretty sure it's gone.

The only thing I didn't try was using the DHCP server options to set the pertinent connection info.

It (vista) works (if you can call it that) but I'm not gonna use it.

Have Fun!

 

[marvhuffaker]

One of our guys is running Vista, so I'll take a look at his machine and see what's up.

Marvin Huffaker, MCNE
Marvin Huffaker Consulting, Inc.
A Novell Platinum Partner

http://www.redjuju.com

 

[9iron]

I've read some posts elsewhere about putting in the IP addy instead of the server name, but I tried that and still get the same error message. Let's see, what else...my firewall is turned off (as I mentioned), Windows Defender is off.

This machine's been a nightmare from day one. It took me close to two weeks of posting questions about why I couldn't install any applications, until someone told me to try installing them in safe mode. Can you believe that? I need to install some programs in safe mode on this thing. Unreal. It's like this thing is in total lockdown mode and won't let me do anything unless I circumvent the whole thing. Anyway, thanks for the replies. I'll stay in touch and continue searching for enlightenment.

 

[IRudebwoy]

Try putting the name of a replica or master server in the tree field of the log in dialog.

 

[9iron]

Sorry for the late reply. We're a pretty small network here, so no replicas or master servers. As a whim, I decided to just try the server name in the tree field, but no luck.

That which does not kill me makes me stronger I say!

 

[9iron]

I forgot to mention the error code I'm getting: 0x800789FC. I've been Googling it, but all I can find are others like me...lotsa questions, but no answers.

 

[9iron]

Just to put this baby to bed, I figured it out. It was that OneCare service, which is not to be confused with the service "Windows Live OneCare", which had no effect on the client problem. I narrowed it down to this one service, which I promptly shutdown. I may have opened this machine up to future problems by doing this, but for now I'm satisfied. I also used the latest Novell client patch, but in retrospect I'm not even sure it was needed.

Thanks to all who chimed in to help here. Now if you'll excuse me, I need to go scarf up as many XP machines as I can.