Anonymous_User

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2010-06-24
23:53
16123 views
Windows 7, Client 2sp1ir1 and ir2, and Sophos - Tree or Server Not Found
Hi,
in the process of testing Windows 7 we've come across the following
situation:
On a fresh Windows 7 Enterprise 32bit install, we have the Novell
Client 2sp1ir1 and ZCM10sp3. It will log in perfectly.
We then install Sophos AntiVirus and reboot.
If we try to log in as soon as the Novell Login Prompt appears then we
will see
- Waiting for Network to Initialize
- Logging in to network
then immediately after that
- Error code 0x800789FC
and we get a message "The tree or server cannot be found. Choose a
different tree or server. Would you still like to try to log in to
Windows?"
If we wait 10 - 15 seconds after the login prompt appears we can log in
without any issue. If we disable the Sophos AV service, we don't have
the issue. Entering the IP Address for the tree and server doesn't
change what is happening.
This is reproducable on multiple machines and is very definitely a
combination of Sophos and the Novell Client. We have tried both ir1
and ir2.
With the XP client you can set the depend on service so the login
prompt wouldn't appear before the IP stack was up, however I can't
really see a way to do that with the Windows 7 client - the closest
service I can see is that for ncp...
Any suggestions - I've logged the issue with both Novell and Sophos but
have a sneaking suspicion that I'll get a lot of finger pointing 🙂
in the process of testing Windows 7 we've come across the following
situation:
On a fresh Windows 7 Enterprise 32bit install, we have the Novell
Client 2sp1ir1 and ZCM10sp3. It will log in perfectly.
We then install Sophos AntiVirus and reboot.
If we try to log in as soon as the Novell Login Prompt appears then we
will see
- Waiting for Network to Initialize
- Logging in to network
then immediately after that
- Error code 0x800789FC
and we get a message "The tree or server cannot be found. Choose a
different tree or server. Would you still like to try to log in to
Windows?"
If we wait 10 - 15 seconds after the login prompt appears we can log in
without any issue. If we disable the Sophos AV service, we don't have
the issue. Entering the IP Address for the tree and server doesn't
change what is happening.
This is reproducable on multiple machines and is very definitely a
combination of Sophos and the Novell Client. We have tried both ir1
and ir2.
With the XP client you can set the depend on service so the login
prompt wouldn't appear before the IP stack was up, however I can't
really see a way to do that with the Windows 7 client - the closest
service I can see is that for ncp...
Any suggestions - I've logged the issue with both Novell and Sophos but
have a sneaking suspicion that I'll get a lot of finger pointing 🙂
39 Replies
zthiel

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2011-03-03
20:02
Any chance someone can email me the single file fix to test with?


Knowledge Partner
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2011-03-04
11:40
On 03/03/2011 20:06, zthiel wrote:
> Any chance someone can email me the single file fix to test with?
If you want the file you will need to log an SR with Novell. This is
deliberately so that Novell can track and resolve any issues.
The fix will be included in IR6.
--
Simon
Novell Knowledge Partner (NKP)
------------------------------------------------------------------------
Do you work with Novell technologies at a university, college or school?
If so, your campus could benefit from joining the Novell Technology
Transfer Partner (TTP) program. See novell.com/ttp for more details.
------------------------------------------------------------------------
> Any chance someone can email me the single file fix to test with?
If you want the file you will need to log an SR with Novell. This is
deliberately so that Novell can track and resolve any issues.
The fix will be included in IR6.
--
Simon
Novell Knowledge Partner (NKP)
------------------------------------------------------------------------
Do you work with Novell technologies at a university, college or school?
If so, your campus could benefit from joining the Novell Technology
Transfer Partner (TTP) program. See novell.com/ttp for more details.
------------------------------------------------------------------------
luminous00

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2011-09-02
18:20
I hate to break the news to you guys, but we're running IR7 and we're having the same exact issue. We were originally seeing it with LDAP Contextless login issues randomly throughout our campus, but once we disabled LDAP entirely and chose the context with autolog we're now seeing random Tree or Server cannot be found issues. We're not running Sophos though, but rather Symantec EndPoint with Win7 32-bit Enterprise. I called Novell about this and they just wrote it off as an LDAP issue but this proves that it's stemming from something deeper. Anyone else seeing this issue past IR6?
theflyingcorpse

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2011-09-02
18:55
luminous00;2134230 wrote:
I hate to break the news to you guys, but we're running IR7 and we're having the same exact issue. We were originally seeing it with LDAP Contextless login issues randomly throughout our campus, but once we disabled LDAP entirely and chose the context with autolog we're now seeing random Tree or Server cannot be found issues. We're not running Sophos though, but rather Symantec EndPoint with Win7 32-bit Enterprise. I called Novell about this and they just wrote it off as an LDAP issue but this proves that it's stemming from something deeper. Anyone else seeing this issue past IR6?
Seen this on IR6, IR7 and IR8. I have only seen it during our deployment phase BEFORE we install Symantec EndPoint protection, where its a forced context... I dont get the issue, and its quite annoying. I've still got to try to tweak timeout values to see if its sudden spikes or sth on the servers thats causing it.
- « Previous
- Next »