Novell Client 2 SP1 for Windows 7

July 4, 2010 at 06:00:56
Specs: Windows 7
Strange behavior of Novell Client 2 SP1 for Windows 7 - I cannot login to one of the servers.
It is no problem neither from Windows XP with Novell Client 4.91 SP5, nor from SLED 10 with novell-client-2.0-sle10sp1. Only from Windows 7 workstation it attaches one server and ignores other with error 'server is unknown'.
I can attach it only if I give the IP address of this second server. In this case it will attach also the first one.
The tree has the same IP address as the fi

See More: Novell Client 2 SP1 for Windows 7

Report •

#1
July 6, 2010 at 05:40:19
Are the 2 servers in the same tree?

Can you ping the second server by using it's name?
Is the netware server running DNS server?
Is there an A record and a resource record type PTR for the second server configured in your DNS server?

The original poster should always write the last response !!!
Let us know, if the problem is solved !!!


Report •

#2
July 12, 2010 at 21:47:09
Both servers are in the same tree.
DNS server is running on the second one and has the A record for it (nsbes-gw -> 192.168.2.90). Tree has the same IP as first server (nsbes1 -> 192.168.2.100).
Maybe the Novell Client 2 SP1 for Windows 7 has different default settings than Client 4.91 SP5 for Windows XP?
When I install Client 4.91 SP5 for Windows XP from scratch (for example, new Windows install), for the first login I can just select tree and context leaving server field empty, and it will connect both servers without any problem.,
The same method with Client 2 SP1 for Windows 7 will connect only the first server (nsbes1 -> 192.168.2.100 which has the same IP for the tree). If I put in the server field:
192.168.2.100
or nsbes1
or even nsbes-gw
it will connect only nsbes1, but if I put there 192.168.2.90, it will connect both nsbes1 and nsbes-gw

Report •

#3
July 13, 2010 at 07:34:43
Did you use attach command in login script to attach to the second server?

The original poster should always write the last response !!!
Let us know, if the problem is solved !!!


Report •

Related Solutions

#4
July 13, 2010 at 23:51:30
Great thanks, paulsep!!!
You guided me to the solution!!!
Before, ATTACH was not used in login script.
I tried to use it, and found that if I put ATTACH nsbes-gw/user, I get the same error - Server is unknown. But in this way:
ATTACH 192.168.2.90/user - it works, and the drive is mapped to nsbes-gw successfully. So it means it is the DNS problem.
After few discovery steps I found that there was no DNS suffix in TCP/IP settings for network connection in Windows7. After putting the suffix mapping was successfull without ATTACH command in login script.
WindowsXP doesn't need any DNS suffix, so it was never configured for our workstations.
By the way, ATTACH in Windows7 works OK, but in WindowsXP doesn't allow login to extra server...

Report •

#5
July 14, 2010 at 15:53:50
You're welcome :-)

The original poster should always write the last response !!!
Let us know, if the problem is solved !!!


Report •

#6
October 5, 2010 at 07:51:56
I have the same issue but dont really understand how you resolved it.

We are looking to migrate to W7 but like yourself it will only pick up 1 tree when we have 3.

Any help would be much appreciated.


Report •

Ask Question