Anonymous_User Absent Member.
Absent Member.
3422 views

client issues on new Dell Latitude D520

We just recieved some new Dell Latitude D520 laptops and after installing
our version of Windows XP cannot get the Novell Client 4.91 SP2 to
communicate with the tree.

After installing the client and rebooting I am able to click on
the "Trees" option and select our tree name. Then when I click on
the "Contexts" button I get the message "cannot access tree "tree name"".

I have tried an earlier version of the Client with the same issues. The
two NICS are 1) Broadcom 4401 2) Dell minicom wireless 1390

It doesn't matter which nic I'm trying to access the tree from the
message is the same. I appreciate any information you can give me.

Thanks
Don

Labels (1)
0 Likes
19 Replies
Anonymous_User Absent Member.
Absent Member.

Re: client issues on new Dell Latitude D520

What version of NetWare running at the server ?


--
Edison Ortiz
Novell Product Support Forum SysOp
(No Email Support, Thanks !)
0 Likes
Anonymous_User Absent Member.
Absent Member.

client issues on new Dell Latitude D520

Just as an update to this original post. I'm now seeing this same issue
with a Dell Optiplex 210L that has an Intel 100/VE nic. The machines see
the tree, but don't seem able to communicate with it.

Thanks again


> We just recieved some new Dell Latitude D520 laptops and after

installing
> our version of Windows XP cannot get the Novell Client 4.91 SP2 to
> communicate with the tree.
>
> After installing the client and rebooting I am able to click on
> the "Trees" option and select our tree name. Then when I click on
> the "Contexts" button I get the message "cannot access tree "tree

name"".
>
> I have tried an earlier version of the Client with the same issues.

The
> two NICS are 1) Broadcom 4401 2) Dell minicom wireless 1390
>
> It doesn't matter which nic I'm trying to access the tree from the
> message is the same. I appreciate any information you can give me.
>
> Thanks
> Don
>


0 Likes
Anonymous_User Absent Member.
Absent Member.

client issues on new Dell Latitude D520

As an update to this issue we are now seeing the exact same problem with
the new Dell Optiplex 210L computers that are using an Intel 100/VE nic.
Each time they see the tree just fine, but then will not communicate with
it.

Thanks again.


> We just recieved some new Dell Latitude D520 laptops and after

installing
> our version of Windows XP cannot get the Novell Client 4.91 SP2 to
> communicate with the tree.
>
> After installing the client and rebooting I am able to click on
> the "Trees" option and select our tree name. Then when I click on
> the "Contexts" button I get the message "cannot access tree "tree

name"".
>
> I have tried an earlier version of the Client with the same issues.

The
> two NICS are 1) Broadcom 4401 2) Dell minicom wireless 1390
>
> It doesn't matter which nic I'm trying to access the tree from the
> message is the same. I appreciate any information you can give me.
>
> Thanks
> Don
>


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: client issues on new Dell Latitude D520

We are currently running Netware 6.0 sp5

> What version of NetWare running at the server ?
>
>
> --
> Edison Ortiz
> Novell Product Support Forum SysOp
> (No Email Support, Thanks !)


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: client issues on new Dell Latitude D520

On 6/9/2006 don.remy@nebo.edu wrote:

> We are currently running Netware 6.0 sp5


Server in the same VLAN as the workstation ?
Let's see the SLPINFO /ALL output from one workstation.
Try disabling "Bad Name Cache" via the "Advanced Settings" tab on the
Novell Client Properties page.
--
Edison Ortiz
Novell Product Support Forum SysOp
(No Email Support, Thanks !)
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: client issues on new Dell Latitude D520

The server is in the same vlan as the pc. We always reside our netware
boxes on x.x.x.2 Below is the info from slpinfo /all.

*****************************************************
*** Novell Client for Windows NT ***
*** Service Location Diagnostics ***
*****************************************************

SLP Version: 4.91.0.1
SLP Start Time: 9:50:41am 6/12/2006
Last I/O: 10:23:38am 6/12/2006
Total Packets: Out: 75 In: 62
Total Bytes: Out: 5480 In: 39103


SLP Operational Parameters Values
------------------------------- ------------
Static Scopes NO
Static Directory Agents NO
Active Discovery YES
Use Broadcast for SLP Multicast NO
Use DHCP for SLP YES
SLP Maximum Transmission Unit 1400 bytes
SLP Multicast Radius 32 hops


SLP Timers Values
------------------------------------- ------------
Give Up on Requests to SAs 15 seconds
Close Idle TCP Connections 5 minutes
Cache SLP Replies 1 minutes
SLP Default Registration Lifetime 10800 seconds
Wait Before Giving Up on DA 5 seconds
Wait Before Registering on Passive DA 1-2 seconds


Scope List Source(s)
---------------------------------------- ------------
<unscoped>
nebo_scope DHCP,DA


DA IP Address Source(s) State Version Local Interface Scope(s)
--------------- --------- ----- ------- --------------- ---------
------
160.7.1.7 DHCP UP SLPV2 160.7.145.232
Nebo_Scope


Local Interface 160.7.145.232
---------------------------------
Operational State: UP
Operating Mode(s): MCAST,STATIC-DA,DHCP-MANDATORY-SCOPES
SA/UA Scopes: nebo_scope
Last I/O: 10:23:38am 6/12/2006
Total Packets: Out: 75 In: 62
Total Bytes: Out: 5480 In: 39103
Last Addr Out: 160.7.1.7
Last Addr In: 160.7.1.7




