Re: Unable to use RWW with new Fortigate 50B appliance
- From: Sean <Sean@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 2 Nov 2008 07:47:00 -0800
Greg,
All outbound traffic is unrestricted, I will begin locking down once I have
the critical functions working. I'll try directly accessing with RDP, and
post my results.
--
Sean
"Gregg Hill" wrote:
Sean,.
Because you have 3389 open inbound (not needed for RWW), test to see if you
can RDP directly to port 3389.
Are you blocking any outbound ports with the firewall? If you are blocking
outbound ports, you need to allow port 4125 for RWW-RDP to work. It must be
open inbound and outbound.
Gregg Hill
"Sean" <Sean@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D2B9EE43-8BD8-40A2-85C9-B7B50460DB33@xxxxxxxxxxxxxxxx
I just swapped outmy old Sonicwall TZ-170 for a new Fortigate 50B and I
opened ports 443, 444, 4125, and 3389 to my SBS server. I am running SBS
2003
Standard with one NIC.
I can connect to the server and when I attempt to connect to either a
desktop or server it wont let me, gives an error "The client could not
connect to the remote computer..... " this used to work, the only variable
is
the new firewall.
Anybody have any suggestions as to what I should look for to resolve this.
Thanks
--
Sean
- References:
- Unable to use RWW with new Fortigate 50B appliance
- From: Sean
- Re: Unable to use RWW with new Fortigate 50B appliance
- From: Gregg Hill
- Unable to use RWW with new Fortigate 50B appliance
- Prev by Date: Re: Unable to use RWW with new Fortigate 50B appliance
- Next by Date: Re: Accessing remote ressource
- Previous by thread: Re: Unable to use RWW with new Fortigate 50B appliance
- Next by thread: RE: Unable to use RWW with new Fortigate 50B appliance
- Index(es):
Relevant Pages
|