"The network name cannot be found."

[beandip]

very odd situation.

one NW6sp3 server as primary NDS/file/print.
all workstations are winxp/2k/9x.
all workstations are part of workgroups - no domain.

using a mix of clients - 4.83sp2, 3.32, and 4.9.

when trying to find other machines through My Network Places | Entire
Network | Microsoft Windows Network, only one (of three) workgroups
appears. double-clicking said network produces the following:

"[workgroup] is not accessible.
the network name cannot be found."

we tried to see if it was a basic connectivity issue through ping.
ping by computer name = success.
ping by computer IP = success.

we do not have an internal DNS.
likewise, we do not have extensive HOST entries on each PC.

our netware is primarily TCP/IP. the primary NDS server has IPX
enabled with a SERVERID as a requirement of our backup server. IPX is
not bound to the NIC. no other devices on the network are IPX.

right now, this is only a minor inconvenience. however, we are unable
to add new backup jobs... push anti-virus installs... utilize net
send... etc. we've not found anything on UseNet, MS kb, or Novell kb.

have made no recent major changes to the network.

tried removing individual workstations from the workgroup, then adding
them back. initially, the workstation is able to see all three
workgroups, but after exploring a workgroup the network neighborhood
returns to the above.

any help is greatly appreciated.

 

[Keith V. Klenke]

here is a very small list of things to start with once you complete this
list then come back if you have further issues. Yes, that means complete
this list .....

make sure you have all the post sp4 w2k patches

make sure DS is clean & healthy

make sure you are using the latest nwclient & patches
support.novell.com/filefinder

make sure you have the server updated to the latest patches & oplocks level1
& 2 are set correct

SLP is setup properly on the server, & distributed properly to workstations
via dhcp (yes, you do want to set this up)

DNS setup properly (yes, you do want to set this up)

that speed/duplex on *everything* is hardset, & hardset correctly

latest drivers for everything (nic/chipset/controller/etc)

check cables, make sure everything is cat5e certified, not using flat
cables/cat3/etc (ive seen it in a lot of places)

purge all volumes & turn off compression

make sure there is more than 10% free on EVERY volume

make sure bios/firmware to everything (server/raid
cards/switches/workstations/etc) up to date

 

[beandip]

## for those tracking similar issue ##

we were experiencing a master browser issue with NetBIOS.

using nbtstat -r from several workstations, we found that the only
system being resolved by the workstations was an ill-configured win2k
box that the other systems had "voted" the master. removed this
machine from the network, allowed the systems to "vote" again, and all
was well with the workgroup.

thanks for your help.

here is a very small list of things to start with once you complete this
list then come back if you have further issues. Yes, that means complete
this list .....

make sure you have all the post sp4 w2k patches

make sure DS is clean & healthy

make sure you are using the latest nwclient & patches
support.novell.com/filefinder

make sure you have the server updated to the latest patches & oplocks level1
& 2 are set correct

SLP is setup properly on the server, & distributed properly to workstations
via dhcp (yes, you do want to set this up)

DNS setup properly (yes, you do want to set this up)

that speed/duplex on *everything* is hardset, & hardset correctly

latest drivers for everything (nic/chipset/controller/etc)

check cables, make sure everything is cat5e certified, not using flat
cables/cat3/etc (ive seen it in a lot of places)

purge all volumes & turn off compression

make sure there is more than 10% free on EVERY volume

make sure bios/firmware to everything (server/raid
cards/switches/workstations/etc) up to date

--
Thanks,
Keith V. Klenke
--------------------------------------------------
http://www.abend.org Giving Novell that "slash" feeling
--------------------------------------------------

very odd situation.

one NW6sp3 server as primary NDS/file/print.
all workstations are winxp/2k/9x.
all workstations are part of workgroups - no domain.

using a mix of clients - 4.83sp2, 3.32, and 4.9.

when trying to find other machines through My Network Places | Entire
Network | Microsoft Windows Network, only one (of three) workgroups
appears. double-clicking said network produces the following:

"[workgroup] is not accessible.
the network name cannot be found."

we tried to see if it was a basic connectivity issue through ping.
ping by computer name = success.
ping by computer IP = success.

we do not have an internal DNS.
likewise, we do not have extensive HOST entries on each PC.

our netware is primarily TCP/IP. the primary NDS server has IPX
enabled with a SERVERID as a requirement of our backup server. IPX is
not bound to the NIC. no other devices on the network are IPX.

right now, this is only a minor inconvenience. however, we are unable
to add new backup jobs... push anti-virus installs... utilize net
send... etc. we've not found anything on UseNet, MS kb, or Novell kb.

have made no recent major changes to the network.

tried removing individual workstations from the workgroup, then adding
them back. initially, the workstation is able to see all three
workgroups, but after exploring a workgroup the network neighborhood
returns to the above.

any help is greatly appreciated.

 

[Sam]

Have you tried installing Netbeui on the computers that
cannot see the other workgroup? I have done that and it
resolved the issue.