> On 6/9/2006 don.remy@nebo.edu wrote:
>
> > We are currently running Netware 6.0 sp5

>
> Server in the same VLAN as the workstation ?
> Let's see the SLPINFO /ALL output from one workstation.
> Try disabling "Bad Name Cache" via the "Advanced Settings" tab on the
> Novell Client Properties page.
> --
> Edison Ortiz
> Novell Product Support Forum SysOp
> (No Email Support, Thanks !)


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: client issues on new Dell Latitude D520

SLPINFO looks good. Couple of things.

1) Try forcing the DA information in the client instead
of DHCP and see if it helps.

2) Are they any duplicate names in the network that
can cause the client to be confused when browsing
the TREE ?

3) Firewall installed at the clients ?


--
Edison Ortiz
Novell Product Support Forum SysOp
(No Email Support, Thanks !)
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: client issues on new Dell Latitude D520

I disabled the "bad name cache", but no change. Also tried attaching to
the tree with the firewall disabled and got the same results. There
aren't any duplicate names, and using static DA info hasn't helped.

We have one tree that spans the district called "NEBO", this is the one I
can see, but not communicate with. Each school is a location within that
tree and thus far it doesn't seem to matter what location I'm at. I do
have one extra tree that resides on a solitary server used at one of our
high schools. I can login to that tree without even a hiccup. So I'm
deffintely favoring an issue with our tree, but I've run dsrepair without
any change.

I appreciate the help


> SLPINFO looks good. Couple of things.
>
> 1) Try forcing the DA information in the client instead
> of DHCP and see if it helps.
>
> 2) Are they any duplicate names in the network that
> can cause the client to be confused when browsing
> the TREE ?
>
> 3) Firewall installed at the clients ?
>
>
> --
> Edison Ortiz
> Novell Product Support Forum SysOp
> (No Email Support, Thanks !)


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: client issues on new Dell Latitude D520

I disabled the "bad name cache", but no change. Also tried attaching to
the tree with the firewall disabled and got the same results. There
aren't any duplicate names, and using static DA info hasn't helped.

We have one tree that spans the district called "NEBO", this is the one I
can see, but not communicate with. Each school is a location within that
tree and thus far it doesn't seem to matter what location I'm at. I do
have one extra tree that resides on a solitary server used at one of our
high schools. I can login to that tree without even a hiccup. So I'm
deffintely favoring an issue with our tree, but I've run dsrepair without
any change.

I appreciate the help


> SLPINFO looks good. Couple of things.
>
> 1) Try forcing the DA information in the client instead
> of DHCP and see if it helps.
>
> 2) Are they any duplicate names in the network that
> can cause the client to be confused when browsing
> the TREE ?
>
> 3) Firewall installed at the clients ?
>
>
> --
> Edison Ortiz
> Novell Product Support Forum SysOp
> (No Email Support, Thanks !)


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: client issues on new Dell Latitude D520

Let's isolate SLP troubleshooting and connect to the
server using IP. At the Novell GUI Login, click on Advanced
and replace the server name with its IP address.

Can you login then ?


--
Edison Ortiz
Novell Product Support Forum SysOp
(No Email Support, Thanks !)
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: client issues on new Dell Latitude D520

When I specify the IP address of the server I get the message "tree or
server cannot be found" as soon as I click on OK.



> Let's isolate SLP troubleshooting and connect to the
> server using IP. At the Novell GUI Login, click on Advanced
> and replace the server name with its IP address.
>
> Can you login then ?
>
>
> --
> Edison Ortiz
> Novell Product Support Forum SysOp
> (No Email Support, Thanks !)


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: client issues on new Dell Latitude D520

On 6/12/2006 don.remy@nebo.edu wrote:

> When I specify the IP address of the server I get the message "tree or
> server cannot be found" as soon as I click on OK.


So it's not a SLP issue. I believe the problem is with the prebuilt OS from
Dell since you are only having problems with those models and no other
computer in your network. Can you reinstall Windows XP if possible ?


--
Edison Ortiz
Novell Product Support Forum SysOp
(No Email Support, Thanks !)
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: client issues on new Dell Latitude D520

The problem isn't with the prebuilt OS, but with reinstalled versions of
XP. We have to use our version of XP for cloning purposes, but I've done
fresh installs using both our version of XP and the XP cd that shipped with
the boxes with the same issues. The only way these machines will work with
our tree is if I boot them up out of the box and install the client on the
shipped version of XP.

On the fresh installs I'm using all of the drivers from Dell's site, but
nothing seems to work. The shipped version of XP won't work for us since
we need to reclone and the version Dell ships on the machines don't allow this.



> On 6/12/2006 don.remy@nebo.edu wrote:
>
> > When I specify the IP address of the server I get the message "tree or
> > server cannot be found" as soon as I click on OK.

>
> So it's not a SLP issue. I believe the problem is with the prebuilt OS from
> Dell since you are only having problems with those models and no other
> computer in your network. Can you reinstall Windows XP if possible ?
>
>
> --
> Edison Ortiz
> Novell Product Support Forum SysOp
> (No Email Support, Thanks !)


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: client issues on new Dell Latitude D520

On 6/13/2006 don.remy@nebo.edu wrote:

> The only way these machines will work with
> our tree is if I boot them up out of the box and install the client on the
> shipped version of XP.


Interesting. I'm clueless as to what's the problem here.


--
Edison Ortiz
Novell Product Support Forum SysOp
(No Email Support, Thanks !)
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.