Client 4.9.2 "Tree not found" errors

[LawnBoy]

I've been testing out the 4.9.2 client for a few days and so far no problems except:
Saturday I came in and got "tree not found". I waited a few minutes, still had error. Rebooted, no good. Reloaded 4.9.2 client, no good. Put server IP in place of servername, no good. Reverted to 4.9.1, all ok.

Running NW 6.5.2, pure IP. Did not have slp scoped (but do now).

Has anybody else seen this? Is it a fluke? Now that I have slp scoped, would this have prevented the problem?

Your thoughts would be most appreciated...

 

[terry712]

slp is key -
should have worked with ip address - although thats nasty
my total preference is that the server should be blank

you should have no probs with slp setup though

 

[jfp23]

Make sure that your using Client 4.9sp2 as the non service packed version did have some problems.

 

[LawnBoy]

Well, I reloaded 4.9.2 to give it another run. This time slp is set up. Time will tell.

 

[marvhuffaker]

Just want to say that I also prefer to leave the server field blank.. You're logging in to the tree, not a particular server. The server field goes way back to bindery days when you did have to make connections to specific servers.

If your client and server are functional, you should always be able to attach with the IP address, although it should only be used for testing. So something else might be going on there.

Marvin.



Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting

http://www.redjuju.com