Yes or No

[Guest]

Should I make my home PC with XP Pro installed part of a domain to be-able to
connect to my work network (Server 2003). Should I lock-on "To This Computer"
or lock on to the Domain on home PC when I whant to connect to the work
network with (RDC).

Thanks in advance
Donovan

 

[Shenan Stanley]

Should I make my home PC with XP Pro installed part of a domain to
be-able to connect to my work network (Server 2003). Should I lock-on
"To This Computer" or lock on to the Domain on home PC when I whant
to connect to the work network with (RDC).

Unless your office (work) has been very restrictive on who can connect to
their domain resources - you gain very little by joining the domain with
your personal machine and they gain control of it in many ways.

You do not need to join a computer to a domain (in most cases) to access the
resources available - you just need to know your domain credentials and how
to access them through manual or scripted means (essentially - you need to
know the where/what and your username/password) - and you are in.

 

[Guest]

Thanks for your replay Shenan

I am responsible for the network at work. (I'm not a expert) 5 clients & 1
SBS 2003
server. all using xP Pro. I am trying to get the boss new pc @ home (XP Pro)
connected to his PC @ work. using http://xxx.xxx.xxx.xxx/remote I can connect
to outlook and read/send e-mail. I also see all the clients pc's and the
server, BUT can not connect to any of them. I will try disable the firewall
tomorrow and see what happens. (RDC) would not connect give error message.

Shenan do I need to install any thing before I setup/use RDC?

 

[Shenan Stanley]

Thanks for your replay Shenan

I am responsible for the network at work. (I'm not a expert) 5
clients & 1 SBS 2003
server. all using xP Pro. I am trying to get the boss new pc @ home
(XP Pro) connected to his PC @ work. using
http://xxx.xxx.xxx.xxx/remote I can connect to outlook and read/send
e-mail. I also see all the clients pc's and the server, BUT can not
connect to any of them. I will try disable the firewall tomorrow and
see what happens. (RDC) would not connect give error message.

Shenan do I need to install any thing before I setup/use RDC?

*If* the bosses machine has a publically accessible IP address, thenall you
need to do is open the Remote Desktop port (3389) through his Windows
Firewall.

*If* the bosses machine has a privately assigned IP address, then the proper
port must be forwarded through whatever setup you have to their machine.
The boss would then use the public IP address to access their machine.

Also - the boss must have an account on the machine that is a member of the
Remote Desktop Users group and must have a password assigned. It can be a
domain account - as long as that account is a member of the Remote Desktop
Users group - or a member of a group that is already a member of the RDU
group.

 

[Guest]

I will try this first

"*If* the bosses machine has a publically accessible IP address, thenall you
need to do is open the Remote Desktop port (3389) through his Windows
Firewall." All the client PC and the boss home PC use "Auto IP"

He is a RDU member. I'm not sure but I think he has Remote Desktop enable in
his Firewall. I 1st had his pc connected to the network at work before i took
it to his home. It worked fine when it was connected to the LAN. The Firewall
is grayed out and I could not disable it to do a test yesterday. If RD port
3389 is open I would disable the Firewall (using Group Policy) in order to do
a test.

Do I need Connection Manager, and where do I get it. I used sbspackage.exe
not sure if it worked.