Re: Cannot browse network
From: Tim (timakal_at_hotmail.com)
Date: 04/05/04
- Next message: Ben Fitzgerald: "Clustered Queuing"
- Previous message: Darren Hook [MSFT]: "Re: groups"
- In reply to: Tim: "Re: Cannot browse network"
- Next in thread: George Valkov: "Re: Cannot browse network"
- Reply: George Valkov: "Re: Cannot browse network"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 4 Apr 2004 19:51:41 -0500
Well, I just learned something....
It appears to be a specific problem with XP.... on the same machine, when dual-booting with Windows
2000 Pro, Win2k can properly see the domain and browse the network. XP cannot....
perhaps it's time to wipe XP and reinstall....
"Tim" <timakal@hotmail.com> wrote in message news:%237j58OpGEHA.2876@TK2MSFTNGP09.phx.gbl...
> Thanks :)
>
> I tried the BROWSTAT GETMASTER and I got this message:
>
> Unable to get Master: Access is denied.
>
> I tried BROWSTAT STATUS and got this:
>
> Status for domain WRKDOMAIN on transport
\Device\NetBT_Tcpip_{04E79BDF-665C-4337-A81B-A9B7B7087791}
> Browsing is NOT active on domain.
> Master name cannot be determined from GetAdapterStatus.
>
>
> I'm not sure what else to try. I checked the parameters for BROWSER service on the DC, and it has
> the following attributes:
>
> MaintainServerList: Yes
> IsDomainMaster: FALSE
>
> It IS the ONLY DC on the network, so I set IsDomainMaster to TRUE, and rebooted the computer. That
> was the first thing I did before I sent my original message. So, the above "errors" are after the
> fact of me changing it.
>
> Any thoughts?
>
> Thanks again,
> Tim
>
>
> "George Valkov" <null@somewhere.com> wrote in message
> news:eJ%23kainGEHA.3096@TK2MSFTNGP11.phx.gbl...
> > This is most likely because of a problem with the the Master Browser on the
> > domain.
> > If for some reasons the Master Browser do not maintain the list of servers
> > properly, the domain / workgroup will become inaccessible and clients will
> > receive the message:
> >
> > The list of servers for this workgroup are not currently available.
> >
> > If the server running as a Master Browser becomes firewalled, the domain /
> > workgroup is not accessible.
> >
> > How to find which server is acting as a Master Browser:
> > 1. Obtain the browstat.exe utility. You can find it here:
> > a) CD-ROM:\SUPPORT\TOOLS\SUPPORT.CAB\browstat.exe
> > and copy it to Your windows directory
> > b) You can also install it from CD-ROM:\SUPPORT\TOOLS\SUPTOOLS.MSI
> > note: CD-ROM:\ is the path to Your Windows XP / Windows Server 2003
> > installation CD-ROM.
> >
> > 2. At command prompt run:
> > browstat -?
> > to see the help information for this tool.
> > 3. To get the netbios name of the current Master Browser, run:
> > browstat GETMASTER
> >
> > 4. There are also other usefull options like:
> > Force election on remote domain (ELECT) or force remote master to stop
> > (TICKLE).
> >
> > 5. You can also use the Services snap-in to disable the Computer Browser
> > service on a Server that should not be a Master Browser.
> >
> >
> > I hope this information is useful to You.
> > Bye!
> >
> > George Valkov
> >
> >
> >
> >
> >
> > "Tim" <timakal@hotmail.com> wrote in message
> > news:uqhp#$mGEHA.4048@TK2MSFTNGP12.phx.gbl...
> > > Server is running Windows 2000 Server, SP4. It is a domain controller for
> > a small network.
> > >
> > > I've run into a problem where the clients (mostly comprised of Windows XP
> > Pro, and a few Windows
> > > 2000 Pro) cannot access the network.
> > >
> > > On XP, go to My Network Places, then open up Microsoft Windows Network,
> > then I see my domain. When
> > > I double-click on the domain, I get this error:
> > >
> > > "<DOMAN> is not accessible. You might not have permission to use this
> > network resource. Contact the
> > > administrator of this server to find out if you have access permissions.
> > >
> > > The list of servers for this workgroup are not currently available."
> > >
> > > I have joined the XP machine to the Win2k domain with no problem. I am
> > signed onto the XP computer
> > > with local administrator username. HOWEVER, even if I sign into the domain
> > from it, it will still
> > > give me this same error message.
> > >
> > > BUT, if I just go to the server name \\SERVER, I will get a list of the
> > shares on the server, and
> > > can access each and every one of them.
> > >
> > > Does anyone have any ideas? I'm at a loss...
> > >
> > > Tim
> > >
> > >
> >
> >
>
>
>
- Next message: Ben Fitzgerald: "Clustered Queuing"
- Previous message: Darren Hook [MSFT]: "Re: groups"
- In reply to: Tim: "Re: Cannot browse network"
- Next in thread: George Valkov: "Re: Cannot browse network"
- Reply: George Valkov: "Re: Cannot browse network"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
