• October 19, 2019, 07:38:18 AM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Author Topic: Dir-857 Network Neighbourhood bug?  (Read 6206 times)

AMPatrick

  • Level 2 Member
  • **
  • Posts: 43
Dir-857 Network Neighbourhood bug?
« on: April 15, 2012, 04:05:56 PM »

Since I switched from my DGL-4500 to the DIR-857; my "Network" neighbourhood is messed up.  Not all the machines within my LAN show up in the "Network" window even though they are in the same workgroup.  And different machines show differences in their respective "Network" window even though they are all in the same workgroup.  Several of my machines in my LAN are concurrently running their own "Master Scheduler" for network browsing (which shouldn't be happening).  This all used to work correctly with my DGL-4500...  The DIR-857 looks like it has done a bad thing to Windows networking...

BTW: I do not use a WINS server and I have the NetBIOS node type in the DIR-857 set to broadcast only (which was the setting I used in the DGL-4500).

As a workaround, I am mapping machines in my LMHOSTS file.  This is a real ugly workaround and difficult to maintain, especially on notebook computers (which I often take out of the house...).  I am also thinking about putting up a WINS server so I won't have to worry about LMHOSTS file synchronization.

Anyone had similar problems and found a better fix?
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 47844
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: Dir-857 Network Neighbourhood bug?
« Reply #1 on: April 15, 2012, 07:18:08 PM »

Care to post a capture of your network hood of what it looks like.
Most people aren't using any LMHOST or WINS services as WINS isn't used much anymore. So default settings are working for most people.
Logged
Cable:200mb/10Mb>NetGear C7800>DIR-882>DGS-1100>HP 24pt Gb Switch. COVR-3902/2202/1203,DIR-2680,890L,882,880L,868L,DNR-202L,DNS-345x2,DCS-933L,936L and 960L.
Go Here>Router Troubleshooting

AMPatrick

  • Level 2 Member
  • **
  • Posts: 43
Re: Dir-857 Network Neighbourhood bug?
« Reply #2 on: April 15, 2012, 11:16:41 PM »

I used the command line variants to display the network conditions as seen by three of the computers on my LAN plus I have some puzzling results from my DNS-323.  As I said, everything used to work with the Windows networking with my DGL-4500 and when I switched to the DIR-857, it all went to h__ll.  Maybe that's where Windows networking really belongs - but you have to give the devil his due when you use his technology.  8)  In any case knock yourself out:

****************************************************
*  This first segment of log was output from a
*  computer called ASUS001 in workgroup PATRICK
*  Note that ASUS001 could not detect any other
*  computers in my LAN tonight.  It started behaving this
*  way after I installed the DIR-857...  ASUS001 is wirelessly
*  connected using a D-Link DAP-1522.  I have good signal
*  strength, and good connectivity (file transfers, HTTP, etc.),
*  it's just the network browser doesn't work right.
*  BTW: I disabled the Master Scheduler service on
*  this computer because I didn't want multiple
*  of these running on my network.  ASUS001 does
*  not find the master scheduler service running
*  on the computer called BOZEN (an HP Windows
*  Home Server - Bozen WHS).  When this happens, it
*  liked to start its own master scheduler service
*  with sometimes very confusing consequences.
****************************************************
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Tony>nbtstat -n

Local Area Connection 6:
Node IpAddress: [192.168.81.61] Scope Id: []

                NetBIOS Local Name Table

       Name               Type         Status
    ---------------------------------------------
    ASUS001        <00>  UNIQUE      Registered
    PATRICK        <00>  GROUP       Registered
    ASUS001        <20>  UNIQUE      Registered
    PATRICK        <1E>  GROUP       Registered

C:\Documents and Settings\Tony>net view
System error 6118 has occurred.

The list of servers for this workgroup is not currently available

C:\Documents and Settings\Tony>nbtstat -c

Local Area Connection 6:
Node IpAddress: [192.168.81.61] Scope Id: []

    No names in cache

C:\Documents and Settings\Tony> exit



*****************************************************
* This second segment of the log was output from a
* computer called BOZEN also in workgroup PATRICK.
* It is an HP Windows Home Server and is running the
* master scheduler service  just like MicroSoft doc says
* it should be doing.  Note that it was not able
* to register all the computers on my LAN.  Note that
* the computer called ASUS001 does not appear!
* Neither does my D-Link DNS-323 NAS...  Not cool!
*****************************************************
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator>nbtstat -n

Local Area Connection:
Node IpAddress: [192.168.81.103] Scope Id: []

                NetBIOS Local Name Table

       Name               Type         Status
    ---------------------------------------------
    BOZEN          <00>  UNIQUE      Registered
    PATRICK        <00>  GROUP       Registered
    BOZEN          <20>  UNIQUE      Registered
    PATRICK        <1E>  GROUP       Registered
    PATRICK        <1D>  UNIQUE      Registered
    ..__MSBROWSE__.<01>  GROUP       Registered

C:\Documents and Settings\Administrator>net view
Server Name            Remark

-----------------------------------------------------
\\ACER007              Tony's Acer Aspire One netbook
\\BOZEN                Bozen WHS
\\LIBRARY              HP Pavilion in Office area
The command completed successfully.


C:\Documents and Settings\Administrator>exit



***************************************************************
*  This third segment of log was output from a computer
*  called LIBRARY in workgroup PATRICK.  It was able to find
*  the Master Scheduler service running on BOZEN and at least
*  some of the computers in my LAN show up. (The same ones
*  that BOZEN found - as expected.)
***************************************************************
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:\Users\Tony>nbtstat -n

Local Area Connection:
Node IpAddress: [192.168.81.101] Scope Id: []

                NetBIOS Local Name Table

       Name               Type         Status
    ---------------------------------------------
    LIBRARY        <00>  UNIQUE      Registered
    PATRICK        <00>  GROUP       Registered
    PATRICK        <1E>  GROUP       Registered
    LIBRARY        <20>  UNIQUE      Registered

    No names in cache

C:\Users\Tony>net view
Server Name            Remark

-----------------------------------------------------
\\ACER007              Tony's Acer Aspire One netbook
\\BOZEN                Bozen WHS
\\LIBRARY              HP Pavilion in Office area
The command completed successfully.


C:\Documents and Settings\Tony> exit



**************************************************************
* This fourth log segment uses remote nbtstat and remote net view
* commands to interogate a computer called BLITZEN also in
* workgroup PATRICK.  BLITZEN is a D-Link DNS-323 NAS.
* Although, it can still be referenced by it's IP address, it does
* not appear in the network neighbourhood (ie: a general
* net view command without identifying a host - as demonstrated above).
* Note that I cannot now access the NBT table on BLITZEN - this used to work
* with the DGL-4500...  BTW: Blitzen is hard wired to the router (not wireless).
**************************************************************
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:\Users\Tony>ping blitzen.ici

Pinging Blitzen.ici [192.168.81.104] with 32 bytes of data:
Reply from 192.168.81.104: bytes=32 time=2ms TTL=64
Reply from 192.168.81.104: bytes=32 time<1ms TTL=64
Reply from 192.168.81.104: bytes=32 time<1ms TTL=64
Reply from 192.168.81.104: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.81.104:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 2ms, Average = 0ms

C:\Users\Tony>nbtstat -A 192.168.81.104

Local Area Connection:
Node IpAddress: [192.168.81.101] Scope Id: []

    Host not found.


C:\Users\Tony>net view \\192.168.81.104
Shared resources at \\192.168.81.104

Dlink DNS-323

Share name  Type   Used as  Comment

-------------------------------------------------------
backups     Disk
BT          Disk
lp          Print           USB Printer
Media       Disk            Media - read only
Media-1     Disk            Media - RW
Public      Disk
Tony        Disk
Volume_1    Disk
web_page    Disk            Enter Our Web Page Setting
The command completed successfully.


C:\Users\Tony> exit

« Last Edit: April 15, 2012, 11:20:52 PM by AMPatrick »
Logged

AMPatrick

  • Level 2 Member
  • **
  • Posts: 43
Re: Dir-857 Network Neighbourhood bug?
« Reply #3 on: April 15, 2012, 11:28:26 PM »

BTW: My D-Link DNS-323 can no longer refer to my networked computers by their NetBIOS names.  I now need to use their IP addresses in order to do file access (file transfers, and backups using the built-in DNS-323 file transfer mechanism)...  Very annoying...
Logged