Re: ISA Remote Access Stops Working
- From: "Ori Yosefi [MSFT]" <oriy@xxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 19 Feb 2006 16:23:01 +0200
Try checking the logviewer to see which traffic is blocked.
From what you are describing, I think RDP traffic should be allowed.
Ori.
--
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.This posting is provided "AS IS" with no warranties, and
confers no rights.
"Rodney Buike (MVP)" <rodb@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:ep5tJ02MGHA.3144@xxxxxxxxxxxxxxxxxxxxxxx
My computer is still part of the Remote Management Computers group, and I
was able to reboot it mutliple times during setup, applying patches. The
issue did not occur until I configured the rules.
The three RDP rules are published servers on the LAN. I will try a
internal to localhost rule.
Thanks for the suggestion.
Rod
"ZVR" <vzaneNOSPAM@xxxxxxxxxx> wrote in message
news:43f53907$0$5694$9a6e19ea@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
I am testing a new HP DL320 ISA appliance and have come across this same
issue repeatedly.
Since you are using a "pre-configured" appliance... did you verify
whether the membership of the Remote Management Computers group is being
reset automatically at each reboot by the appliance? I know at least one
appliance that does this for security purposes, unless you specifically
disable this feature.
I have no special rules configured, 3 inbounnd RDP rules
What are the 3 inbound RDP rules for?
I originally thought this was a hotfix issue as I was installing a new
set of hotfixes after it was configured. I started fresh and installed
all hotfixes before creating any rules. This worked out but for fun I
decided to reboot and see what happens. RDP access to the ISA broke
again.
OK here's an alternate suggestion if nothing works and you're stuck with
this.
1. Change the TS port on your ISA appliance to something else, say, port
10000 or whatever.
http://support.microsoft.com/default.aspx?scid=kb;en-us;q187623
2. Create a custom rule allowing access to Localhost for the protocol
RDP, from the management IP(s). Make sure you specify the new port when
you create the custom rule (don't accept the "default port" setting).
This should work if everything else fails.
Virgil
I get
the error
---------------------------
Remote Desktop Disconnected
---------------------------
The client could not connect to the remote computer.
Remote connections might not be enabled or the computer might be too
busy to accept new connections.
It is also possible that network problems are preventing your
connection.
Please try connecting again later. If the problem continues to occur,
contact your administrator.
---------------------------
OK Help
---------------------------
What am I missing?
--
--
Rodney Buike
MVP Windows Server - Directory Services
http://thelazyadmin.com
*** This posting is provided "AS IS" with no warranties, and confers no
rights. ***
.
- References:
- ISA Remote Access Stops Working
- From: Rodney Buike \(MVP\)
- Re: ISA Remote Access Stops Working
- From: ZVR
- Re: ISA Remote Access Stops Working
- From: Rodney Buike \(MVP\)
- ISA Remote Access Stops Working
- Prev by Date: Re: Cannot Access Internet
- Next by Date: Re: Cannot Access Internet
- Previous by thread: Re: ISA Remote Access Stops Working
- Next by thread: ISA will not NAT 443
- Index(es):
Relevant Pages
|