Re: Remote mvBase Access...
- From: "Simon Verona" <nomail@xxxxxxxxxx>
- Date: Wed, 4 Jan 2006 10:01:33 -0000
If you are specifically doing remote support, then I use a product called
"BLive" www.blive.com which is a much more cost effective solution than
the Citrix Ones..
You install a "listener" package at your help desk, and the user goes to a
web site and connects through there by entering his details.. You have the
ability for "chat", "view his desktop", "view your desktop" or to share
control of either. It uses VNC to do some of the hard work but is simple
and straightforward - requires no software installatiom on the client (it
installs itself!).
Regards
Simon
"David Morris" <david@xxxxxxxxxxxxxxxxxx> wrote in message
news:I9yU$Jnhi4uDFwFp@xxxxxxxxxxxxxxxxxxxxx
> Simon Verona once wrote in <43baff3f$0$63088$ed2e19e4@ptn-nntp-
> reader04.plus.net>...
>>Depends on the firewall/ router, so I can't really comment specifically.
>>
>>If you are using a low-end all-in-one ADSL router then it likely uses NAT
>>and has a Firewall setting which allows you to redirect tcp ports to an ip
>>address.... You will need to post the make/model of the router /
>>firewall
>>or refer to the manual I'm afraid...
>>
>>But at the end of the day, for VPN you need to open port 1723 on the
>>router
>>and firewall and get it directed to your windows server..
>>
>
> What may be easier if the client is behind a NATting router is to talk
> them through installation of VNC or similar on their machine. Assuming
> you then know how to operate your own kit, you set up and put VNC into
> 'listen mode' on your box and get them to make a connection out to you.
> It's slightly messier but removes the need for any changes on the client
> router and doesn't compromise security of the client's network.
>
> Of course, this then relies on the person doing the remote support
> knowing how to configure their router to let the inbound connection in
> (which for VNC is, IIRC on port 5500). This link describes the process
> which seems to fit the case here...
>
> http://faq.gotomyvnc.com/fom-serve/cache/88.html
>
> If you need to support several clients like this, you could allocate an
> inbound port for each one (because each port would need to be seperately
> forwarded on your firewall unless it supports forwarding ranges).
>
> On a more long term basis, the outbound connection can be initiated from
> a batch file and placed in a desktop icon.
>
> The keywords here are: free, secure and secure (yes, I meant to put that
> in twice): the first because there's little to no change of their
> network being compromised and secondly in this wonderful world of SOX
> compliance etc, because the end user / client is controlling who
> connects and when, the auditors should be happier than just having
> people being able to connect in willy-nilly.
>
> PS: If I can talk my mother through downloading and installing VNC, I
> reckon anyone with a bit of nouce can do the same to all but the most
> clueless at the remote end.
> --
> David Morris
> (who also does mv)
.
- Follow-Ups:
- Re: Remote mvBase Access...
- From: daddepants
- Re: Remote mvBase Access...
- References:
- Remote mvBase Access...
- From: daddepants
- Re: Remote mvBase Access...
- From: Simon Verona
- Re: Remote mvBase Access...
- From: daddepants
- Re: Remote mvBase Access...
- From: Simon Verona
- Re: Remote mvBase Access...
- From: David Morris
- Remote mvBase Access...
- Prev by Date: Re: US car dealer software
- Next by Date: Setting up a modem on Universe
- Previous by thread: Re: Remote mvBase Access...
- Next by thread: Re: Remote mvBase Access...
- Index(es):
Relevant Pages
|