Re: connect to a server via terminal without a public IP
- From: "Merv Porter [SBS-MVP]" <mwport@xxxxxxxxxxxxxxxxxxx>
- Date: Sat, 31 Mar 2007 20:05:19 -0400
I'm surprised Merv mentions logmein and server in the same sentence
Not a favored solution by any means, but it may be all that's possible here
if the OP can't get the ports open or get another ISP. Figured I'd throw it
on the table for consideration. 256-bit SSL encryption. I've tried to keep
pretty close tabs on it for the past year and I haven't seen anything yet
that would indicate that Logmein is a major security risk. Maybe I'm not
reading the right reviews/security papers?
And yes, I agree there are ISP's who only offer a private connection through
their servers to the web. Ran into this last month with a wireless
(satellite) provider in my area. But these guys at least opened up the
connection so that all traffic was forwarded to a router in front of the
client's computer.
--
Merv Porter [SBS-MVP]
============================
"SuperGumby [SBS MVP]" <not@xxxxxxxxxxx> wrote in message
news:%23miRrr9cHHA.588@xxxxxxxxxxxxxxxxxxxxxxx
not necessarily
it's not really common but there are (normally cable) ISPs who use a
private subnet for customer equipment. Only real answer in this case is to
get another ISP. It _may_ be that the ISP can provide a public IP, at
additional cost.
I'm surprised Merv mentions logmein and server in the same sentence. If we
cannot get a public IP nor router changes then I might consider logmein on
one (or many) of the workstations but that carp is coming nowhere near the
server, it's not required on the server. General users may benefit from
access to their PC's and administration could be performed by 1st
controlling a workstation and from there the server.
"Merv Porter [SBS-MVP]" <mwport@xxxxxxxxxxxxxxxxxxx> wrote in message
news:OuuX757cHHA.984@xxxxxxxxxxxxxxxxxxxxxxx
The leased router has a public (WAN, public IP address) and a private
(LAN, 192.168.1.x). If your customer's server is behind this leased
router, can you have the leasing company put the router in bridge mode
and forward all inbound traffic to the private LAN (192.168.1.x)?
If so, you could then put another router or firewall between the leased
router and the customer's SBS server. Then set up the new router with a
static WAN IP address in the same subnet as the leased router
(192.168.1.x). The LAN (private) side of the new router should then be
configured for a different subnet (say, 192.168.0.x). You would then
need to change the LAN IP address of the customer's SBS server to
something in the 192.168.0.x subnet using the built in Change IP Wizard
in SBS. All traffic would flow from the Internet, through the leased
router, to the new router. Turn off DHCP service on the new router. You
could then forward the appropriate ports (3389, 4125, 443, etc.) from the
new router to the customer's SBS server NIC and re-run CEICW to set up
the SBS server to host the DHCP service for the SBS LAN and configure the
services you require (RWW, Terminal Services, etc.).
Internet
|
Leased Router (WAN side, public IP address, bridge mode-forward all
traffic to 192.168.1.x LAN)
|
Leased Router (LAN side, 192.168.1.x, static IP)
|
New Router (WAN side, 192.168.1.x, static IP)
|
New Router (LAN side, 192.168.0.x, static IP)
|
SBS Server NIC (192.168.0.x, static IP)
Another way (easier to implement but perhaps a bit less secure and
without file transfer capability) would be to install Logmein (Free
Edition) on the customer's SBS server.
www.logmein.com
--
Merv Porter [SBS-MVP]
============================
"Cristian Caraccio" <CristianCaraccio@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:3FDC0616-0A9C-480D-ABA3-379AABC75C4B@xxxxxxxxxxxxxxxx
Hello from Italy, excuse my bad english, sorry.
When the SBS 2003 server is connected to internet DSL with public IP
address
I have no problems, for both static and dynamic IP, but I have a big
problem
when the server is connected to internet via a DSL subscription without
PUBLIC IP, for example I have my server sbs connected normally with a
public
static IP dsl, no problems, but another sbs 2003 server connected to
internet
with only a private ip range, the router is not owned from the customer,
but
is leased and is not possible to open ports (3389 for example) and is
not
possible to have a public ip. The customer has the server and all the
network
in 192.168.1.x range, I need a solution that can be installed in the
server
sbs 2003, better if starts as a service, this must me connect the
PRIVATE
server directly to my public static IP, then I need to connect using
terminal, a session from me (public) to the PRIVATE server. I have in
mind
something like VPN, but I have tried to do this without success, besides
the
PRIVATE SERVER has only 1 nic, my public server in the other hand has 2
nic
(multihomed). Please what is the best and easy solution to open a port
only
for me to log in using terminal to the private server, connected 24h to
internet, but without public ip. Remember I can go to the private server
sbs
and install sw to do this, I need only to do administrative tasks using
internet terminal services from my location (public) to the private
server
that is a DC too.Thaks for all, if you need other explanations ask me,
regards. Cristian. PS: If solution is VPN please let me know shortly
step by
step I must do to the PRIVATE server to connect is to my public
multihomed
server, port to open , remember I can use only PPTP to my router. HElp
me,
bye.
.
- References:
- Re: connect to a server via terminal without a public IP
- From: SuperGumby [SBS MVP]
- Re: connect to a server via terminal without a public IP
- Prev by Date: Re: sbs 2003 disaster recovery best software
- Next by Date: Re: PPTP won't connect
- Previous by thread: Re: connect to a server via terminal without a public IP
- Next by thread: Re: SP 2 and Internet RIM Issues HELP
- Index(es):
Relevant Pages
|
