Re: RDP to internal client machine?
- From: "Steve" <newsgroup@xxxxxxxxxx>
- Date: Wed, 23 May 2007 09:41:05 -0700
You're really complicating things. As Cris says use RWW.
"Blake" <Blake@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:DBBC9E53-647B-48FC-A376-7DE980AA3962@xxxxxxxxxxxxxxxx
I've got a SBS2003 setup on a small domain in our office with about 6
networked XP Pro Computers and a few printers, etc.
We've got internet access through a single NIC and a 2Wire DSL
Modem/Router/Gateway. But, have got DHCP controlled through the SBS2003
box.
Have the router successfully setup to allow VPN to the server, some other
activites (Synching ACT to the databases) and can successfully RDP to the
server (I actually manage most of it remotely.) When needed, i've been
able
to then RDP to other computers within the network, but then comes very
slow
(RDP -> RDP) and uses up one of the RDP connections on the server (there's
two of us that RDP to the server so want to keep it as open as possible.)
I'm attempting to get a straight RDP connection to ONE of the client
machines within the network (The boss, who's out alot, needs access, etc.)
I
don't need it on all (though would be nice) but just this one specific
computer (in addition to the server, which I already have.)
I've used the recommendations on Geek.com for setting up RDP through a
modem/router on a few instances (my own home, office, and in other
"workgroup" situations) and I love it - works well.
http://www.geek.com/news/geeknews/2003Aug/fea20030828021469.htm
I've even done multiple machines within the same workgroup by following
his
"manually fix a specific machine IP address and then regedit the port
number
that RDP listens on." to connect to more than one computer on the same
network. (When connecting, add the port number after a colon I.e.
58.176.25.55:3390)
But, i'm having problems configuring on this SBS setup. All client
machines
are Auto Config DHCP from the server. But, on the said client, i've
manually
setup IP address, DNS servers, etc. All internet access etc. still works
on
machine - all is good from within. I've then setup the router/modem to
Port
Forward 3390 to the IP address of the said machine. (The default 3389
still
works to the server too). After many tries, i still can't connect from the
outside.
I'm also having intermittent problems, now, connecting to the client
machine
from within the network via RDP from the server. At first, the machine
name
was unrecognizable, but i added the server to the WINS address. Before
that,
I could RDP by IP address. Yesterday, couldn't connect again and found
out
that the McAfee local firewall was blocking stuff (though I had it enabled
to
pass through both Ports 3389 and 3390 just in case) Thogh the WinXP
firewall
is locked down via domain settings. I was succesffull at one point to
connet
from the server w/o issue, but today after re-booting (and just by waking
up
:( it's not even recognizable on the network (Cant rdp to machine name or
even IP address)
Also, can't ping the local computer from within the network via server
either . . times out. Things are just acting up even more so.... So,
with
all that.
1. I'm having issues just getting the client to RDP from the server now.
Why won't ping back? Why can't connect at all any more?
2. Will my desired setup (via router/gateway) even work at any point on
this
SBS setup?
3. Is there an overall better way to be able to RDP straight into a client
desktop w/o going through all this?
I hope i've left enough info, but will be glad to offer more. I'm out of
ideas, and a few weeks/days of hacking this, i need some "real" help ;)
Thanks,
Blake
.
- References:
- RDP to internal client machine?
- From: Blake
- RDP to internal client machine?
- Prev by Date: Re: Automation
- Next by Date: Re: SBS RWW Vista and Client drive mapping
- Previous by thread: Re: RDP to internal client machine?
- Next by thread: Re: RDP to internal client machine?
- Index(es):
Relevant Pages
|
