Re: VPN Works, OWA and RWW Don't



ITDUDE27 wrote:
Merv,

I'm experiencing a very semilar issue, can you shed some light on my cituation


I'm experiencing an issue configuring rww to allow a few sales guys to access their desktops while they are on the road.
I can connect to the desktops from within the office with no problem, when I try to connect from outside I get error message stating : '"The client could not connect ot the remote computer. Remote connections might not be enabled or the computer might be to busy to accept connections.".
I can't connect with the administrator account nor the user accounts which has the right permission.

I have a few questions.
2. I have a Firefox firewall I opened filter port 443, 4125, is that all?
Should be enough for RWW.

3. Is it manadatory to have an ISA server configured?

No.

4. could having one nic card on the server cause the busy server error?

No.

5. on the firewall how can I make sure the port that's opened is tied to ip of the server (telnet)?

You're getting a web page with an error message from the SBS at the
moment, so port 443 is OK. Since it works from the LAN, it's definitely
a routing issue. It does appear that 4125 is not being forwarded, so
the first check is the router configuration to look for typos. If
the entries for 443 and 4125 are otherwise the same then it gets
interesting. If you can set the router to log port 4125 connections,
you may get a further clue. 4125 doesn't open until RWW accepts a
connection to a workstation, so you may or may not see it open. The
chances are it will only open for a few seconds at most in a fault
condition, so not seeing it proves nothing. Just for fun, try power
cycling the router. This fixes a lot of temporary VPN problems in a
wide range of models, so it's worth a try here.

6. does the internal desktops needs static ip's?

No. SBS will know its workstations' IP addresses, and the RWW system
routes port 4125 to port 3389 of the right workstation. In this
area, check by ipconfig that the workstations are all getting DNS
information from the SBS. Probably RWW wouldn't work from inside
the LAN if that's not the case, but have a look anyway. It's straw-
clutching time.
.



Relevant Pages

  • Re: Remote Connection Issue
    ... > If you want to connect to connect to the SBS server box and the LAN client ... you can use the RWW site ... > all related settings in ISA, IIS and firewall automatically. ... >>through port number 3389 and a workstation on the LAN through port number ...
    (microsoft.public.windows.server.sbs)
  • Re: Remote Connection Issue
    ... the main reason many inidividuals went to 2003 is the RWW (remote web ... > If you want to connect to connect to the SBS server box and the LAN client ... >>through port number 3389 and a workstation on the LAN through port number ...
    (microsoft.public.windows.server.sbs)
  • Re: Problem with getting RWW setup
    ... Forwarding of port 3389 is not needed for RWW. ... The only ports you need open on your router to have Exchange, OWA, OMA, RWW, ... nics in server ...
    (microsoft.public.windows.server.sbs)
  • Re: Simple question about RD and RWW
    ... RWW includes a dynamic proxy that forwards the incoming RDP traffic on External port 4125 to the selected Internal machine's port 3389. ... Without RWW or a similar solution to translate/map the traffic from the External machine to the Internal machine's port 3389 then you need unique ports or external ips for each machine similar to your home. ... TS Gateway is a new feature introduced in Windows Server 2008. ... machines so I can map ports on my router to them for remote ...
    (microsoft.public.windows.terminal_services)
  • Re: Direct remote access to a particular computer
    ... So, I'll stick with RWW and the phone calls, but I do thank you for the hints! ... file) can connect to either the server or a PC. ... You only have one public IP so any port can only be ... However, this means each RDP listener is exposed to the internet, not really ...
    (microsoft.public.windows.server.sbs)