Directory Services Client

  • Thread starter Thread starter Gil Davis
  • Start date Start date
G

Gil Davis

I installed this on my Windows 95 machine, and now it
won't work. It hangs after the log-in screen. Task Manager
reports MPREXE (not responding), and I can't end the task
or shut down.

I cannot find instructions to uninstall the DSCLIENT.
There is a hot-fix listed for DSCLIENT, but I cannot find
a download link.
 
Gil Davis said:
I installed this on my Windows 95 machine, and now it
won't work. It hangs after the log-in screen. Task Manager
reports MPREXE (not responding), and I can't end the task
or shut down.

I cannot find instructions to uninstall the DSCLIENT.
There is a hot-fix listed for DSCLIENT, but I cannot find
a download link.
Click to expand...

One thing that would affect the client is if you have your ISP's DNS
settings in the Win9x machine, since the client is trying to find AD by
querying DNS. You need to point it only to your internal DNS servers. BTW-
this is important for all your AD machines. IIRC, it's installed under
Network properties in Win9x, but can't remember exactly, it's been about 3
years since I used it. Here's some links for you:

249841 - INFO How Windows 95 and Windows 98 Directory Services Client Uses
Active Directory Site Information:
http://support.microsoft.com/?id=249841

The update:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;323466

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
-----Original Message-----


One thing that would affect the client is if you have your ISP's DNS
settings in the Win9x machine, since the client is trying to find AD by
querying DNS.
Click to expand...

I connect to my ISP using a dial-up adapter (DUN 1.3). I
have a 3rd party ICS program (Internet LanBridge) that
shares this connection to other computers using NetBEUI.
My W2K server is both AD and DNS. My NIC's TCP/IP
properties specify the DNS server address.

My system's hard drive is removable (mobile rack), and I
use two different drives to switch between W95 and W98.
The W98 installation appears to function, but the W95 does
not (there are complicated reasons for my madness ;-)).
The TCP/IP settings are identical.
You need to point it only to your internal DNS servers. BTW-
this is important for all your AD machines. IIRC, it's installed under
Network properties in Win9x, but can't remember exactly, it's been about 3
years since I used it. Here's some links for you:

249841 - INFO How Windows 95 and Windows 98 Directory Services Client Uses
Active Directory Site Information:
http://support.microsoft.com/?id=249841

The update:
http://support.microsoft.com/default.aspx?scid=kb;EN- US;323466
Click to expand...
Thank you for the reply. I have been to the update link,
and there is no update file there to be downloaded. It
says that I have to contact MS directly for the hotfix.

The other link was enlightening. It leads me to believe
that neither installation (W98 or W95) *should* work
because of NetBEUI.

No matter what I do to the W95 installation, I
cannot "see" the W2K server in Network Neighborhood.
However, I can successfully search for people in AD. Weird.

The W2K server is in my basement, and the W9x machine is
in the dining room. The W9x machine hosts a printer and
the dial-up.

The W95 version shares the dial-up for both internet and
fax, and also shares the printer. I can get to the printer
ove NetBEUI, but not over TCP/IP. It seems like the TCP/IP
is not right. I can ping all the machines, but Network
Neighborhood is barren except for the W95 machine in its
workgroup.

The W98 version shares the dial-up for internet, but fax
sharing does not work (never did, that's one reason for
keeping the W95). The printer share is fine. Network
Neighborhood shows the W2K server in the W2K domain, and
shows the W98 machine in a workgroup.

Perhaps I expect too much?

I am a recent MCP (70-215 installation, administration W2K
server) working towards MCDBA.
 
-----Original Message-----
One thing that would affect the client is if you have your ISP's DNS
settings in the Win9x machine, since the client is trying to find AD by
querying DNS.
Click to expand...

I connect to my ISP using a dial-up adapter (DUN 1.3). I
have a 3rd party ICS program (Internet LanBridge) that
shares this connection to other computers using NetBEUI.
My W2K server is both AD and DNS. My NIC's TCP/IP
properties specify the DNS server address.

My system's hard drive is removable (mobile rack), and I
use two different drives to switch between W95 and W98.
The W98 installation appears to function, but the W95 does
not (there are complicated reasons for my madness ;-)).
The TCP/IP settings are identical.
You need to point it only to your internal DNS servers. BTW-
this is important for all your AD machines. IIRC, it's installed under
Network properties in Win9x, but can't remember exactly, it's been about 3
years since I used it. Here's some links for you:

