RE: can't RDP into ISA server after reboot - for 30 minutes or so.
- From: Ken Rideout <slydiggidydog at hotmail dot com>
- Date: Thu, 17 Aug 2006 15:20:01 -0700
Check this out: http://www.mcse.ms/archive99-2006-2-2156417.html
The problems with RDP make sense once you see how MS is doing it, but it
sure is strange that this isn't addressed by ISA directly. I went into the TS
manager on the ISA box, and changed it to bind only to the internal nic as
indicated in the article. After a reboot, things appear to be working fine.
"Ken Rideout" wrote:
I'm having the same issue here where I can't RDP to the ISA box after a.
reboot. I've found that if I disable the RDP server publishing rules (I have
two terminal servers on the DMZ) prior to a boot, and enable them after the
boot, RDP to the ISA box works fine.
I've never tried waiting to see if it starts working on it's own, I'm far to
impatient for that. Monitoring RDP traffic gave much the same results as you
as well.
"billd" wrote:
"Shijaz" wrote:
Interesting problem :)
During the first ~30 mins, have you ever tried opening the Monitoring tab on
the server itself and then trying to establish RDP session from a workstation?
10.50.100.160:3389 10.50.100.50 Internal Local Host Establish 0x0
10.50.100.160:3389 10.50.100.50 Internal Local Host Terminate 0x80074e21
3 x in a row... The RDP Terminal service is running and the RPC service is
running, so it can't be that it can't find the server
that's it... 30 minute is the mimum. I rebooted yesterday, and wasn't able
to get a remote session until this morning... wondering if perhaps if it
restarts after I manually restart the firewall services after a reboot...
possible sequencing problem
You probably need to speak to MS Support. If you figure out what was wrong
please post back so that we all know!
when I build a
new site-to-site VPN tunnel, I have to reboot the ISA server... hitting
apply, reloading firewall etc etc, does no good, it HAS to be rebooted.
Have you tried simply restarting the ISA services manually instead of
rebooting the server itself?
Have tried restarting everything to do with ISA... no go... reboot and it
starts working. Google a bit on it, several people having the same problem
when building tunnels... not good if its an enterprise system like mine. I
only have a 2 hour slot where I can reboot this server at all and I would at
least like to do it remotely, but no, I have to come into office at 3am and
do it as it's out of our offices core hours... and we're only a fairly
small company, not sure how large companies that run 24x7 deal wiht this.
--
Shijaz
MCSE:Security, CCNA
www.shijaz.com/isaserver
"billd" wrote:
Hi,
This is really weird. I have an access rule to allow my comptuer to RDP
into my ISA server... and it works, after a while. If I reboot my server, I
can't RDP into it for at least 30 minutes... that's really a guess, I can't
log into it for quite a long while anyway. Then at some point later on, I
can log in. Doesn't matter what time of day or anything... but, as I've
found to my chagrin and several days of scratching my head, when I build a
new site-to-site VPN tunnel, I have to reboot the ISA server... hitting
apply, reloading firewall etc etc, does no good, it HAS to be rebooted. Have
seen several other posts on this subject and it's fact... so anyway, when I'm
building a new tunnel, I have to reboot the ISA server, which is a real pain
as then I can't RDP back into it. I can just about live with the reboots,
but if I am working remotely, I can make a change, then reboot, if it doesn't
work, then I can't get back in to figure out why for at least 30 minutes. :-(
- References:
- Prev by Date: RE: can't RDP into ISA server after reboot - for 30 minutes or so.
- Next by Date: Is it normal for MSDE to make so many files?
- Previous by thread: RE: can't RDP into ISA server after reboot - for 30 minutes or so.
- Next by thread: migrating a ISA 2000 Enterprise Configuration to a New ISA 2004 Enterprise Server
- Index(es):
Relevant Pages
|
