Lanmanserver issue

Greetings,

Last week I had a Win2K server (current on updates) fail to start a myriad
of services after it started. Critical due to the fact that it would not
start my Exchange 2000 services. Perplexed at what to do about this and
noticing that my server was no longer viewable in the network neighborhood,
I was beginning to get concerned. I found that in the registry,
particularly HKLM\System\CurrentControlSet\Services\ I had no lanmanserver
folder. All of my other servers had on and it appeared that this might be a
culprit. I read from an article about the Event code 7003 that to first try
and re run the latest service pack. When this did absolutely nothing, it
gave the mention to copy a working server's registry entry for lanmanserver
and to copy and merge it into the affected computer. Right after then
restart from doing that, Mail services and all other services started up
without fail.

HOWEVER: now the servers shares are lost and the server is still not
present in network neighborhood. Nor is it accessible in trying to map a
drive or even use an administrative share. Email still is working fine and
I can RDP to the server at will.

What can I do to get the server back into the "neighborhood" It appears not
to want to broadcast or is broadcasting all wrong.

Thanks in Advance and hope to hear back from someone soon.

--
Thank you for your time and attention to this matter,

Robert Wisian Jr.

Can you verify the server service is running when the problem
occurs. You may have to stop and restart the service using
the services applet.
"Junior" <(E-Mail Removed)> wrote in message news:
> Greetings,
>
> Last week I had a Win2K server (current on updates) fail to start a
myriad
> of services after it started. Critical due to the fact that it would
not
> start my Exchange 2000 services. Perplexed at what to do about this
and
> noticing that my server was no longer viewable in the network
neighborhood,
> I was beginning to get concerned. I found that in the registry,
> particularly HKLM\System\CurrentControlSet\Services\ I had no
lanmanserver
> folder. All of my other servers had on and it appeared that this
might be a
> culprit. I read from an article about the Event code 7003 that to
first try
> and re run the latest service pack. When this did absolutely nothing,
it
> gave the mention to copy a working server's registry entry for
lanmanserver
> and to copy and merge it into the affected computer. Right after then
> restart from doing that, Mail services and all other services started
up
> without fail.
>
> HOWEVER: now the servers shares are lost and the server is still not
> present in network neighborhood. Nor is it accessible in trying to
map a
> drive or even use an administrative share. Email still is working
fine and
> I can RDP to the server at will.
>
> What can I do to get the server back into the "neighborhood" It
appears not
> to want to broadcast or is broadcasting all wrong.
>
> Thanks in Advance and hope to hear back from someone soon.
>
> --
> Thank you for your time and attention to this matter,
>
> Robert Wisian Jr.
>
>

Well whatever you do don't remove it from the domain!!! Exchange 2003 is
tied to Active Directory so you don't want to "cut its throat". I'm not
sure about why it won't show on the LAN properly, maybe someone can help get
that working.

If you can get it to function partly correct, then as soon as possible I
would get exchange off that machine and get it rebuilt. You would want to
build an additional Exchange box with both Exchanges part of the same
"Exchange Site". Then use the "move mailbox" feature in Exchange to move the
mail boxes to the new temporary Exchange.

