RE: Remote Access

Hi & Thanks for your reply,

I do have a router connected to the internet <-> SBS server and port 4125 is
forwarded to the server. (I have done this manually but as it is a PnP router
it does give me the option to run the wizard and let it do it for me, I have
tried with and without the wizard with the same result)

I have run "netstat -aon | find ":4125"" on the server and I get no
response, I have tested the command on other ports and on"*" and I do get a
response (I see the port open and the corresponding PID)

As for XPsp2 I have reconfigured the pop up blocker so as it does not block
pop-ups, this had no effect.

I have also had the same connection issue on an XP Home box.

The network topology is thus:

_ Remote client PCs have been both XP Pro sp2 and XP Home with the same
result.
_ Firewall/Router is Netgear DG834 v2 Connected to Netgear FS524 Switch
_ No ISA
_ SBS 2003 Standard sp1
_ Simple LAN environment, DHCP is SBS, 9 terminals all running XP Pro sp2

RWW & RDC are fine from on the lan using http://servername/remote but when
remotely connecting to http://*.*.*.*/remote it will connect to RWW but the
connection to ALL desktops is intermittant.

By intermittant I mean that if I run the "connect to the internet" wizard on
the SBS box it will work, but after an undetermined amount of time it will no
longer allow connections to desktops and servers, displaying the error
message in SOLONYs previous post.

I can only assume that this problem has been from the beginning, as I only
recently set up RWW and have noticed the problem, no software has been
installed since setup, current major packages include:
_ Exchange 2003 sp1
_ Symantec Mail Security for MS exchange
_ Symantec Client Secuity
_ Symantec Antivirus Corporate Edition
_ GFI Mail Essentials V12

Rest is standard stuff.

Thanks for your time,

Chris




--
IT & Network Coordinator


""Brandy Nee [MSFT]"" wrote:

Hello Chris,

Thank you for posting back!

It is Brandy here. Since Jenny is taking leave so I will work on this issue
with you.

I understand that after you reboot SBS Server, you cannot RWW and then RDP
to domain computer desktops. If I have misunderstood your concern, please
let me know.

From the error message, most of the issue is caused by the inbound TCP port
4125 is blocked. So I suggest that you check the following things:

1> Do you have a router connected from SBS to internet? Make sure that the
port 4125 has turned on on the router or firewall hardware, and forward
traffic on port 4125 to the SBS server. For more information regarding a
similar issue which is caused by ISA, read the KB article:

828053 ISA Server prevents connection to a remote desktop when you connect
http://support.microsoft.com/?id=828053

2> If you have already turned on the port 4125, the issue still exists,
please check whether there is certain process running on the SBS server has
listened on the port 4125.

For detail information and steps, please read the following KB article:

886209 Users cannot connect to remote desktops by using the Windows Small
http://support.microsoft.com/?id=886209

3> Sometimes this issue can occur if you are using a Windows XP SP2
computer to connect from. Windows XP SP2 has a pop-up stopper which will
block the Web RDP session. In Internet Explorer on the workstation you are
connecting from, go to Tools, Internet Options, then click on the Privacy
tab, remove the check for Block pop-ups. Close and reopen IE and check if
you can connect now. If you have third party pop-up stopper software
installed, please also disable it.

If the issue persists, please help me to gather following information for
further research:

1. What is the Network Topology? For example:

{Remote problematic PC} {Hardware Firewall/ISA} {Internet} {Router/Hardware
Firewall} {ISA} {NIC1} {SBS 2K3} {NIC2} {In LAN}

2. Are all of the "problematic" workstations at the same location? If you
change another remote location, will the issue occur?

3. Could you access the SBS server desktop from RWW?

4. Does this issue occur to all remote clients or only certain? If you ask
a good client to log on the problematic remote client workstation, will
this issue occur?

5. When did the issue occur? Did you encounter this issue before? If no,
did you make any changes or install any updates/software recently?

