Anonymous_User Absent Member.
Absent Member.
2109 views

various clients cannot connect via server name...

Howdy,

We used to be able to connect to NetWare server on the NW6.5 SP5 network
from a workstation using Windows' Start | Run and typing the UNC to the
resource (e.g. \\SERVER\VOLUME). However, within the past few months and
using various client versions (4.91 w/ various SPs) we are unable to
connect to the resource as aforementioned. I am logging in as an admin
user to a server that holds the [Root] replica.

We can connect using the DNS name (e.g. \\SERVER.DOMAIN.COM), and we can
then subsequently connect to that resource using the UNC path
\\SERVER\VOLUME; makes sense because we've made the connection, so
there's no need to search for the server name again...

Not sure if this is client-specific, SLP, etc. Can you give me some
troubleshooting ideas?
Labels (1)
0 Likes
14 Replies
Anonymous_User Absent Member.
Absent Member.

Re: various clients cannot connect via server name...

On 12/20/2006 thick@thick.net wrote:

> Can you give me some
> troubleshooting ideas?


Let's see your SLPINFO /ALL output
BTW, I recommend just enabling SLP and NDS as the
name resolution methods. Disable DNS and HOSTS if you can.


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

Re: various clients cannot connect via server name...

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

SLP Version: 4.91.3.0
SLP Start Time: 11:43:07am 12/20/2006
Last I/O: 12:18:15am 12/20/2006
Total Packets: Out: 65 In: 33
Total Bytes: Out: 5698 In: 1752


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>
GLOBALSLPSCOPEUNIT DHCP,DA


DA IP Address Source(s) State Version Local Interface Scope(s)
--------------- --------- ----- ------- --------------- ---------
------

192.148.10.128 DHCP UP SLPV2 [ip hidden]
GlobalSLPScopeU
nit


Local Interface 192.168.104.39
---------------------------------
Operational State: UP
Operating Mode(s): MCAST,STATIC-DA,DHCP-MANDATORY-SCOPES
SA/UA Scopes: GLOBALSLPSCOPEUNIT
Last I/O: 12:18:15am 12/20/2006
Total Packets: Out: 65 In: 33
Total Bytes: Out: 5698 In: 1752
Last Addr Out: 192.148.10.128
Last Addr In: 192.148.10.128
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: various clients cannot connect via server name...

SLPINFO looks good. Try sticking to those 2 name
resolution methods I suggest and post back.


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

Re: various clients cannot connect via server name...

Changed name resolution methods per your suggestion - still unable to
connect to server via UNC...

p.s.
The server's SLP.CFG file shows:

DA IPV4, 192.148.10.128 (IP of the designated SLPDA server)

The SLPDA module is loaded on that server...

However, the Global Scope SLP container does not show any eDir entries
for the server in question... The Global Scope eDir container is in the
root of the tree in its own partition...


> SLPINFO looks good. Try sticking to those 2 name
> resolution methods I suggest and post back.


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: various clients cannot connect via server name...

On 12/20/2006 thick@thick.net wrote:

> However, the Global Scope SLP container does not show any eDir entries
> for the server in question...


Then we have a problem at the server side. The DA should never reference
itself in SLP.CFG. It will find itself via LOOPBACK.


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

Re: various clients cannot connect via server name...

Update:
-------
If the workstation has a static IP address, I cannot find certain servers
via UNC call as we have discussed.

However, I set my workstation to get IP via DHCP and I am now able to get
to the resource with \\SERVER\VOLUME

Are you certain about the DA not having its own entry? I recall reading
that it was OK to do that...

In any event, given the DHCP versus static-IP results mentioned, are we
still talking about the DA's SLP.CFG, or another issue altogether?


> On 12/20/2006 thick@thick.net wrote:
>
> > However, the Global Scope SLP container does not show any eDir

entries
> > for the server in question...

>
> Then we have a problem at the server side. The DA should never reference
> itself in SLP.CFG. It will find itself via LOOPBACK.
>
>
> --
> Edison Ortiz
> Novell Product Support Forum SysOp
> (No Email Support, Thanks !)


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: various clients cannot connect via server name...

On 12/20/2006 thick@thick.net wrote:

> Update:
> -------
> If the workstation has a static IP address, I cannot find certain servers
> via UNC call as we have discussed.


Can you ping the server when using static ?

>
> However, I set my workstation to get IP via DHCP and I am now able to get
> to the resource with \\SERVER\VOLUME


That's expected 🙂

> Are you certain about the DA not having its own entry? I recall reading
> that it was OK to do that...


Very certain, that will break things.

> In any event, given the DHCP versus static-IP results mentioned, are we
> still talking about the DA's SLP.CFG, or another issue altogether?


The DA should have all its services registered in eDirectory. If they aren't
then we have a problem.



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

Re: various clients cannot connect via server name...

Glad to know we are not the only ones with this problem.

We noticed this starting a couple of months ago when we brought up two
new OES Linux servers.

