Hi,
Seeking some wisdom if I may.
I have a dual homed SBS 2003 server with ISA 2004 SP3. There is also an application server behind the ISA box on the same subnet as the Internal interface of the sbs box.
Until recently this worked very well and I could use RWW to point remote users to the application server when required and I could remotely administer either the SBS box or the Application server from RWW logged in as a domain admin.
I added an allow protocol rule to ISA to allow a specific port access. All still good for everyone wanting to get to the App Server, but now I cant get to the SBS box. I just get silently redirected to the Term Server no matter which one I select from RWW.
No problem. Remove offending Allow protocol rule to reverse the problem. Problem still exists! Cant get to the SBS server except from its console. Even if I am on the internal lan I can no longer RDP to the SBS box. I get the “The client could not connect to the remote computer”
The ISA monitor shows nothing in a logg of port 3389 in the above situation.
Can anyone help me debug this situation. I have spent ages trawling through google groups and the microsoft KB, and sites like ISA.org. All to no avail. They all tell me to check that remote connections are allowed in the properties, which they naturally are as it was working perfectly before the ISA change.
