remote desktop from win95 to xp on an nt network

[bobr]

I have been dialing in to my pc and a server sucessfully
for some time. I have win95 at home and had an nt 4.0 pc at
work on an NT domain. I got a new pc at work with win xp
and have copied desktop on to my home pc as recommended. I
took the modem from my old machine and put it in the new
one. I can still dial in to the nt server that I could
dial into before, but when I dial into my new pc, the modem
picks up and it looks like I am being connected, but the
session is terminated in about 30 seconds. Also, rather
than getting prompted to log on to a server, I get prompted
to log on to the domain, twice more. If I cancel out both
or complete the two additional logins, the session still
gets terminated.

Also, before I was using batch files to turn RAS service
off at 7:00 and on at 17:00 on M, T, W, Th and F, and then
the RAS would stay up all weekend. With the new scheduling
wizard, I cant seem to do this with RRAS. The modem wants
to pick up when the phone rings even if I use the batch
files and tell it to start on a monday, using a weekly
schedule.

any suggestions for either problem would be great

 

[Bill Sanderson]

I've heard good feedback when I've suggested net stop remoteaccess and net
start remoteaccess as appropriate batch commands to start and stop RAS from
answering the phone on XP PRo. These can be put in .CMD files and scheduled
using either command-line or gui scheduler.

On the first issue, I'm far less sure of my ground. When you dial into the
NT4 server, what kind of connection is this? Any chance you can then simply
RD to the XP machine via that connection? Possible glitches: Nt4 may not
be set up to allow IP connections from the outside world--that wasn't the
default when it was created. It's perfectly possible--I've run all IP NT4
domains including VPN and dialup access--but your network may not be so
arranged.

I've never tried exactly what you are trying to do with an XP machine on an
NT domain. If this were a Windows 2000 domain, I would wonder about either
AD dial-in permissions on the domain user account, or policy settings of
some sort--but those should never have allowed the login to happen.

Any clues from the event logs on either the XP machine or the NT domain
controller?

You can respond to the login prompt with a local user, and the machine name
as domain. I think for network access, an account with a password is the
requirement. For RD access, the account must be an administrator or a
member of the remote desktop users group (start, run, control userpasswords2
<enter> advanced tab, advanced button
(this is also available via the gui in properties of My Computer, remote
tab)

I'm not sure I have useful thoughts about the authentication issue, but
maybe my musings will prompt some from you?