Re: ISA client on a non-domain machine
- From: "cory_jackson" <cory@xxxxxxxxxxxxxxxxxxx>
- Date: 1 Jun 2006 08:23:49 -0700
Wow, thanks for the great response. I'm going to look into your
suggestions at the bottom but I'll answer your questions first.
1) No.
2) No.
3) Not sure. Do you mean admin of the machine or the domain? On the
machine the user account is an admin account. The machine belongs to
another domain primarily so therefore can not join this domain. Now if
I log into one of the domain machines I am able to make the RD client
out there.
4) Yes. Here it is:
Event Type: Error
Event Source: Microsoft Firewall Client 2004
Event Category: None
Event ID: 2
Date: 6/1/2006
Time: 8:05:18 AM
User: N/A
Computer: TOWHEE
Description:
Application [mstsc.exe]. Authentication failed. Verify that the user
account running this application has the required permissions. If the
application is running under a system account, you can apply different
credentials for this application via the client configuration and
FwcCreds.exe.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 04 03 09 80
5) What would you like a screenshot of? There really isn't anything to
see. It's the normal message you get when you try to connect to a
machine that isn't responding. Sorry, I'm using Google and i don't see
a way to attach. If you really need it I'll put it on my website for
you but there's really nothing remarkable about it.
Let me back up a little here. It just occurred to me that I might be
going about this the wrong way. Can you advise me as how the best way
to do this is? IOW if I'm on a non-domain machine and want to get RD to
work how do i do it? You say doing it with ISA is not advised so what
is the recommended way?
I apologize. I should know more about ISA than I do. To be honest I
don't know the first thing about it and i feel like an idiot. Maybe you
could recommend some reading for me to get started with? Personally I
like books with functional descriptions of the systems followed by
practical examples. But my problem has been that either the books have
been too simple or they are a sort of expert reference guide that's 4"
thick and impossible to digest. So if you know of any good books I'm
all ears. I'll go to the bookstore later today and see what I can find.
I would like to kindly clarify that the Firewall Client can be installed on
the non-domain user (but it's not the recommended way). As I know, the
firewall client (FWC) can pick up the client side network requests;
encapsulate the request with the current logon users' credentials and then
send the request to the ISA server. If the workstation is not a member of
the domain, the FWC will send the request with anonymous privilege. You can
create the rule which applies to 'All Users' to allow the outbound requests
for the non-domain computers.
This sounds interesting. I saw the bit about using the FwcCreds but i
tried that on another machine and it didn't work. But I wasn't very
enamored by the idea of having to set credentials for every single
application. It seemed to me that I should go to the ISA server and in
effect tell it that on machine 192.168.1.23 to allow outbound traffic
on port 3389 or something like that.
Like I say I'll try your suggestion but I'm crippled by the fact
that I don't know the Ass from the head of this beast. <g> Thank you
very much for helping me out on this one.
.
- Follow-Ups:
- Re: ISA client on a non-domain machine
- From: "Crina Li"
- Re: ISA client on a non-domain machine
- References:
- ISA client on a non-domain machine
- From: cory_jackson
- RE: ISA client on a non-domain machine
- From: "Crina Li"
- ISA client on a non-domain machine
- Prev by Date: Re: Web publishing rules are not created with the internet conection wizard
- Next by Date: Re: Instructions for upgrading SBS2003 Std to SBS 2003 Premium
- Previous by thread: RE: ISA client on a non-domain machine
- Next by thread: Re: ISA client on a non-domain machine
- Index(es):
Relevant Pages
|
Loading
