Windows 7 novell cannot find tree

We have been continually trying the rebuild process which has 3 autologins and sometimes it will work on a login or it might fail, there is no logic to it.

The problem is the network guys need us to prove that its the Juniper firewall. We have a request for them to build a connected subnet without the Juniper box for diagnostics but that won't happen until tomorrow at the earliest and this project is almost at its deadline. They have opened up all ports and nothing is being blocked in the logs. Seeing it works sometimes, the only thing I can think is something is dropping. On a non-working trace it looks like: Client sends 6 Service Requests from This was taken from a client that has both worked and failed on the remote VPN subnet.

Any ideas? PetervdM; wrote: not for windows 7, or vista but for w2k and xp it is known that the client starts to early, before the tcpip stack is completely initalized.

Thanks, I'll give this a shot. Even if a client has booted and sitting at login screen for awhile then we try it and it might not find tree. When it does fail to find the tree, what can I do to connect? At the basic level I thought all I would need to do is enter the IP address of the local NW server that it can resolve but this hasn't worked. On the local clients configure the NCW with a static slp scope and static slp da.

Use the ip address of the slp da, which I assume is running on a server across the vpn and not on the local netware server. BTW how have you set up slp on the local netware server? Is it set up to register with the DA server across the vpn and if so is it successful? Configure the NCW default login service properties ie what shows up int the login dialog box with the ip address of the server that provides the tree information and the ip address of the local server for authentication purposes.

If you use LDAP contextless login then set that up with ip addresses for the ldap servers as well. Just trying to eliminate all aspects of name-to-ip address resolution so we do not need to cross any wan links, firewalls, vpn's etc.

You can do these things as a temporary fix until you get the actual problem sorted out and can return to using names and a dynamic configuration instead of ip address's and static configuration.

That will tell you how the client is finding the DA via dhcp, multicast, static and whether it has found the DA's ip address and whether it can talk to the DA up, down.

Since you have already done tip 1 to some extent it may be that the windows client is not routing the requests properly to the vpn network. I've seen this in the past but I forget the fix On a client that fails what does the ip situation look like? Long Explanatory Note you can probably skip this bit It seems to me from the discussion that you may not be aware of the relationship as there seems to be some conflation of the two services in your comments I could be misinterpreting you though.

Let me elaborate a bit. The client trying to resolve the name of the tree via SLP is not helped by having a local server, even if the local server has any part or even the whole tree replicated to it. This is because the Tree is a service and the name of the service, ie the name of the Tree as specified in your client settings, is useless without it being resolvable into the ip address of a server with a replica of the root of the tree.

Thus Service Location Protocol SLP is setup to enable clients to find the ip address of a server which is actually hosting the service. So if your client cannot find out the ip address for the server with the root of the tree then the tree will not be found. The first step in finding the ip address of the server hosting the root of the tree is to find the ip address of the server performing SLP service registration, ie the SLP DA.

You may also tell the local server the ip address of another server that is acting as a DA. With all servers sending service info up to the DA server a client then only needs to talk to the DA to be able to find services and resolve them to an ip address of the server actually hosting the service.

Again, I'm sorry if I am being pedantic and you already know all of this. Cheers, Ron. Thanks for the info Ron. If you do it a second time select all three then the Novell client logins. How do I 1. Thank you! Join our community to see this answer! Unlock 1 Answer and 3 Comments. Andrew Hancock - VMware vExpert. See if this solution works for you by signing up for a 7 day free trial. What do I get with a subscription? With your subscription - you'll gain access to our exclusive IT community of thousands of IT pros.

We can't always guarantee that the perfect solution to your specific problem will be waiting for you. If you ask your own question - our Certified Experts will team up with you to help you get the answers you need. Who are the certified experts? How quickly will I get my solution? We can't guarantee quick solutions - Experts Exchange isn't a help desk.