In article <(E-Mail Removed). com>,
"optionstraderjeff" <(E-Mail Removed)> wrote:
>My Win98 machine refuses to see my Debian and BSD systems in the
>Network Neighborhood. However, "net use ...", issued in a DOS window,
>quickly establishes a working, browseable drive mapping without any
>problem--the mapped drive even shows up in Windows Explorer. "Find
>Computer" also works, opening a box with the specified machine listed
>and browseable. This suggests that Samba is configured correctly and
>that the network is operational. It seems that everything works except
>for Network Neighborhood. The problem exists whether you click on
>Network Neighborhood from the desktop, or from within Windows Explorer.
> Clicking View / Refresh does not help. The network is configured as
>peer-to-peer; there are no WINS servers of NT Domain Controllers.
>
>I am using a netgear router and have standard TCP/IP using DHCP on all
>machines (both Win and Unix). Everything else networkwise works
>perfectly: ftp, http, ssh, you name it.
>
>Any help would be appreciated.
>
>Jeff
Are the Debian and BSD systems making NetBIOS broadcasts to announce
their presence on the network? If not, they won't appear in Network
Neighborhood.
In addition, Network Neighborhood only shows computers in the same
workgroup as the Win98 machine. Mapping and "Find Computer" work with
computers in any workgroup.
To see other workgroups in Network Neighborhood, click the Entire
Network icon. Click a workgroup to see the computers in it.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)
Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.
Microsoft Most Valuable Professional - Windows Networking
http://mvp.support.microsoft.com
Steve Winograd's Networking FAQ
http://www.bcmaven.com/networking/faq.htm