249841 - INFO How Windows 95 and Windows 98 Directory Services Client Uses
Active Directory Site Information:
http://support.microsoft.com/?id=249841

The update:
http://support.microsoft.com/default.aspx?scid=kb;EN- US;323466
Click to expand...
Thank you for the reply. I have been to the update link,
and there is no update file there to be downloaded. It
says that I have to contact MS directly for the hotfix.

The other link was enlightening. It leads me to believe
that neither installation (W98 or W95) *should* work
because of NetBEUI.

No matter what I do to the W95 installation, I
cannot "see" the W2K server in Network Neighborhood.
However, I can successfully search for people in AD. Weird.

The W2K server is in my basement, and the W9x machine is
in the dining room. The W9x machine hosts a printer and
the dial-up.

The W95 version shares the dial-up for both internet and
fax, and also shares the printer. I can get to the printer
ove NetBEUI, but not over TCP/IP. It seems like the TCP/IP
is not right. I can ping all the machines, but Network
Neighborhood is barren except for the W95 machine in its
workgroup.

The W98 version shares the dial-up for internet, but fax
sharing does not work (never did, that's one reason for
keeping the W95). The printer share is fine. Network
Neighborhood shows the W2K server in the W2K domain, and
shows the W98 machine in a workgroup.

Perhaps I expect too much?

I am a recent MCP (70-215 installation, administration W2K
server) working towards MCDBA.
 
In
Gil Davis said:
I connect to my ISP using a dial-up adapter (DUN 1.3). I
have a 3rd party ICS program (Internet LanBridge) that
shares this connection to other computers using NetBEUI.
My W2K server is both AD and DNS. My NIC's TCP/IP
properties specify the DNS server address.

My system's hard drive is removable (mobile rack), and I
use two different drives to switch between W95 and W98.
The W98 installation appears to function, but the W95 does
not (there are complicated reasons for my madness ;-)).
The TCP/IP settings are identical.

Thank you for the reply. I have been to the update link,
and there is no update file there to be downloaded. It
says that I have to contact MS directly for the hotfix.

The other link was enlightening. It leads me to believe
that neither installation (W98 or W95) *should* work
because of NetBEUI.

No matter what I do to the W95 installation, I
cannot "see" the W2K server in Network Neighborhood.
However, I can successfully search for people in AD. Weird.

The W2K server is in my basement, and the W9x machine is
in the dining room. The W9x machine hosts a printer and
the dial-up.

The W95 version shares the dial-up for both internet and
fax, and also shares the printer. I can get to the printer
ove NetBEUI, but not over TCP/IP. It seems like the TCP/IP
is not right. I can ping all the machines, but Network
Neighborhood is barren except for the W95 machine in its
workgroup.

The W98 version shares the dial-up for internet, but fax
sharing does not work (never did, that's one reason for
keeping the W95). The printer share is fine. Network
Neighborhood shows the W2K server in the W2K domain, and
shows the W98 machine in a workgroup.

Perhaps I expect too much?

I am a recent MCP (70-215 installation, administration W2K
server) working towards MCDBA.
Click to expand...

Good luck in your endeavors.
From what I see, maybe in W95, you might have File and Print Sharing
disabled?

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
From what I see, maybe in W95, you might have File and
Print Sharing
disabled?
Click to expand...

No. I have them unbound from the Dialup adapter, but they
are there.

I have been uninstalling things one at a time trying to
figure out who is trying to dial out when I hit enter at
the "Log In To Microsoft Network". Sometimes I see

MPREXE (not responding)

along with

RNAAPP

in Task Manager. I just don't understand why it wants to
dial out. Do you know what it is looking for?

Thanks for the response.
 
I have discovered that the Internet LanBridge hijacks the
TCP/IP by replacing the winsock file with its own. There
is a small side note in their documentation that I
overlooked that says you can use NetBEUI or IPX/SPX to
network between PCs but it does not support TCP/IP between
PCs.

