I don't see why I'd need WINS, but I did already try that anyway with no
success.
As I intimated, the network has been faultless since installed.
All PC's are XP or Windows 2000. All on the same physical site.
Cannot get a list of PC's / Servers on any PC or server, even the domain
controllers. Just get that error...............
Pretty wierd.
"Anthony" wrote:
> You don't say anything about your network, but if normal network browsing is
> not working you need to use WINS.
> Anthony
>
>
> "Fraser Simpson" <(E-Mail Removed)> wrote in message
> news:B3619FA4-989B-4E7B-9FE2-(E-Mail Removed)...
> > Hi there,
> >
> > As the subject says, this issue cropped up some time ago and I've been
> > trawling the internet for similar issues and trying all the fixes, but
> > nothing..........
> >
> > If I go to any PC or server and request a specific server like \\server1
> > it
> > finds and displays it perfectly and works. However if I try to go through
> > Network places and then entire network, there is a 3-4 second delay before
> > I
> > see the primary domain/workgroup listed. Then once I click on that to see
> > a
> > list of PC's and servers in that domain/workgroup I wait for approx 10-15
> > seconds and then get a message saying "The list of servers for this
> > workgroup
> > is not currently available"
> >
> > Also in the same message it mentions that I might not have access to the
> > network resource.
> >
> > I read some stuff and think I've found the answer and then it doesn't fix
> > my
> > issue.
> >
> > When I run netdiag I get this.........
> >
> >
> > Computer Name: GTWLGDS
> > DNS Host Name: gtwlgds.gtgroup.co.nz
> > System info : Windows 2000 Server (Build 3790)
> > Processor : x86 Family 6 Model 4 Stepping 2, AuthenticAMD
> > List of installed hotfixes :
> > KB890046
> > KB893756
> > KB896358
> > KB896422
> > KB896424
> > KB896428
> > KB899587
> > KB899588
> > KB899589
> > KB899591
> > KB900725
> > KB901017
> > KB901214
> > KB902400
> > KB904706
> > KB904942
> > KB905414
> > KB905915
> > KB908519
> > KB908531
> > KB909520
> > KB910437
> > KB911280
> > KB911562
> > KB911564
> > KB911567
> > KB911927
> > KB912812
> > KB912919
> > KB912945
> > KB913446
> > KB914388
> > KB914389
> > KB916281
> > KB917159
> > KB917344
> > KB917422
> > KB917734
> > KB917953
> > KB918439
> > KB918899
> > KB920214
> > KB920670
> > KB920683
> > KB921398
> > KB921883
> > KB922616
> > Q147222
> >
> >
> > Netcard queries test . . . . . . . : Passed
> >
> >
> >
> > Per interface results:
> >
> > Adapter : Local Area Connection
> >
> > Netcard queries test . . . : Passed
> >
> > Host Name. . . . . . . . . : gtwlgds
> > IP Address . . . . . . . . : 192.168.4.20
> > Subnet Mask. . . . . . . . : 255.255.255.0
> > Default Gateway. . . . . . : 192.168.4.1
> > Dns Servers. . . . . . . . : 127.0.0.1
> >
> >
> > AutoConfiguration results. . . . . . : Passed
> >
> > Default gateway test . . . : Passed
> >
> > NetBT name test. . . . . . : Passed
> > [WARNING] At least one of the <00> 'WorkStation Service', <03>
> > 'Messenger Service', <20> 'WINS' names is missing.
> >
> > WINS service test. . . . . : Skipped
> > There are no WINS servers configured for this interface.
> >
> >
> > Global results:
> >
> >
> > Domain membership test . . . . . . : Passed
> >
> >
> > NetBT transports test. . . . . . . : Passed
> > List of NetBt transports currently configured:
> > NetBT_Tcpip_{FE11D0F1-5E51-41A3-8889-051E64735B47}
> > 1 NetBt transport currently configured.
> >
> >
> > Autonet address test . . . . . . . : Passed
> >
> >
> > IP loopback ping test. . . . . . . : Passed
> >
> >
> > Default gateway test . . . . . . . : Passed
> >
> >
> > NetBT name test. . . . . . . . . . : Passed
> > [WARNING] You don't have a single interface with the <00> 'WorkStation
> > Service', <03> 'Messenger Service', <20> 'WINS' names defined.
> >
> >
> > Winsock test . . . . . . . . . . . : Passed
> >
> >
> > DNS test . . . . . . . . . . . . . : Passed
> > PASS - All the DNS entries for DC are registered on DNS server
> > '127.0.0.1' and other DCs also have some of the names registered.
> >
> >
> > Redir and Browser test . . . . . . : Passed
> > List of NetBt transports currently bound to the Redir
> > NetBT_Tcpip_{FE11D0F1-5E51-41A3-8889-051E64735B47}
> > The redir is bound to 1 NetBt transport.
> >
> > List of NetBt transports currently bound to the browser
> > NetBT_Tcpip_{FE11D0F1-5E51-41A3-8889-051E64735B47}
> > The browser is bound to 1 NetBt transport.
> >
> >
> > DC discovery test. . . . . . . . . : Passed
> >
> >
> > DC list test . . . . . . . . . . . : Failed
> > Failed to enumerate DCs by using the browser.
> > [ERROR_NO_BROWSER_SERVERS_FOUND]
> >
> >
> > Trust relationship test. . . . . . : Skipped
> >
> >
> > Kerberos test. . . . . . . . . . . : Passed
> >
> >
> > LDAP test. . . . . . . . . . . . . : Passed
> >
> >
> > Bindings test. . . . . . . . . . . : Passed
> >
> >
> > WAN configuration test . . . . . . : Skipped
> > No active remote access connections.
> >
> >
> > Modem diagnostics test . . . . . . : Passed
> >
> > IP Security test . . . . . . . . . : Skipped
> >
> > Note: run "netsh ipsec dynamic show /?" for more detailed information
> >
> >
> > The command completed successfully
> >
> > I can see it says DC List fails which is clearly what's causing the issue,
> > but I don't know how to delve deeper into the issue to solve it.
> >
> > I've remove and reinstalled client for Microsoft Networking, TCP/IP and
> > the
> > network adaptor driver on the server as some people said this solved their
> > issue.
> >
> > The server listed above is the GC server, does DHCP and DNS. That's about
> > it. Just a basic file server.
> >
> > Any ideas ?? Any help much appreciated...............
> >
> > Fraser Simpson
> >
>
>
>
|