<network> is not accessible.

Ok. Something happened to our network. When we go to access it through
network neighborhood or windows explorer we get the following: Note,
<network> is the domain/workgroup name. Yes, we are using a domain.

<network> is not accessible. You might not have permission to use this
network resource. Contact ... blah blah blah. The network path was not
found.

We're running Windows 2003 Small Business Server Premium edition and
everything was working good until yesturday. Also, if we type is
//<server-name> we can access the server just as we always have been. It's
just that the list of computers is not showing up. Does anyone know how to
fix this?

Brian

On the server lookin to the event viewer and post any errors you see with
the event ID.

sharad
"Brian Minier" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Ok. Something happened to our network. When we go to access it through
> network neighborhood or windows explorer we get the following: Note,
> <network> is the domain/workgroup name. Yes, we are using a domain.
>
> <network> is not accessible. You might not have permission to use this
> network resource. Contact ... blah blah blah. The network path was not
> found.
>
> We're running Windows 2003 Small Business Server Premium edition and
> everything was working good until yesturday. Also, if we type is
> //<server-name> we can access the server just as we always have been.
It's
> just that the list of computers is not showing up. Does anyone know how
to
> fix this?
>
> Brian
>
>

Ok, I found some ... ok lots. It all started when I tried to set up adapter
teaming. I later stopped it but the problem still persists. Now, for the
errors.
First I got a warning with NETLOGON and EventID 5782 and quickly followed by
an error with NETLOGON and EventID 5774.

I'm going to look into these further but if someone out there who
understands these much better than I do could help, that would be greatly
appreciated.

Brian



"sharad" <(E-Mail Removed)> wrote in message
news:eBth$(E-Mail Removed)...
> On the server lookin to the event viewer and post any errors you see with
> the event ID.
>
> sharad
> "Brian Minier" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > Ok. Something happened to our network. When we go to access it through
> > network neighborhood or windows explorer we get the following: Note,
> > <network> is the domain/workgroup name. Yes, we are using a domain.
> >
> > <network> is not accessible. You might not have permission to use this
> > network resource. Contact ... blah blah blah. The network path was not
> > found.
> >
> > We're running Windows 2003 Small Business Server Premium edition and
> > everything was working good until yesturday. Also, if we type is
> > //<server-name> we can access the server just as we always have been.
> It's
> > just that the list of computers is not showing up. Does anyone know how
> to
> > fix this?
> >
> > Brian
> >
> >
>
>

Network Neighborhood will be upset if you multihome the server. The
browser service depends on netbios names, and can't handle multiple
interfaces on a browse master. The logon trouble sounds like a similar
problem with DNS having multiple entries. See KB 289735 and 292822 .

"Brian Minier" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Ok, I found some ... ok lots. It all started when I tried to set up
adapter
> teaming. I later stopped it but the problem still persists. Now, for the
> errors.
> First I got a warning with NETLOGON and EventID 5782 and quickly followed
by
> an error with NETLOGON and EventID 5774.
>
> I'm going to look into these further but if someone out there who
> understands these much better than I do could help, that would be greatly
> appreciated.
>
> Brian
>
>
>
> "sharad" <(E-Mail Removed)> wrote in message
> news:eBth$(E-Mail Removed)...
> > On the server lookin to the event viewer and post any errors you see
with
> > the event ID.
> >
> > sharad
> > "Brian Minier" <(E-Mail Removed)> wrote in message
> > news:(E-Mail Removed)...
> > > Ok. Something happened to our network. When we go to access it
through
> > > network neighborhood or windows explorer we get the following: Note,
> > > <network> is the domain/workgroup name. Yes, we are using a domain.
> > >
> > > <network> is not accessible. You might not have permission to use
this
> > > network resource. Contact ... blah blah blah. The network path was
not
> > > found.
> > >
> > > We're running Windows 2003 Small Business Server Premium edition and
> > > everything was working good until yesturday. Also, if we type is
> > > //<server-name> we can access the server just as we always have been.
> > It's
> > > just that the list of computers is not showing up. Does anyone know
how
> > to
> > > fix this?
> > >
> > > Brian
> > >
> > >
> >
> >
>
>

In network connection, properties of your primary adapter through which the
client connect to your server, TCP IP proerties - the primary DNS server
should be set to the local IP address of the server.
If both adapters are local, then do this for both the adapters.
If you do teaming then again the primary DNS should be your local
DNS server IP.

Sharad

"Brian Minier" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Ok, I found some ... ok lots. It all started when I tried to set up
adapter
> teaming. I later stopped it but the problem still persists. Now, for the
> errors.
> First I got a warning with NETLOGON and EventID 5782 and quickly followed
by
> an error with NETLOGON and EventID 5774.
>
> I'm going to look into these further but if someone out there who
> understands these much better than I do could help, that would be greatly
> appreciated.
>
> Brian
>
>
>
> "sharad" <(E-Mail Removed)> wrote in message
> news:eBth$(E-Mail Removed)...
> > On the server lookin to the event viewer and post any errors you see
with
> > the event ID.
> >
> > sharad
> > "Brian Minier" <(E-Mail Removed)> wrote in message
> > news:(E-Mail Removed)...
> > > Ok. Something happened to our network. When we go to access it
through
> > > network neighborhood or windows explorer we get the following: Note,
> > > <network> is the domain/workgroup name. Yes, we are using a domain.
> > >
> > > <network> is not accessible. You might not have permission to use
this
> > > network resource. Contact ... blah blah blah. The network path was
not
> > > found.
> > >
> > > We're running Windows 2003 Small Business Server Premium edition and
> > > everything was working good until yesturday. Also, if we type is
> > > //<server-name> we can access the server just as we always have been.
> > It's
> > > just that the list of computers is not showing up. Does anyone know
how
> > to
> > > fix this?
> > >
> > > Brian
> > >
> > >
> >
> >
>
>