Just to be picky,
The private addresses start with:
10.
172.16-32.
192.168.
I'll give you 127. , though that one's #really# private.
Best wishes
Chris Jaecker
>- --- "Alex K. Angelopoulos" <[EMAIL PROTECTED]> wrote:
> > OK, first question is - can you co
Rusty,
The java app only uses 5800 to download the VNC viewer app. The actual Java
app uses the regular VNC ports. So you need 5800 to get the java app, but
5900+ to get the VNC client-server traffic.
Chris Jaecker
At 07:08 25/04/02 +0100, you wrote:
>Date: Thu, 25 Apr 2002 05:49:07 -0
regular VNC client,
it is simply a java app downloaded to the client from the server as opposed
to a local client program. Once it is downloaded and running, it works the
same way as the regular client.
Hope this gives you something to go on. Let me know more about the topology
if you can, as
Gabor,
APC have a Master Switch Network power controller that can be console
managed (via a terminal server or direct connection), SNMP managed, or
telnet managed. It's excellent. I run a remote lab and can power down,
reboot and power up all of the lab equipment.
Best wishes
Chris Ja
go faster than 33.2Kbps, as they are both having to do the digital/analog
conversions. Only when you connect to an ISDN device (e.g. at your ISP),
will the traffic to you be sent at 56K. Any kind of noise or attenuation of
signal
Greetings,
I know this is a little "off the topic", but does any one know how to get
an NT server to boot without a mouse without reporting an error event? I'd
like to be able to boot either with or without the mouse.
Thanks
Mike,
They lied to you. IPSEC is a tunnelling protocol, and carries VNC via TCP
over IP. What's happening is the data from VNC is being sent in a container
that is too big to fit into IPSEC's payload. So it's being broken into
2 and put into 2 datagrams, and reassembled by your VNC client. Th
At 10:20 24/01/02 +, you wrote:
>Date: Thu, 24 Jan 2002 13:00:28 +
>From: [EMAIL PROTECTED]
>Subject: Re: MTU
>
>Chris,
>can you clarify your reply please.
No problem. Bear in mind that this may not be the cause of your problems.
>On 24/01/2002 11:35:2
l.
The other possibility is if you have any kind of NAT or PAT running and
it's aging out the ports too quickly. I don't think this is likely unless
the TCP "hello"s are too widely spaced. You'd fix this on the router.
Hope this is useful
Chris Jaecker
At 06:00 24/01
nnels, and have run tunnel connections from Singapore and
Taiwan to Sydney.
Hope this will help others facing similar problems.
Chris Jaecker
______
Chris Jaecker, Director Illustrated Networks
tel: +61 (0)2 9418 4226 [EMAIL PROTECTED]
fax:
n, and the mail archives (1999-2001). In
the latter I percieve that this is not a new problem, but sadly have not
been able to read any appropriate answers.
Any and all suggestions would be appreciated.
Best wishes
Chris Jaecker
________
11 matches
Mail list logo