We had problems connecting to one of the two servers in particular.

We host ZEN apps on that server, and it was not uncommon for someone to
click on an app and get an error message about not being able to access
the files. If you tried to type in the UNC path Explorer would sit
there for awhile and then eventually complain about not seeing the server.

But if you put in \\<IP Address of server> then it would connect. From
then on you could type in the UNC path like \\<server name> and it would
work fine.

thick@thick.net wrote:
> Howdy,
>
> We used to be able to connect to NetWare server on the NW6.5 SP5 network
> from a workstation using Windows' Start | Run and typing the UNC to the
> resource (e.g. \\SERVER\VOLUME). However, within the past few months and
> using various client versions (4.91 w/ various SPs) we are unable to
> connect to the resource as aforementioned. I am logging in as an admin
> user to a server that holds the [Root] replica.
>
> We can connect using the DNS name (e.g. \\SERVER.DOMAIN.COM), and we can
> then subsequently connect to that resource using the UNC path
> \\SERVER\VOLUME; makes sense because we've made the connection, so
> there's no need to search for the server name again...
>
> Not sure if this is client-specific, SLP, etc. Can you give me some
> troubleshooting ideas?



--
Jeremy Mlazovsky
Senior System Engineer - Enterprise Desktop
UDit-Central Hardware Systems & Network Storage
University of Dayton

http://forge.novell.com/modules/xfmod/project/?udimage
http://vmpconfig.sourceforge.net/
http://regeditpe.sourceforge.net
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: various clients cannot connect via server name...

> Can you ping the server when using static ?

Yes. And I can connect with DNS name via UNC \\server.domain.com\

> > Are you certain about the DA not having its own entry? I recall

reading that it was OK to do that...
>
> Very certain, that will break things.


> The DA should have all its services registered in eDirectory. If they

aren't then we have a problem.

Let me clarify. I can see the DA's services in eDirectory and can connect
to that server fine, but I can't see some of the other servers' SLP
objects in eDir; shouldn't I see an SLP eDir object for all servers in my
tree? Every servers' SLP.CFG file has been configured the same.

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: various clients cannot connect via server name...

On 12/20/2006 thick@thick.net wrote:

> Let me clarify. I can see the DA's services in eDirectory and can connect
> to that server fine, but I can't see some of the other servers' SLP
> objects in eDir; shouldn't I see an SLP eDir object for all servers in my
> tree? Every servers' SLP.CFG file has been configured the same.


Issue a DISPLAY SLP SERVICES on each server and let me know if the
amount of URLs are the same.

Also, please post the DISPLAY SLPDA from each server.


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

Re: various clients cannot connect via server name...

i have 14 servers, so i'll post some of the items...

server 1 display slpda
192.148.10.128 : v2 : ACTIVE : GLOBALSLPSCOPEUNIT : DHCP : 21 : 0ms

Total Active: 1 Total Inactive: 0

server 2
192.148.10.128 : v1 : ACTIVE : GlobalSLPScopeUnit : STATIC : 0 : 2ms

Total Active: 1 Total Inactive: 0

server 3
Total Active: 0 Total Inactive: 0
(Side note: this server has a configured slp.cfg file, same as servers 1
and 2; when doing a display slp services, it returns 63 URLs - the other
servers return 39 URLs)

server 4 (the slpda server itself)
SLP LOOPBACK : v2 : ACTIVE : GlobalSLPScopeUnit : IANA : 14 : 0ms
192.148.10.128 : v2 : ACTIVE : GLOBALSLPSCOPEUNIT : DHCP : 14 : 0ms


I think I may have stumbled onto something here. I changed the server 3
slp.cfg file (added a blank line after the last entry) and restarted the
server - the server now shows the same SLPDA information as servers 1 and
2, and has registered itself in eDir... I'm assuming the other servers
will have the same behavior... Does that make any sense to
you?
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: various clients cannot connect via server name...

On 12/21/2006 thick@thick.net wrote:

> I'm assuming the other servers
> will have the same behavior... Does that make any sense to
> you?


Yes, it does. It does make a difference to have an extra space.
I also think the scope name may be case sensitive.


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

Re: various clients cannot connect via server name...

Excellent.

I appreciate your time and effort, Edison - you're one of the reasons the
forums are so great!

Enjoy the Holidays


> On 12/21/2006 thick@thick.net wrote:
>
> > I'm assuming the other servers
> > will have the same behavior... Does that make any sense to
> > you?

>
> Yes, it does. It does make a difference to have an extra space.
> I also think the scope name may be case sensitive.
>
>
> --
> Edison Ortiz
> Novell Product Support Forum SysOp
> (No Email Support, Thanks !)


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: various clients cannot connect via server name...

On 12/21/2006 thick@thick.net wrote:

> Excellent.
>
> I appreciate your time and effort, Edison - you're one of the reasons the
> forums are so great!


Glad to help.

> Enjoy the Holidays


You too !


--
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.