E
Eric
Hi Everyone!
I have an interesting situation that I was looking for input before I
declare there is nothing left I can do.
One of our buildings is partially owned by a very large corporation,
that building gets it's Internet connection over a 256k leased line
that goes back to the corporate headquarters. Our other offices all
connect to the Internet by T1s/DSLs and are completely under our
control. However the building in question is completely seperate from
our organization with no AD connection at all, it is more connected to
the headquarters then it is to us; which that is not a problem.
The problem lies in the fact that there is a very strict firewall in
place at the other end of the leased line, the administrator computer
is only allowed ports 80, 443, and 21. Now when we are at this other
site and there is a problem back at any of our other offices it would
be very nice to be able to remote desktop out to our other servers,
the only way we can do that now is to dial up.
So my first thought was to modify the port that Terminal Services uses
to 21. I was able to come in across the Internet and TS to port 21 on
one of the servers. But when we got to the locked-down building and
tested it we had no success; so my guess is corporate's firewall is
application aware and seeing that the traffic is not FTP at all, and
blocking it.
As you may guess, corporate politics have denied me the ability to
request 3389 be opened, or we get a seperate, faster connection and do
a VPN to corporate.
So before I hang up my coat and give up getting remote connectivity
out of this building on something faster then a dial-up, does anyone
have any suggestions? The remote servers are Win2003, so I was able
to change the port that TSWeb uses aswell, still no luck.
I am pretty sure there is nothing else that can be done, but it never
hurts to ask the fine people of this group.
Thanks,
Eric Phillips
I have an interesting situation that I was looking for input before I
declare there is nothing left I can do.
One of our buildings is partially owned by a very large corporation,
that building gets it's Internet connection over a 256k leased line
that goes back to the corporate headquarters. Our other offices all
connect to the Internet by T1s/DSLs and are completely under our
control. However the building in question is completely seperate from
our organization with no AD connection at all, it is more connected to
the headquarters then it is to us; which that is not a problem.
The problem lies in the fact that there is a very strict firewall in
place at the other end of the leased line, the administrator computer
is only allowed ports 80, 443, and 21. Now when we are at this other
site and there is a problem back at any of our other offices it would
be very nice to be able to remote desktop out to our other servers,
the only way we can do that now is to dial up.
So my first thought was to modify the port that Terminal Services uses
to 21. I was able to come in across the Internet and TS to port 21 on
one of the servers. But when we got to the locked-down building and
tested it we had no success; so my guess is corporate's firewall is
application aware and seeing that the traffic is not FTP at all, and
blocking it.
As you may guess, corporate politics have denied me the ability to
request 3389 be opened, or we get a seperate, faster connection and do
a VPN to corporate.
So before I hang up my coat and give up getting remote connectivity
out of this building on something faster then a dial-up, does anyone
have any suggestions? The remote servers are Win2003, so I was able
to change the port that TSWeb uses aswell, still no luck.
I am pretty sure there is nothing else that can be done, but it never
hurts to ask the fine people of this group.
Thanks,
Eric Phillips