new server with WS2003

We just installed a new server at our church with Windows
Server 2003 OS. The old server died a slow death and is
not available to tranfer any files to the new server.
The old server operated on WinNT. We used the old domain
name on the new server. Once it was up, the work station
of course couldn't find the LAN. In order for the stations
to see the new server, we manually went to a few
workstations and switched them from the domain to a
WORKGROUP, then back to the domain name. We also went into
IPCONFIG, RELEASE AND RENEW in order for them to find the
new DNS address. The W2000 stations went smooth, but the
W98 still can't find the new server.
Is there an easier/faster way to set up the stations
(2000, XP, and 98) to find the new server-without
configuring each machine manually?
We will also have to configure over 50 machines in our
school.
Thanks for any help. If you need more info, please let me
know and I'll give more facts.

Phil

If you are using a single level domain name, you likely to have problwems.
See

http://support.microsoft.com/default...b;EN-US;300684

In any case, for the Win98 clients, install the dsclient from the server CD.
Also, an lmhosts file may help. See:

http://support.microsoft.com/default...b;en-us;314108

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP

"Phil" <(E-Mail Removed)> wrote in message
news:26e6301c46247$a4de03f0$(E-Mail Removed)...
> We just installed a new server at our church with Windows
> Server 2003 OS. The old server died a slow death and is
> not available to tranfer any files to the new server.
> The old server operated on WinNT. We used the old domain
> name on the new server. Once it was up, the work station
> of course couldn't find the LAN. In order for the stations
> to see the new server, we manually went to a few
> workstations and switched them from the domain to a
> WORKGROUP, then back to the domain name. We also went into
> IPCONFIG, RELEASE AND RENEW in order for them to find the
> new DNS address. The W2000 stations went smooth, but the
> W98 still can't find the new server.
> Is there an easier/faster way to set up the stations
> (2000, XP, and 98) to find the new server-without
> configuring each machine manually?
> We will also have to configure over 50 machines in our
> school.
> Thanks for any help. If you need more info, please let me
> know and I'll give more facts.
>
> Phil

"you likely to have problwems"

OK, it was 1:00 AM - and yes, there was beer at the cookout.

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP

"Doug Sherman [MVP]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> If you are using a single level domain name, you likely to have problwems.
> See
>
> http://support.microsoft.com/default...b;EN-US;300684
>
> In any case, for the Win98 clients, install the dsclient from the server
CD.
> Also, an lmhosts file may help. See:
>
> http://support.microsoft.com/default...b;en-us;314108
>
> Doug Sherman
> MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
>
> "Phil" <(E-Mail Removed)> wrote in message
> news:26e6301c46247$a4de03f0$(E-Mail Removed)...
> > We just installed a new server at our church with Windows
> > Server 2003 OS. The old server died a slow death and is
> > not available to tranfer any files to the new server.
> > The old server operated on WinNT. We used the old domain
> > name on the new server. Once it was up, the work station
> > of course couldn't find the LAN. In order for the stations
> > to see the new server, we manually went to a few
> > workstations and switched them from the domain to a
> > WORKGROUP, then back to the domain name. We also went into
> > IPCONFIG, RELEASE AND RENEW in order for them to find the
> > new DNS address. The W2000 stations went smooth, but the
> > W98 still can't find the new server.
> > Is there an easier/faster way to set up the stations
> > (2000, XP, and 98) to find the new server-without
> > configuring each machine manually?
> > We will also have to configure over 50 machines in our
> > school.
> > Thanks for any help. If you need more info, please let me
> > know and I'll give more facts.
> >
> > Phil
>
>

Thanks for the help, Doug. Sounds like the cookout was fun!
>-----Original Message-----
>"you likely to have problwems"
>
>OK, it was 1:00 AM - and yes, there was beer at the
cookout.
>
>Doug Sherman
>MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
>
>"Doug Sherman [MVP]" <(E-Mail Removed)>
wrote in message
>news:(E-Mail Removed)...
>> If you are using a single level domain name, you likely
to have problwems.
>> See
>>
>> http://support.microsoft.com/default.aspx?scid=kb;EN-
US;300684
>>
>> In any case, for the Win98 clients, install the
dsclient from the server
>CD.
>> Also, an lmhosts file may help. See:
>>
>> http://support.microsoft.com/default.aspx?scid=kb;en-
us;314108
>>
>> Doug Sherman
>> MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
>>
>> "Phil" <(E-Mail Removed)> wrote in
message
>> news:26e6301c46247$a4de03f0$(E-Mail Removed)...
>> > We just installed a new server at our church with
Windows
>> > Server 2003 OS. The old server died a slow death and
is
>> > not available to tranfer any files to the new server.
>> > The old server operated on WinNT. We used the old
domain
>> > name on the new server. Once it was up, the work
station
>> > of course couldn't find the LAN. In order for the
stations
>> > to see the new server, we manually went to a few
>> > workstations and switched them from the domain to a
>> > WORKGROUP, then back to the domain name. We also went
into
>> > IPCONFIG, RELEASE AND RENEW in order for them to find
the
>> > new DNS address. The W2000 stations went smooth, but
the
>> > W98 still can't find the new server.
>> > Is there an easier/faster way to set up the stations
>> > (2000, XP, and 98) to find the new server-without
>> > configuring each machine manually?
>> > We will also have to configure over 50 machines in our
>> > school.
>> > Thanks for any help. If you need more info, please
let me
>> > know and I'll give more facts.
>> >
>> > Phil
>>
>>
>
>
>.
>