Re: win98 clients cant connect after sbs4.0 to sbs2003 migration
anonymous_at_discussions.microsoft.com
Date: 04/13/04
- Next message: Dunbar: "Access to folders denied/Group Policy"
- Previous message: Arttu: "Can't install additional printer driver for NT client"
- In reply to: MCLTECH: "Re: win98 clients cant connect after sbs4.0 to sbs2003 migration"
- Next in thread: Mal Osborne: "Re: win98 clients cant connect after sbs4.0 to sbs2003 migration"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 13 Apr 2004 07:18:03 -0700
I had the same issues.
I looked in the Wins Table and had some wierd machines
saying they were owning the domain. I deleted all of
those and waited a while everything was Ok after that.
I also loaded the DS client everywhere to be safe and all
has been ok since
>-----Original Message-----
>Jon
>
>I had one similar situation - and using the DSCLIENT
worked - eliminated the
>problem. Couldn't figure out what was wrong, took out
the old NT 4.0 server
>and only already mapped drives would connect, put the NT
4 member server
>back in and communication was OK.
>
>Did the DSCLIENT and threw the NT 4 out for good.
>
>Cal
>
>"Jon Skelley" <jskelley@cfanetworks.com> wrote in message
>news:1b9bb01c42106$02d10670$a501280a@phx.gbl...
>> My customer was running SBS 4.0 and I had to migrate
them
>> to SBS2003. The migration went rather smoothly until I
>> tried to get the windows 98 clients to connect. On a
>> win98 client I changed the workgroup name to the new
>> domain name and then I changed the Client for MS to the
>> new domain name. Once the 98 machine rebooted I logged
>> into the new domain. I was prompted for a new password
>> since the migration set the password to expire. Once I
>> did this I received an error saying that the device was
>> not on the network. I could not change the password.
>> So, I logged on as administrator to at least see if the
>> rest would work. I opened network neighborhood and the
>> only thing listed was "Entire Network" and if I clicked
>> on it I received an error that I could not browse the
>> network.
>> I have tried a static IP address and pointing WINS to
the
>> new server. I tried uninstalling all network protocols
>> and clients and then reinstalling. Same result. This
>> happened on 3 different win98 clients. The strange
thing
>> is if I change the domain names back to the old
domain, I
>> can now browse the network and see all the PCs.
>>
>> I have tried only connecting one client and the new
>> server and trying the same tests and get the same
>> result.
>>
>> I have looked on the PC in the registry for the old
>> server name and domain but I cant find anything. I
have
>> looked through to see if there is a SBS client or
>> something forcing it to use the old domain name but I
>> cant find anything.
>>
>> If I leave the new server connected to the network but
>> the clients are still pointing to the old server, I can
>> see the new domain but when I click on it I get an
error
>> saying that I dont have access. The thing is that I
can
>> browse directly to the new server.
>>
>> Could this possibly be that I need to install the
Active
>> Directory client on these PCs? I have never seen
where a
>> 98 machine will only browse the network if a specific
>> domain name is used.
>>
>> Jon Skelley
>
>
>.
>
- Next message: Dunbar: "Access to folders denied/Group Policy"
- Previous message: Arttu: "Can't install additional printer driver for NT client"
- In reply to: MCLTECH: "Re: win98 clients cant connect after sbs4.0 to sbs2003 migration"
- Next in thread: Mal Osborne: "Re: win98 clients cant connect after sbs4.0 to sbs2003 migration"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