Please take your time to perform the steps and gather the information as
required. I am looking forward to your reply!

Best regards,

Brandy Nee

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security
======================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.



--------------------
Thread-Topic: Remote Access
thread-index: AcaAnk14p4GzgxqWTES5nkJtzm64NQ==
X-WBNR-Posting-Host: 81.137.39.206
From: =?Utf-8?B?Y21qa2VlZ2Fu?= <cmjkeegan@xxxxxxxxxxxxxxxxxxxxxxxxx>
References: <BF22BD9B-60E6-4450-89FA-70242B7BFFB6@xxxxxxxxxxxxx>
<NcwfEtjeGHA.188@xxxxxxxxxxxxxxxxxxxxx>
<14F3B911-C3A0-413E-B71F-3FB8839A085F@xxxxxxxxxxxxx>
<KTLt#$yeGHA.3900@xxxxxxxxxxxxxxxxxxxxx>
<778726D5-8658-40D3-A59A-A0A02AFA6A70@xxxxxxxxxxxxx>
<EKFAJO6fGHA.5608@xxxxxxxxxxxxxxxxxxxxx>
<HC20XS6fGHA.2260@xxxxxxxxxxxxxxxxxxxxx>
<D4276B5D-DF6E-493D-9E20-6742C8292814@xxxxxxxxxxxxx>
<shLSTeIgGHA.5184@xxxxxxxxxxxxxxxxxxxxx>
Subject: RE: Remote Access
Date: Fri, 26 May 2006 01:28:01 -0700
Lines: 322
Message-ID: <06B61A08-56A5-4AFE-BC46-A8A8BF3DB088@xxxxxxxxxxxxx>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
Newsgroups: microsoft.public.windows.server.sbs
Path: TK2MSFTNGXA01.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:271048
NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
X-Tomcat-NG: microsoft.public.windows.server.sbs

Hello again, I thought it was working but having restarted the server last
night I have come across the same problem.

I will assume that running the same wizard as before will solve the
problem
but I don't want to have to do that every time it is rebooted , for
obvious
reasons.

Is there a service that isn't starting or something? I can access RWW but
when trying to connect to any desktops or servers I recieve the message
that
"REMOTE CONNECTIONS MAY NOT BE ENABLE OF THE COMPUTER MIGHT BE TO BUSY TO
ACCEPT NEW CONNECTIONS. IT IS ALSO POSSIBLE THAT THE NETWORK PROBLEMS ARE
PREVENTING YOUR CONNECTION"

It's annoying me!

Chris
--
IT & Network Coordinator



.

Relevant Pages

  • Re: RWW problem with SBS2003
    ... This SBS server is new since the ex left, ... >> the default RDP port from 3389. ... >>> of the RDP connection can stay at their defaults, ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot connect client to server 2003
    ... you need to reconfigure the IP schema of your SBS ... On the SBS 2003 Server open the Server Management console. ... On the Connection Type page, click Broadband, and then click Next. ... Alternate DNS server, type the IP addresses that are provided by your ISP ...
    (microsoft.public.windows.server.sbs)
  • Re: Remote Web Workplace Partially Works
    ... Les Connor [SBS Community Member - SBS MVP] ... > a) I opened port 4125 on the SBS server following the guidance of KB ... > c) Remote connection should be enabled on the wotkstations as I did use ...
    (microsoft.public.windows.server.sbs)
  • Re: Urgent! New router and big disaster
    ... seleting full time broadband connection. ... Les Connor [SBS Community Member - SBS MVP] ... check the router as well and unless I missed a firewall setting on it, ... Anyway the Server Ipconfig /all is this... ...
    (microsoft.public.windows.server.sbs)
  • Re: Urgent! New router and big disaster
    ... Anyway the Server Ipconfig /all is this... ... Server Local Area Connection: ... Les Connor [SBS Community Member - SBS MVP] ... First Page of the Internet Connection Wizard, ...
    (microsoft.public.windows.server.sbs)
Loading