Solved Novell Client cannot find tree / srever

paulsep October 31, 2012 at 21:59:57

Can you ping any other computer from the PC in question? What OSes are the working PCs running? Is tcp/ip running on the Novell server? Can you ping the Novell servers ip address? Did the PC in question get a valid ip address out of the range of the server?

Can you ping any other computer from the PC in question? Yes What OSes are the working PCs running? All other PC’s are running XP, this PC was working correctly on this server with Win7 before it crashed. Is tcp/ip running on the Novell server? I am not sure how to figure that out, sorry Can you ping the Novell servers ip address? Yes Did the PC in question get a valid ip address out of the range of the server? It has the same IP address as it did before the crash.

paulsep November 1, 2012 at 09:11:26

✔ Best Answer

Try the following: Open the properties of the network card of that PC. Click on Internet Protocol Version 4 (TCP/IPv4) and choose properties Click on Advanced Click the DNS tab Click Add DNS Suffix and add the domain name, e.g. yourdomain.com Click OK til all windows gets closed. You may have to restart the PC. Give it a shot.

paulsep November 5, 2012 at 09:08:34

Were you able, to fix the problem?

Sorry, I got distracted by other problems... I have not gotten it fixed... I don't know what the domain name would be to add.

paulsep November 5, 2012 at 16:22:52

What did you get on ping -a your_servers_ip_address ? You should get something like that: Pinging yourserver.yourdomain.tld [192.168.0.10] with 32 bytes of data: Reply from 192.168.0.10: bytes=32 time=2ms TTL=128 Reply from 192.168.0.10: bytes=32 time=1ms TTL=128 Reply from 192.168.0.10: bytes=32 time=1ms TTL=128 Reply from 192.168.0.10: bytes=32 time=1ms TTL=128 Ping statistics for 192.168.0.10: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 1ms, Maximum = 2ms, Average = 1ms The part yourdomain.tld is, what you need.

When I ping the IP Address that I think is my server it just reads Pinging 192.168.0.10 with 32 bytes of data:

paulsep November 6, 2012 at 11:19:21

But the ping didn't time out, right? Have you tried the same thing from a working XP machine, to get the fqdn name of the server? You can also try to enter the ip address in the tree field of the Novell Client and the correct context of the user, you are trying to login with.

You are my hero! I got the domain name when I ran the server ping on a computer that was logged into the Novell network, then I followed the instructions above to add a DNS suffix, then I put the server IP address in the Tree section of the Advance log in for Novell and it worked!!!! Thank You!

paulsep November 6, 2012 at 15:18:13

You may now try to choose the tree name. Normally, It should work. Otherwise, you have an DNS issue. I assume, the XP machines do run the IPX protocol. Therefore, they work perfectly by using Novell's NCP protocol over IPX. Windows 7 do not support IPX protocol. So you have to configure some additional things in the DHCP and DNS server to provide some informations about the Novell network to the IP clients, or, you have to add some entries to the hosts file of any Windows 7 machine.

Hi paulsep: Do you know what additional things would have to added in the DHCP and DNS sever to provide information about the Novell network to the IP clients, or what entries to the hosts files of the Windows machines so they could see the server on the Novell network?