Once everything is safely moved use the proper proceedures to remove
Exchange from the box (don't just wipe the box). Once Exchange is off the
box, move it out of the Domain into its own workgroup,...rebuild
it,..re-join,...reinstall Exchange into the same "Exchange Site",...move the
mailboxes back again. Then follow the proper steps to decommission the
temporary Exchange.

Research it out and do it properly,..don't just start "clicking" with what
tiny amount of information I gave in this post.

What I am describing is called the "Swing Server Method".

How to upgrade to Exchange Server 2003 by using the swing upgrade method
http://support.microsoft.com/default...b;en-us;821896
--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


"Junior" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Greetings,
>
> Last week I had a Win2K server (current on updates) fail to start a myriad
> of services after it started. Critical due to the fact that it would not
> start my Exchange 2000 services. Perplexed at what to do about this and
> noticing that my server was no longer viewable in the network
neighborhood,
> I was beginning to get concerned. I found that in the registry,
> particularly HKLM\System\CurrentControlSet\Services\ I had no
lanmanserver
> folder. All of my other servers had on and it appeared that this might be
a
> culprit. I read from an article about the Event code 7003 that to first
try
> and re run the latest service pack. When this did absolutely nothing, it
> gave the mention to copy a working server's registry entry for
lanmanserver
> and to copy and merge it into the affected computer. Right after then
> restart from doing that, Mail services and all other services started up
> without fail.
>
> HOWEVER: now the servers shares are lost and the server is still not
> present in network neighborhood. Nor is it accessible in trying to map a
> drive or even use an administrative share. Email still is working fine
and
> I can RDP to the server at will.
>
> What can I do to get the server back into the "neighborhood" It appears
not
> to want to broadcast or is broadcasting all wrong.
>
> Thanks in Advance and hope to hear back from someone soon.
>
> --
> Thank you for your time and attention to this matter,
>
> Robert Wisian Jr.
>
>

I show that it is started and appears to be running. I can restart this
service after 5pm my time when most everyone is out of the office. This is
already critical since I have BackupExec on a different server and with this
happening, my remote agent will not connect and backup the mailbox store and
Information Stores.

--R

"Michael Giorgio - MS MVP" <(E-Mail Removed)> wrote in
message news:udaHi$(E-Mail Removed)...
> Can you verify the server service is running when the problem
> occurs. You may have to stop and restart the service using
> the services applet.
> "Junior" <(E-Mail Removed)> wrote in message news:
>> Greetings,
>>
>> Last week I had a Win2K server (current on updates) fail to start a
> myriad
>> of services after it started. Critical due to the fact that it would
> not
>> start my Exchange 2000 services. Perplexed at what to do about this
> and
>> noticing that my server was no longer viewable in the network
> neighborhood,
>> I was beginning to get concerned. I found that in the registry,
>> particularly HKLM\System\CurrentControlSet\Services\ I had no
> lanmanserver
>> folder. All of my other servers had on and it appeared that this
> might be a
>> culprit. I read from an article about the Event code 7003 that to
> first try
>> and re run the latest service pack. When this did absolutely nothing,
> it
>> gave the mention to copy a working server's registry entry for
> lanmanserver
>> and to copy and merge it into the affected computer. Right after then
>> restart from doing that, Mail services and all other services started
> up
>> without fail.
>>
>> HOWEVER: now the servers shares are lost and the server is still not
>> present in network neighborhood. Nor is it accessible in trying to
> map a
>> drive or even use an administrative share. Email still is working
> fine and
>> I can RDP to the server at will.
>>
>> What can I do to get the server back into the "neighborhood" It
> appears not
>> to want to broadcast or is broadcasting all wrong.
>>
>> Thanks in Advance and hope to hear back from someone soon.
>>
>> --
>> Thank you for your time and attention to this matter,
>>
>> Robert Wisian Jr.
>>
>>
>
>

Thanks for the heads up on that procedure. Ideally I would hope to not have
to go so far, however, if I should find myself in a bind, it may have to
come to this. I have tried creating new shares on this server and still I
am not able to produce a folder connection via a workstation.

--R

"Phillip Windell" <@.> wrote in message
news:(E-Mail Removed)...
> Well whatever you do don't remove it from the domain!!! Exchange 2003 is
> tied to Active Directory so you don't want to "cut its throat". I'm not
> sure about why it won't show on the LAN properly, maybe someone can help
> get
> that working.
>
> If you can get it to function partly correct, then as soon as possible I
> would get exchange off that machine and get it rebuilt. You would want to
> build an additional Exchange box with both Exchanges part of the same
> "Exchange Site". Then use the "move mailbox" feature in Exchange to move
> the
> mail boxes to the new temporary Exchange.
>
> Once everything is safely moved use the proper proceedures to remove
> Exchange from the box (don't just wipe the box). Once Exchange is off the
> box, move it out of the Domain into its own workgroup,...rebuild
> it,..re-join,...reinstall Exchange into the same "Exchange Site",...move
> the
> mailboxes back again. Then follow the proper steps to decommission the
> temporary Exchange.
>
> Research it out and do it properly,..don't just start "clicking" with what
> tiny amount of information I gave in this post.
>
> What I am describing is called the "Swing Server Method".
>
> How to upgrade to Exchange Server 2003 by using the swing upgrade method
> http://support.microsoft.com/default...b;en-us;821896
> --
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>
> "Junior" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Greetings,
>>
>> Last week I had a Win2K server (current on updates) fail to start a
>> myriad
>> of services after it started. Critical due to the fact that it would not
>> start my Exchange 2000 services. Perplexed at what to do about this and
>> noticing that my server was no longer viewable in the network
> neighborhood,
>> I was beginning to get concerned. I found that in the registry,
>> particularly HKLM\System\CurrentControlSet\Services\ I had no
> lanmanserver
>> folder. All of my other servers had on and it appeared that this might
>> be
> a
>> culprit. I read from an article about the Event code 7003 that to first
> try
>> and re run the latest service pack. When this did absolutely nothing, it
>> gave the mention to copy a working server's registry entry for
> lanmanserver
>> and to copy and merge it into the affected computer. Right after then
>> restart from doing that, Mail services and all other services started up
>> without fail.
>>
>> HOWEVER: now the servers shares are lost and the server is still not
>> present in network neighborhood. Nor is it accessible in trying to map a
>> drive or even use an administrative share. Email still is working fine
> and
>> I can RDP to the server at will.
>>
>> What can I do to get the server back into the "neighborhood" It appears
> not
>> to want to broadcast or is broadcasting all wrong.
>>
>> Thanks in Advance and hope to hear back from someone soon.
>>
>> --
>> Thank you for your time and attention to this matter,
>>
>> Robert Wisian Jr.
>>
>>
>
>

Browsing relies on the server service to send a host name
announcement packet to a local SMB or segment master
browser. The SMB gathers the local browse list and passes
it on to the DMB or domain master browser. The DMB gathers
the entire list and passes back to all SMBs who then provide the
list to clients who request them. This whole process also relies on
NetBios broadcasts in order to work. Netbios should be enabled
and not filtered. Open a dos prompt and run net view. What do
you see? Attempt to map to a share on the problem server first
by tcp/ip address then by name. Does either fail. If so, what is the
exact error message.

"Junior" <(E-Mail Removed)> wrote in message news:
> I show that it is started and appears to be running. I can restart
this
> service after 5pm my time when most everyone is out of the office.
This is
> already critical since I have BackupExec on a different server and
with this
> happening, my remote agent will not connect and backup the mailbox
store and
> Information Stores.
>

What happens when you manually attempt to map to the
new share e.g., exact error message?

"Junior" <(E-Mail Removed)> wrote in message news:
> Thanks for the heads up on that procedure. Ideally I would hope to
not have
> to go so far, however, if I should find myself in a bind, it may have
to
> come to this. I have tried creating new shares on this server and
still I
> am not able to produce a folder connection via a workstation.
>

When doing a net view lookup on \\computername, it returns a System error
51: Windows cannot find the network path. Verify that the network path is
correct
and the destination computer is not busy or turned off. If Windows still
canno
t find the network path, contact your network administrator.

As far as mapping to shares, when I attempt to map a drive, I continue to be
prompted for a username and password, which never authenticates (IP address)
and then I get the error:
The network path \\computername\share could not be found. Does this on
shares and administrative shares. I must also mention that the shares I use
to have on the server are no longer there, so I am trying to recreate the
shares and they still will not map or open remotely.

--R

"Michael Giorgio - MS MVP" <(E-Mail Removed)> wrote in
message news:%(E-Mail Removed)...
> Browsing relies on the server service to send a host name
> announcement packet to a local SMB or segment master
> browser. The SMB gathers the local browse list and passes
> it on to the DMB or domain master browser. The DMB gathers
> the entire list and passes back to all SMBs who then provide the
> list to clients who request them. This whole process also relies on
> NetBios broadcasts in order to work. Netbios should be enabled
> and not filtered. Open a dos prompt and run net view. What do
> you see? Attempt to map to a share on the problem server first
> by tcp/ip address then by name. Does either fail. If so, what is the
> exact error message.
>
> "Junior" <(E-Mail Removed)> wrote in message news:
>> I show that it is started and appears to be running. I can restart
> this
>> service after 5pm my time when most everyone is out of the office.
> This is
>> already critical since I have BackupExec on a different server and
> with this
>> happening, my remote agent will not connect and backup the mailbox
> store and
>> Information Stores.
>>
>
>

Make sure NetBios is enabled in the tcp/ip properties of
the problem server. If it is enabled which setting is selected?

"Junior" <(E-Mail Removed)> wrote in message news:
> When doing a net view lookup on \\computername, it returns a System
error
> 51: Windows cannot find the network path. Verify that the network path
is
> correct
> and the destination computer is not busy or turned off. If Windows
still
> canno
> t find the network path, contact your network administrator.
>
> As far as mapping to shares, when I attempt to map a drive, I continue
to be
> prompted for a username and password, which never authenticates (IP
address)
> and then I get the error:
> The network path \\computername\share could not be found. Does this
on
> shares and administrative shares. I must also mention that the shares
I use
> to have on the server are no longer there, so I am trying to recreate
the
> shares and they still will not map or open remotely.

We are having the same issue - 99% the same. I never found the resolution to
this in the Newsgroup. Was this ever resolved???

We'd really appreciate a resolution. Thanks.




"Junior" wrote:

> Thanks for the heads up on that procedure. Ideally I would hope to not have
> to go so far, however, if I should find myself in a bind, it may have to
> come to this. I have tried creating new shares on this server and still I
> am not able to produce a folder connection via a workstation.
>
> --R
>
> "Phillip Windell" <@.> wrote in message
> news:(E-Mail Removed)...
> > Well whatever you do don't remove it from the domain!!! Exchange 2003 is
> > tied to Active Directory so you don't want to "cut its throat". I'm not
> > sure about why it won't show on the LAN properly, maybe someone can help
> > get
> > that working.
> >
> > If you can get it to function partly correct, then as soon as possible I
> > would get exchange off that machine and get it rebuilt. You would want to
> > build an additional Exchange box with both Exchanges part of the same
> > "Exchange Site". Then use the "move mailbox" feature in Exchange to move
> > the
> > mail boxes to the new temporary Exchange.
> >
> > Once everything is safely moved use the proper proceedures to remove
> > Exchange from the box (don't just wipe the box). Once Exchange is off the
> > box, move it out of the Domain into its own workgroup,...rebuild
> > it,..re-join,...reinstall Exchange into the same "Exchange Site",...move
> > the
> > mailboxes back again. Then follow the proper steps to decommission the
> > temporary Exchange.
> >
> > Research it out and do it properly,..don't just start "clicking" with what
> > tiny amount of information I gave in this post.
> >
> > What I am describing is called the "Swing Server Method".
> >
> > How to upgrade to Exchange Server 2003 by using the swing upgrade method
> > http://support.microsoft.com/default...b;en-us;821896
> > --
> >
> > Phillip Windell [MCP, MVP, CCNA]
> > www.wandtv.com
> >
> >
> > "Junior" <(E-Mail Removed)> wrote in message
> > news:(E-Mail Removed)...
> >> Greetings,
> >>
> >> Last week I had a Win2K server (current on updates) fail to start a
> >> myriad
> >> of services after it started. Critical due to the fact that it would not
> >> start my Exchange 2000 services. Perplexed at what to do about this and
> >> noticing that my server was no longer viewable in the network
> > neighborhood,
> >> I was beginning to get concerned. I found that in the registry,
> >> particularly HKLM\System\CurrentControlSet\Services\ I had no
> > lanmanserver
> >> folder. All of my other servers had on and it appeared that this might
> >> be
> > a
> >> culprit. I read from an article about the Event code 7003 that to first
> > try
> >> and re run the latest service pack. When this did absolutely nothing, it
> >> gave the mention to copy a working server's registry entry for
> > lanmanserver
> >> and to copy and merge it into the affected computer. Right after then
> >> restart from doing that, Mail services and all other services started up
> >> without fail.
> >>
> >> HOWEVER: now the servers shares are lost and the server is still not
> >> present in network neighborhood. Nor is it accessible in trying to map a
> >> drive or even use an administrative share. Email still is working fine
> > and
> >> I can RDP to the server at will.
> >>
> >> What can I do to get the server back into the "neighborhood" It appears
> > not
> >> to want to broadcast or is broadcasting all wrong.
> >>
> >> Thanks in Advance and hope to hear back from someone soon.
> >>
> >> --
> >> Thank you for your time and attention to this matter,
> >>
> >> Robert Wisian Jr.
> >>
> >>
> >
> >
>
>
>