Server doesn't show up in Network Neighborhood

"Junior" had a problem just like this about 2 months ago (12/06/04), and our
problem is very similar. Basically, we had problems due to someone doing a
REMOTE DESKTOP to our Exchange Server as themselves. It ran a login script,
which in turn blew down tons of registry entry changes. We've managed to
salvage everything, merging a "good" server registry with the "problem" one.
We've got Exchange running, but the server will not show up in Network
Neighborhood and we cannot map a drive to it. We can, however, browse FROM
it to other servers. SERVER service is running and everything seems fine.
We believe it has something to do w/ LANMANSERVER, but do not know exactly
what. Can anyone help?

Can you map to a share manually by name and tcp/ip address?
Open a dos prompt and run net config server and verify the
hidden field says no. If it says no then open my network places
on the problem machine and see if it shows up there? If so are
there any other machines showing up in the list?

"Dgolden" <(E-Mail Removed)> wrote in message news:
> "Junior" had a problem just like this about 2 months ago (12/06/04),
and our
> problem is very similar. Basically, we had problems due to someone
doing a
> REMOTE DESKTOP to our Exchange Server as themselves. It ran a login
script,
> which in turn blew down tons of registry entry changes. We've managed
to
> salvage everything, merging a "good" server registry with the
"problem" one.
> We've got Exchange running, but the server will not show up in Network
> Neighborhood and we cannot map a drive to it. We can, however, browse
FROM
> it to other servers. SERVER service is running and everything seems
fine.
> We believe it has something to do w/ LANMANSERVER, but do not know
exactly
> what. Can anyone help?

Actually, one of my co-workers recreated the problem in a test lab and found
this to be the answer:

- Go into Network Connections/Properties/General Tab
- UNcheck the box next to FILE AND PRINTER SHARING FOR MS NETWORKS
- Click OK
- CHECK the box to enable it again
- Click OK

Now the drives map and the server is showing up. I realize that's about as
technical as telling someone to "reboot", but it works. Thanks for your help.




"Michael Giorgio - MS MVP" wrote:

> Can you map to a share manually by name and tcp/ip address?
> Open a dos prompt and run net config server and verify the
> hidden field says no. If it says no then open my network places
> on the problem machine and see if it shows up there? If so are
> there any other machines showing up in the list?
>
> "Dgolden" <(E-Mail Removed)> wrote in message news:
> > "Junior" had a problem just like this about 2 months ago (12/06/04),
> and our
> > problem is very similar. Basically, we had problems due to someone
> doing a
> > REMOTE DESKTOP to our Exchange Server as themselves. It ran a login
> script,
> > which in turn blew down tons of registry entry changes. We've managed
> to
> > salvage everything, merging a "good" server registry with the
> "problem" one.
> > We've got Exchange running, but the server will not show up in Network
> > Neighborhood and we cannot map a drive to it. We can, however, browse
> FROM
> > it to other servers. SERVER service is running and everything seems
> fine.
> > We believe it has something to do w/ LANMANSERVER, but do not know
> exactly
> > what. Can anyone help?
>
>
>

That's still better than a reboot. Thanks for that.

--
Todd J Heron, MCSE
Windows Server 2003/2000/NT
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights

Sounds quite interesting. I can't help but wonder how exactly he
managed to re-create the problem?

"DGolden" <(E-Mail Removed)> wrote in message news:
> Actually, one of my co-workers recreated the problem in a test lab and
found
> this to be the answer:
>
> - Go into Network Connections/Properties/General Tab
> - UNcheck the box next to FILE AND PRINTER SHARING FOR MS NETWORKS
> - Click OK
> - CHECK the box to enable it again
> - Click OK
>
> Now the drives map and the server is showing up. I realize that's about
as
> technical as telling someone to "reboot", but it works. Thanks for your
help.
>

It's not the same as a reboot. Disabling and re-enabling the
file and print sharing client in effect is like reinstalling the
client something a reboot doesn't do AFAIK..

"Todd J Heron" <(E-Mail Removed)> wrote in message news:#
> That's still better than a reboot. Thanks for that.

Basically, I think he applied those registry changes that were made on the
problem server to a new "fresh" server to break it. Then he went step by
step through them and UNdid them to narrow it down to what was the culprit.
I obviously don't know specifically, but that's the general idea.

I just hope this post helps someone with the same problem some day - I know
that I would've LOVED to found this when we were in PANIC mode. Thanks for
the support - the Newsgroups are great.


"Michael Giorgio - MS MVP" wrote:

> Sounds quite interesting. I can't help but wonder how exactly he
> managed to re-create the problem?
>
> "DGolden" <(E-Mail Removed)> wrote in message news:
> > Actually, one of my co-workers recreated the problem in a test lab and
> found
> > this to be the answer:
> >
> > - Go into Network Connections/Properties/General Tab
> > - UNcheck the box next to FILE AND PRINTER SHARING FOR MS NETWORKS
> > - Click OK
> > - CHECK the box to enable it again
> > - Click OK
> >
> > Now the drives map and the server is showing up. I realize that's about
> as
> > technical as telling someone to "reboot", but it works. Thanks for your
> help.
> >
>
>
>

Well thanks for posting the resolution. Must have been a
registry setting which gets recreated during the file and
print sharing client installation.

"DGolden" <(E-Mail Removed)> wrote in message news:
> Basically, I think he applied those registry changes that were made on the
> problem server to a new "fresh" server to break it. Then he went step by
> step through them and UNdid them to narrow it down to what was the
culprit.
> I obviously don't know specifically, but that's the general idea.
>
> I just hope this post helps someone with the same problem some day - I
know
> that I would've LOVED to found this when we were in PANIC mode. Thanks
for
> the support - the Newsgroups are great.