Home

Page 1 of 2 12 LastLast
Results 1 to 10 of 15

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

  1. #1
    thick@thick.net NNTP User

    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?

  2. #2
    Edison Ortiz NNTP User

    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 !)

  3. #3
    thick@thick.net NNTP User

    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

  4. #4
    Edison Ortiz NNTP User

    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 !)

  5. #5
    thick@thick.net NNTP User

    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.



  6. #6
    Edison Ortiz NNTP User

    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 !)

  7. #7
    thick@thick.net NNTP User

    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 !)



  8. #8
    Edison Ortiz NNTP User

    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 !)

  9. #9
    Jeremy Mlazovsky NNTP User

    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

  10. #10
    thick@thick.net NNTP User

    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.


Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •