Prev: HELP! Lost Raid 1, now Error loading operation system!
Next: Problem running Best Practices and other MS programs
From: Jim Graue on 29 Sep 2008 04:27
Hello, All:

I am attempting to set up new SBS 2003 Prem R2 system. I have static
routable IP. I intend to have mail for my domain hosted on this system, but
have not yet had Webhosting service change MX record. When I attempt to
connect to sys via RWW using https://my.ip.address/remote, I am able to get
RWW session but cannot use "Connect to my computer at work" or "Connect to my
company's app-sharing server." In both cases, whether domain user or admin,
I get "vbscript: Remote Desktop Disconnected. The client could not
establish a connectio to the remote computer. The most likely causes for
this error are:
1) Remote connections might not be enabled at the remote computer
2) The maximum number of connections might be exceeded at the remote computer.
3) A network error might have occurred while establishing the connection
4) The Remote Web Workplace designated port might be blocked by a firewall.

Getting an OWA window from main menu is possible. On the LAN, when using
http://mysbserver/remote, everything functions, all the way to the desktop on
the TS or client workstation. Same remote systems can get to other
well-functioning SBS networks. Firewall at failed location is forwarding
ports 443, 444, and 4125 to SBS.

Any thoughts and/or insight is greatly appreciated.
--
Best regards,

Jim Graue
From: Lanwench [MVP - Exchange] on 29 Sep 2008 11:33
Jim Graue <JimGraue(a)discussions.microsoft.com> wrote:
> Hello, All:
>
> I am attempting to set up new SBS 2003 Prem R2 system. I have static
> routable IP. I intend to have mail for my domain hosted on this
> system, but have not yet had Webhosting service change MX record.
> When I attempt to connect to sys via RWW using
> https://my.ip.address/remote, I am able to get RWW session but cannot
> use "Connect to my computer at work" or "Connect to my company's
> app-sharing server." In both cases, whether domain user or admin, I
> get "vbscript: Remote Desktop Disconnected. The client could not
> establish a connectio to the remote computer. The most likely causes
> for this error are: 1) Remote connections might not be enabled at
> the remote computer 2) The maximum number of connections might be
> exceeded at the remote computer. 3) A network error might have
> occurred while establishing the connection 4) The Remote Web
> Workplace designated port might be blocked by a firewall.

>
> Getting an OWA window from main menu is possible. On the LAN, when
> using http://mysbserver/remote, everything functions, all the way to
> the desktop on the TS or client workstation. Same remote systems can
> get to other well-functioning SBS networks. Firewall at failed
> location is forwarding ports 443, 444, and 4125 to SBS.
>
> Any thoughts and/or insight is greatly appreciated.

Did you run the CEICW and select the RWW options you wanted?


From: Jim Graue on 29 Sep 2008 12:10
Hello, Lanwench:

My replies/comments are in-line, below:

"Lanwench [MVP - Exchange]" wrote:

> Jim Graue <JimGraue(a)discussions.microsoft.com> wrote:
> > Hello, All:
> >
> > I am attempting to set up new SBS 2003 Prem R2 system. I have static
> > routable IP. I intend to have mail for my domain hosted on this
> > system, but have not yet had Webhosting service change MX record.
> > When I attempt to connect to sys via RWW using
> > https://my.ip.address/remote, I am able to get RWW session but cannot
> > use "Connect to my computer at work" or "Connect to my company's
> > app-sharing server." In both cases, whether domain user or admin, I
> > get "vbscript: Remote Desktop Disconnected. The client could not
> > establish a connectio to the remote computer. The most likely causes
> > for this error are: 1) Remote connections might not be enabled at
> > the remote computer 2) The maximum number of connections might be
> > exceeded at the remote computer. 3) A network error might have
> > occurred while establishing the connection 4) The Remote Web
> > Workplace designated port might be blocked by a firewall.
>
> >
> > Getting an OWA window from main menu is possible. On the LAN, when
> > using http://mysbserver/remote, everything functions, all the way to
> > the desktop on the TS or client workstation. Same remote systems can
> > get to other well-functioning SBS networks. Firewall at failed
> > location is forwarding ports 443, 444, and 4125 to SBS.
> >
> > Any thoughts and/or insight is greatly appreciated.
>
> Did you run the CEICW and select the RWW options you wanted?

Yes. In CEICW, during the certificate creation phase, I used the static
routable address for the FQDN.

--
Best regards,
Jim Graue
From: Lanwench [MVP - Exchange] on 29 Sep 2008 17:15
Jim Graue <JimGraue(a)discussions.microsoft.com> wrote:
> Hello, Lanwench:
>
> My replies/comments are in-line, below:
>
> "Lanwench [MVP - Exchange]" wrote:
>
>> Jim Graue <JimGraue(a)discussions.microsoft.com> wrote:
>>> Hello, All:
>>>
>>> I am attempting to set up new SBS 2003 Prem R2 system. I have
>>> static routable IP. I intend to have mail for my domain hosted on
>>> this system, but have not yet had Webhosting service change MX
>>> record. When I attempt to connect to sys via RWW using
>>> https://my.ip.address/remote, I am able to get RWW session but
>>> cannot use "Connect to my computer at work" or "Connect to my
>>> company's app-sharing server." In both cases, whether domain user
>>> or admin, I get "vbscript: Remote Desktop Disconnected. The
>>> client could not establish a connectio to the remote computer. The
>>> most likely causes for this error are: 1) Remote connections might
>>> not be enabled at the remote computer 2) The maximum number of
>>> connections might be exceeded at the remote computer. 3) A network
>>> error might have occurred while establishing the connection 4) The
>>> Remote Web Workplace designated port might be blocked by a firewall.
>>
>>>
>>> Getting an OWA window from main menu is possible. On the LAN, when
>>> using http://mysbserver/remote, everything functions, all the way to
>>> the desktop on the TS or client workstation. Same remote systems
>>> can get to other well-functioning SBS networks. Firewall at failed
>>> location is forwarding ports 443, 444, and 4125 to SBS.
>>>
>>> Any thoughts and/or insight is greatly appreciated.
>>
>> Did you run the CEICW and select the RWW options you wanted?
>
> Yes. In CEICW, during the certificate creation phase, I used the
> static routable address for the FQDN.

I've never tried this with an IP address. Set up an A record, such as
rww.mydomain.com, in your domain's public DNS and specify your static IP.
Then redo the ssl cert and try again to see what you get.


From: Jim Graue on 29 Sep 2008 19:16
Lan:


My replies/comments are in-line, below:

<SNIP>

> >> Did you run the CEICW and select the RWW options you wanted?
> >
> > Yes. In CEICW, during the certificate creation phase, I used the
> > static routable address for the FQDN.
>
> I've never tried this with an IP address. Set up an A record, such as
> rww.mydomain.com, in your domain's public DNS and specify your static IP.
> Then redo the ssl cert and try again to see what you get.

So, I wonder if the issue is that I don't have a name to resolve to. By
tomorrow night, I would, anyway, since I planned to put in a request to my
Webhosting service regarding MX record. I'd have mail.mydomain.com as my
FQDN, at that point. I'm loath to go to too much work to get the bare IP to
function when I want to have the MX record changed.

I just wanted to be sure that everything was working, but I can see that it
works from within the LAN. Maybe I ought to wait until tomorrow afternoon.
If the change of MX record fixes this, I'll post then.

--
Best regards,
Jim Graue
 |  Next  |  Last
Pages: 1 2 3
Prev: HELP! Lost Raid 1, now Error loading operation system!
Next: Problem running Best Practices and other MS programs