Server Migration and Browsing Issues

  • Thread starter Thread starter celcius233
  • Start date Start date
C

celcius233

Guest
Hello All.

We're migrating our old servers (Win 2003 SP2) to Dell PowerEdge boxes (same
OS). Last night we moved our entire file server, updated login scripts via
group policy, and did the cut over.

The box we moved our data from was the first server in our domain and is a
DC running DHCP and DNS. It is now ONLY performing those roles (we're a very
small business and couldn't afford to split the services). We duplicated the
directory structure on the new box, however it is NOT a DC, only a member
server with much more horsepower.

From the user perspective everything is fine. They can access all their
files, our backups are good, etc.

However, on all of our servers the old drive mapping for the original server
is still showing up when exploring. Get this: It "says" the drive is mapped
to the old server, however in actuality it's pointing to the new server. We
disconnect the drive and try to re-map it with the new information - same
result. Old server/share name, new server in reality.

In the event logs we're seeing Event ID #8032 Source: Browser - "The browser
has failed to retrieve the backup list too many times"

I tried turning off DNS and stopping/starting the Computer Browser service
on the box in question, however this did not resolve. We're still seeing the
issue.

Any thoughts?
 
Re: Server Migration and Browsing Issues

"celcius233" <celcius233@discussions.microsoft.com> wrote in message
news:9AB84500-F71D-4955-B696-54AF212472AC@microsoft.com...

> In the event logs we're seeing Event ID #8032 Source: Browser - "The
> browser
> has failed to retrieve the backup list too many times"

Event log on what server?

> I tried turning off DNS and stopping/starting the Computer Browser service
> on the box in question, however this did not resolve. We're still seeing
> the
> issue.

DNS on what server? If this is not the DC, then remove DNS from the box.
The machine needs to point to the DC for DNS and nothing else.

Disable the Windows Firewall on the Servers. It will cause problems with the
network browser system.

> However, on all of our servers the old drive mapping for the original
> server
> is still showing up when exploring. Get this: It "says" the drive is
> mapped
> to the old server, however in actuality it's pointing to the new server.
> We
> disconnect the drive and try to re-map it with the new information - same
> result. Old server/share name, new server in reality.

Why are you even using "drive mappings"? That was fine during the days of
Novel when Dinosaurs roamed the earth, but they are inefficient,
undependable, and are resource hogs because they need to maintain a constant
connection or they have to keep reconnecting on-demand if they time out
which is always "iffy".

Use network Shortcuts. Just use one one shortcut for the whole file
server,...the shares on the server will show from that point and the users
can go where they want.

To avoid future problems when/if the machine is ever replaced again use a
CNAME in DNS or a Static WINS entry that point to a fake name like
"FileServer" and then based the shortcut off of that name. If the server
ever gets replaced just re-point the CNAME to the new server or correct to
the Static WINS entry to the new IP#, this way you keep using the same name
in the Shortcut to get where you are going no matter what.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------
 
Re: Server Migration and Browsing Issues

Why don't you just DCPROMO the old machine & make sure the login scripts
point to the new shares on the new server? If you have AD & DNS on the new
box & the global catalog/roles are on the new machine then why bother with
the existing box?

When you replicated you updated the schema I guess to 31 (2003 R2) & not
left it at 30 (2003 1st release) because it would have caused problems

"Phillip Windell" wrote:

> "celcius233" <celcius233@discussions.microsoft.com> wrote in message
> news:9AB84500-F71D-4955-B696-54AF212472AC@microsoft.com...
>
> > In the event logs we're seeing Event ID #8032 Source: Browser - "The
> > browser
> > has failed to retrieve the backup list too many times"
>
> Event log on what server?
>
> > I tried turning off DNS and stopping/starting the Computer Browser service
> > on the box in question, however this did not resolve. We're still seeing
> > the
> > issue.
>
> DNS on what server? If this is not the DC, then remove DNS from the box.
> The machine needs to point to the DC for DNS and nothing else.
>
> Disable the Windows Firewall on the Servers. It will cause problems with the
> network browser system.
>
> > However, on all of our servers the old drive mapping for the original
> > server
> > is still showing up when exploring. Get this: It "says" the drive is
> > mapped
> > to the old server, however in actuality it's pointing to the new server.
> > We
> > disconnect the drive and try to re-map it with the new information - same
> > result. Old server/share name, new server in reality.
>
> Why are you even using "drive mappings"? That was fine during the days of
> Novel when Dinosaurs roamed the earth, but they are inefficient,
> undependable, and are resource hogs because they need to maintain a constant
> connection or they have to keep reconnecting on-demand if they time out
> which is always "iffy".
>
> Use network Shortcuts. Just use one one shortcut for the whole file
> server,...the shares on the server will show from that point and the users
> can go where they want.
>
> To avoid future problems when/if the machine is ever replaced again use a
> CNAME in DNS or a Static WINS entry that point to a fake name like
> "FileServer" and then based the shortcut off of that name. If the server
> ever gets replaced just re-point the CNAME to the new server or correct to
> the Static WINS entry to the new IP#, this way you keep using the same name
> in the Shortcut to get where you are going no matter what.
>
> --
> Phillip Windell
> www.wandtv.com
>
> The views expressed, are my own and not those of my employer, or Microsoft,
> or anyone else associated with me, including my cats.
> -----------------------------------------------------
>
>
>
 
Back
Top