Connection lost since upgrade to 2003

[Connection Lost]

I have/had two NT4 domain controllers in my network. I
have a W98 client which has a network share on it and
access to this share is acheived via domain groups (via
the access control functionality in W98). This all
worked great until I upgraded the domain controller to
2003. Now users who should be able to connect to this
share on the W98 client often can not without a reboot of
this W98 machine. Once rebooted it works for a while
and then quits. I looked at this W98 machine when this
is happening and discovered that during this time the W98
machine can not browse/access the newly upgraded 2003
server (in particular the netlogon or sysvol shares).
Once rebooted all is well again (for a while). I have
done a little more investigating and discovered that
similar things are happening on almost all 98 machines
(they lose connection to 2003 server after a while).
It is apparent that the W98 clients can talk to the 2003
domain controller but are eventually losing this
connection. Any answer to fixing this? Also, once I
upgrade the other domain controller (BDC) from NT4 to
2003, should I expect this problem to go away or get
worse?

[Doug Sherman [MVP]]

Probably this is an SMB signing or other down-level client issue. If you
have not done so, try installing the dsclient on the Win98 machines. For
other work arounds - See:

[url]http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/deployguide/en-us/Default.asp?url=/resources/documentation/windowsserv/2003/all/deployguide/en-us/dssbe_upnt_huxa.asp[/url]

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

"Connection Lost" <homerskij@conemaugh.org> wrote in message
news:23f2d01c45f72$0c868730$a601280a@phx.gbl...

> I have/had two NT4 domain controllers in my network. I
> have a W98 client which has a network share on it and
> access to this share is acheived via domain groups (via
> the access control functionality in W98). This all
> worked great until I upgraded the domain controller to
> 2003. Now users who should be able to connect to this
> share on the W98 client often can not without a reboot of
> this W98 machine. Once rebooted it works for a while
> and then quits. I looked at this W98 machine when this
> is happening and discovered that during this time the W98
> machine can not browse/access the newly upgraded 2003
> server (in particular the netlogon or sysvol shares).
> Once rebooted all is well again (for a while). I have
> done a little more investigating and discovered that
> similar things are happening on almost all 98 machines
> (they lose connection to 2003 server after a while).
> It is apparent that the W98 clients can talk to the 2003
> domain controller but are eventually losing this
> connection. Any answer to fixing this? Also, once I
> upgrade the other domain controller (BDC) from NT4 to
> 2003, should I expect this problem to go away or get
> worse?

[Eric the IT Novice]

I was thinking it was a WINS issue, but there are more
knowledgeable people on these forums than me.

>-----Original Message-----
>Probably this is an SMB signing or other down-level

client issue. If you

>have not done so, try installing the dsclient on the

Win98 machines. For

>other work arounds - See:
>
>[url]http://www.microsoft.com/resources/documentation/WindowsSe[/url]

rv/2003/all/deployguide/en-us/Default.asp?
url=/resources/documentation/windowsserv/2003/all/deploygui
de/en-us/dssbe_upnt_huxa.asp

>
>Doug Sherman
>MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
>
>"Connection Lost" <homerskij@conemaugh.org> wrote in

message

>news:23f2d01c45f72$0c868730$a601280a@phx.gbl...

>> I have/had two NT4 domain controllers in my network. I
>> have a W98 client which has a network share on it and
>> access to this share is acheived via domain groups (via
>> the access control functionality in W98). This all
>> worked great until I upgraded the domain controller to
>> 2003. Now users who should be able to connect to this
>> share on the W98 client often can not without a reboot

of

>> this W98 machine. Once rebooted it works for a while
>> and then quits. I looked at this W98 machine when

this

>> is happening and discovered that during this time the

W98

>> machine can not browse/access the newly upgraded 2003
>> server (in particular the netlogon or sysvol shares).
>> Once rebooted all is well again (for a while). I have
>> done a little more investigating and discovered that
>> similar things are happening on almost all 98 machines
>> (they lose connection to 2003 server after a while).
>> It is apparent that the W98 clients can talk to the 2003
>> domain controller but are eventually losing this
>> connection. Any answer to fixing this? Also, once

I

>> upgrade the other domain controller (BDC) from NT4 to
>> 2003, should I expect this problem to go away or get
>> worse?

>
>
>.
>

[Doug Sherman [MVP]]

Could be - but the intermitent nature of the problem is puzzling. A
possible fix would be an lmhosts file pointing to the PDC/Master Browser -
See:

[url]http://support.microsoft.com/default.aspx?scid=kb;en-us;314108[/url]

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

"Eric the IT Novice" <anonymous@discussions.microsoft.com> wrote in message
news:2426401c45f90$ed234ee0$a601280a@phx.gbl...

> I was thinking it was a WINS issue, but there are more
> knowledgeable people on these forums than me.
>
>

> >-----Original Message-----
> >Probably this is an SMB signing or other down-level

> client issue. If you

> >have not done so, try installing the dsclient on the

> Win98 machines. For

> >other work arounds - See:
> >
> >[url]http://www.microsoft.com/resources/documentation/WindowsSe[/url]

> rv/2003/all/deployguide/en-us/Default.asp?
> url=/resources/documentation/windowsserv/2003/all/deploygui
> de/en-us/dssbe_upnt_huxa.asp

> >
> >Doug Sherman
> >MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
> >
> >"Connection Lost" <homerskij@conemaugh.org> wrote in

> message

> >news:23f2d01c45f72$0c868730$a601280a@phx.gbl...

> >> I have/had two NT4 domain controllers in my network. I
> >> have a W98 client which has a network share on it and
> >> access to this share is acheived via domain groups (via
> >> the access control functionality in W98). This all
> >> worked great until I upgraded the domain controller to
> >> 2003. Now users who should be able to connect to this
> >> share on the W98 client often can not without a reboot

> of

> >> this W98 machine. Once rebooted it works for a while
> >> and then quits. I looked at this W98 machine when

> this

> >> is happening and discovered that during this time the

> W98

> >> machine can not browse/access the newly upgraded 2003
> >> server (in particular the netlogon or sysvol shares).
> >> Once rebooted all is well again (for a while). I have
> >> done a little more investigating and discovered that
> >> similar things are happening on almost all 98 machines
> >> (they lose connection to 2003 server after a while).
> >> It is apparent that the W98 clients can talk to the 2003
> >> domain controller but are eventually losing this
> >> connection. Any answer to fixing this? Also, once

> I

> >> upgrade the other domain controller (BDC) from NT4 to
> >> 2003, should I expect this problem to go away or get
> >> worse?

> >
> >
> >.
> >