So, I won't be able to make the W95 work as a TCP/IP
client anyway. It won't be able to support the XP machine
for print sharing, since XP does not support NetBEUI (I
don't see any point in trying IPX/SPX).

Looks like my best solution would be to set up an old PC
to support sharing the dial-up and fax running W95, talk
to it with NetBEUI (too bad, XP!), not have it participate
in the AD and leave it on all the time.
 
In
Gil Davis said:
I have discovered that the Internet LanBridge hijacks the
TCP/IP by replacing the winsock file with its own. There
is a small side note in their documentation that I
overlooked that says you can use NetBEUI or IPX/SPX to
network between PCs but it does not support TCP/IP between
PCs.

So, I won't be able to make the W95 work as a TCP/IP
client anyway. It won't be able to support the XP machine
for print sharing, since XP does not support NetBEUI (I
don't see any point in trying IPX/SPX).

Looks like my best solution would be to set up an old PC
to support sharing the dial-up and fax running W95, talk
to it with NetBEUI (too bad, XP!), not have it participate
in the AD and leave it on all the time.
Click to expand...

Well, glad you figured it out. Sometimes it may be better to go with a newer
OS to handle this stuff. Have you considered an inexpensive Linksys router
for this purpose?

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
-----Original Message-----
In Gil Davis <[email protected]> posted their thoughts, then
I offered mine

Well, glad you figured it out. Sometimes it may be better to go with a newer
OS to handle this stuff. Have you considered an inexpensive Linksys router
for this purpose?

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
--
=================================


.
Click to expand...
I started down that path with a Siemens DSL router that
has a dial-up backup feature and print server, thinking I
could fool it into dialing on demand since I don't have
DSL. I never could get the dial-up to only dial on demand,
even though the docs said it would. Maybe I'll look into
it again, or into the Linksys.

I have access to my neighbor's DSL through a wireless NIC,
but I need to use the dial up to get my e-mail. My ISP
does not seem to accept foreign domain access of their
mail services.
 
In
Gil Davis said:
I started down that path with a Siemens DSL router that
has a dial-up backup feature and print server, thinking I
could fool it into dialing on demand since I don't have
DSL. I never could get the dial-up to only dial on demand,
even though the docs said it would. Maybe I'll look into
it again, or into the Linksys.

I have access to my neighbor's DSL through a wireless NIC,
but I need to use the dial up to get my e-mail. My ISP
does not seem to accept foreign domain access of their
mail services.
Click to expand...

I see, the plot thickens. :-)

I used to be able to get my mail thru outside providers, but sending was a
problem until I checked that the server requires authentication to send
mail. Not sure if this will help.

Usually a dialup or VPN will establish a connection once a request is
queried or an attempt to connect to a resource that is not on the network.
Try making it the default connection in Win95. That would be in Network
Properties under the TCP/IP dialup connection entry (that's if I remember
correctly).


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
I see, the plot thickens. :-)

I used to be able to get my mail thru outside providers, but sending was a
problem until I checked that the server requires authentication to send
mail. Not sure if this will help.

Usually a dialup or VPN will establish a connection once a request is
queried or an attempt to connect to a resource that is not on the network.
Try making it the default connection in Win95. That would be in Network
Properties under the TCP/IP dialup connection entry (that's if I remember
correctly).
Click to expand...
It already is the default (only) dial-up, if that is what
you mean. I think perhaps part of the problem lies in the
fact that the dial-up connection has a user name and a
password that is not the same as my e-mail account user
name and password (I can have up to 5 e-mail accounts). So
there seems to be two layers. Does that sound likely?

This discussion is getting pretty far afield from
Directory Services and W2000. Maybe I should take
it "outside". What group would you suggest?

I appreciate your help and insight.

Gil
 
In
Gil Davis said:
It already is the default (only) dial-up, if that is what
you mean. I think perhaps part of the problem lies in the
fact that the dial-up connection has a user name and a
password that is not the same as my e-mail account user
name and password (I can have up to 5 e-mail accounts). So
there seems to be two layers. Does that sound likely?
Click to expand...

Not really, since the Internet email account that you create in your email
program would need the user/pass and SMTP/POP3 servers entered. They can
(and usually are) different.
This discussion is getting pretty far afield from
Directory Services and W2000. Maybe I should take
it "outside". What group would you suggest?
Click to expand...

Well, hopefully this would take care of it. You can post to the Win95 and/or
Win98 newsgroups (I think there's a
"microsoft.public.win95.dailupnetworking" and networking group too). I would
also suggest to upgrade to Dialup Netoworking 1.2 (DUN 1.2 or better) for
Win95. That may take care of some of the problems, if you haven;'t yet.
Maybe that's the difference between your 98 machine working and this one not
working. That's available free on MS site.
I appreciate your help and insight.

Gil
Click to expand...

Hope it helps.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Back
Top