Re: Remote Connected on VPN - NOW what?

Ports 4125 and 443. You need to rerun the CEICW and make the proper
selections as well as to setup a self signed certificate.

"Tom" <Tom@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C2A58EB8-1A24-465A-A849-54AFA12C3C4B@xxxxxxxxxxxxxxxx
OK. This is starting to make more sense to me. I wasn't aware that RWW and
the VPN were separate things. I've connected to both in my testing.
However,
I think my PIX firewall is blocking access using RWW. I have a Cisco guy
who
helps me program that. What port forwarding do I need to do have him set
on
the firewall?

Problem almost solved, I think.



"Lanwench [MVP - Exchange]" wrote:

Tom <Tom@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
I'll try the \\servername. Meanwhile, can you explain a little more
what RWW is?

Remote Web Workplace. Go to https://localhost/remote on your server
itself
to see what the main page looks like. Users and admins get different
"welcome" pages when they log in (so the users won't see the option to
log
into the server via RD, for example).

The feature of RWW you're going to be the most interested in, is the
"connect to my computer at work" Remote Desktop option. It's a poor man's
terminal server.

That said, if you also get a dedicated TS box on your network, you will
see
the option to "connect to my company's application sharing server" on the
main page.

Is it secure like VPN?

I'd say it's more secure. Not only because it goes over SSL for
encryption,
but also, it doesn't create any kind of tunnel between the host & client
computer through which Bad Things might travel. Remote Desktop just shows
you screenshots - no data is actually travelling between your computer
and
the host, so it's not only better performing, it's also less likely to
expose your corporate network to whatever nasty things are lurking on
your
employees' home computers.

Am I going to have issues with
our PIX firewall using RWW? Thank you very much.

No, you shouldn't, if you know how to do your port forwarding properly.



"Lanwench [MVP - Exchange]" wrote:

Tom <Tom@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
I didn't think this was supposed to be complicated. All I want to do
is be able to access our shared network drive while out of the
office.

OK - you can do that if your VPN is working. When your VPN
connection is up try going to \\servername\sharename.

Additionally, it looks like I should have the ability to get right
to the desktop of a client computer in the office when I am remote.

That's what RWW is for (no VPN required)

As you can see, I just followed the suggested wizards, etc. And it
APPEARS that I got successfully connected. I want to know the best
and most secure way for myself and others in our office to access
the network when out of the office. Thanks.

RWW & remote desktop to their XP Pro computers or a separate W2003
Terminal Services box, hands down.


"Holz" wrote:

On Thu, 31 Jan 2008 09:46:00 -0800, Tom wrote:

I can connect, and it shows that I'm connected in the systray.
But I can't see anything. What am I doing wrong?

What do you want to see? Di you launch RDP to take over a computer?
What exactly do you want to do?

--
:-)






.

Relevant Pages

  • Re: VPN
    ... RWW is the 'killer app' of SBS2003, ... Network Admins SALIVATE over the possibility of stealing it from SBS space. ... How does this negate the need for VPN? ... Allowed users can establish a secure HTTPS connection to the server, ...
    (microsoft.public.windows.server.sbs)
  • Re: Unable to access RWW externally
    ... Since my test machine was "outside" my network by being ... connected to the wireless on the external DSL gateway router, ... > Port 3389 is not needed for RWW, that is only needed for TS. ... >> The netgear has port forwarding set for the above IPs to the external IP ...
    (microsoft.public.windows.server.sbs)
  • Re: RWW and Web Site
    ... When I use RWW I use my static IP address to connect to my workplace server and computers. ... many routers offer 'PPTP passthrough' or 'PPTP ... There is an unbelievably large number of ways to stop VPN from working properly if someone messes with the SBS default settings. ... There are various utilities which can be used to troubleshoot PPTP VPN, but if you expect to administer networked computers, you should learn to use a logging program such as Wireshark or Microsoft's Network Monitor. ...
    (microsoft.public.windows.server.sbs)
  • Re: VPN
    ... Most SBS owners are going to have port 443 open for OWA and/or Exchange RPC ... If VPN is required additional ports need be ... RDP via RWW is inherently more secure due to this. ... Where I support your argument is if a proper firewall is implemented, ...
    (microsoft.public.windows.server.sbs)
  • Re: RE: break in? - terminal services on alternate port
    ... Not changing the default RDP port immediately identifies a potential ... "Network vigilance" would be based on defining what services are needed, ... Terminal services has an excellent ... >serviced machine should be provided via a VPN connection. ...
    (Focus-Microsoft)
Loading