Menu
▾
▴
Re: [coLinux-users] vnc step by step needed
|
From: Ben B. <ben...@gm...> - 2009-08-21 20:50:38
|
Looks like we are getting closer. I can't ping colinux from windows.
colinux:~# ping 10.252.248.152
PING 10.252.248.152 (10.252.248.152) 56(84) bytes of data.
64 bytes from 10.252.248.152: icmp_seq=1 ttl=255 time=30.0 ms
C:\>ping 10.0.2.15
Pinging 10.0.2.15 with 32 bytes of data:
Request timed out.
...
Ping statistics for 10.0.2.15:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
-ben
On Fri, Aug 21, 2009 at 2:27 AM, e_fax_t<e_...@ho...> wrote:
> Hi,
>
> please reply on the list in the future so others can contribute.
>
> colinux.org may not reply (it does for me), but at least it seems
> the address is being resolved so there's hope.
> OTOH your TAP address (192.168.37.10)) is not on the same
> subnetwork as your linux (virtual) one, which is different
> from my setup. Let's try & establish if connectivity is alright
> before thinking of a graphical session.
>
> Can you try pinging windows from colinux/debian
> $ ping 10.252.248.152
>
> then colinux/debian from windows
> c:> ping 10.0.2.15
>
> if that is working, then try installing vncserver (as root)
> # apt-get install vncserver
>
> then start it as suggested in my list reply, and try
> connecting from a windows vnc client to 10.0.2.15:1
>
> ----- Original Message ----- From: "Ben Brannen" <ben...@gm...>
> To: "baldyeti" <e_...@ho...>
> Sent: Thursday, August 20, 2009 9:18 PM
> Subject: Re: [coLinux-users] vnc step by step needed
>
>
> Thank you for responding:
>
> * apt-get-update = yes
>
> * ping colinux.org = no replies with
> PING colinux.org (216.34.181.97) 56(84) bytes of data....and hangs (I
> suppose it would eventually time-out)
>
> * start sshd? - I don't know how to do this.
>
> logged in as root:
> colinux:~# ifconfig
> eth0 Link encap:Ethernet HWaddr 00:ff:11:17:a6:00
> inet addr:10.0.2.15 Bcast:10.0.2.255 Mask:255.255.255.0
> inet6 addr: fe80::2ff:11ff:fe17:a600/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:4605 errors:0 dropped:0 overruns:0 frame:0
> TX packets:1900 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:6551008 (6.2 MiB) TX bytes:118882 (116.0 KiB)
> Interrupt:10
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:34 errors:0 dropped:0 overruns:0 frame:0
> TX packets:34 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:2384 (2.3 KiB) TX bytes:2384 (2.3 KiB)
>
> colinux:~#
>
> from windows host:
> private info is x'd out
> C:\>ipconfig
>
> Windows IP Configuration
>
>
> Ethernet adapter Intel PRO1000 MT Network Connection:
>
> Connection-specific DNS Suffix . : xxxxxxxx.xxx
> IP Address. . . . . . . . . . . . : 10.252.248.152
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 10.252.248.1
>
> Ethernet adapter TAP-Win32 Adapter V8 (coLinux):
>
> Connection-specific DNS Suffix . :
> IP Address. . . . . . . . . . . . : 192.168.37.10
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . :
>
> C:\>
>
> -ben
>
>
>
> On Thu, Aug 20, 2009 at 1:14 PM, baldyeti<e_...@ho...> wrote:
>>
>> I think we need a bit more information, Ben:
>>
>> have you got the network connectivity working at all, eg running
>> "apt-get update" from colinux (or simply "ping colinux.org",
>> for that matter), and conversely connecting from the windows side
>> to your colinux instance (typically using putty after having started
>> sshd on the colinux side) ?
>>
>> I have occasionally run vnc myself (tightvncserver debian package)
>> I start it from the colinux console typing
>> "vncserver -geometry 1024x768 -depth 24"
>>
>> Then I use tightvnc (vnc viewer) on the windows side (colinux-ip:1),
>> and am presented with a KDE desktop.
>>
>>
>> On 19/08/2009 21:44, Ben Brannen wrote:
>>>
>>> I need step by step instructions to setup - use a remote i.e. vnc or
>>> like connection to present a desktop - I'm trying jwm - but would be
>>> happy with even a blank gray screen for starters.
>>>
>>> I've tried for several days using several different methods and have
>>> had no luck.
>>> I think the problem might be in the way the IP's are configured but
>>> I'm not sure.
>>>
>>> What I need is this format:
>>> 1 key this in
>>> 2 set this value... located here.... to ....
>>> 3 key that in....
>>> etc....
>>>
>>> Several blogs, webpages etc have some of it and each web page assumes
>>> we know too much and is written as more of a refresher than a true
>>> step by step. I'm unable to reconcile it all.
>>>
>>> I've loaded co-linux with no problems. That was the easy part. Using
>>> a debian distro (default download) and it works great! I've started
>>> (or tried to start) the vnc / X servers / etc... But when I try to
>>> remote I get ..Connection refused.... I've tried RealVNC, TightVNC, IP
>>> from ifconfig, IP from Windows co-linux network connection,
>>> with/without :1, or :2 appended to the IP and several other
>>> combination's.
>>>
>>> Any help is greatly appreciated.
>>>
>>> -ben
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008
>>> 30-Day
>>> trial. Simplify your report design, integration and deployment - and
>>> focus on
>>> what you do best, core application coding. Discover what's new with
>>> Crystal Reports now. http://p.sf.net/sfu/bobj-july
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008
>> 30-Day
>> trial. Simplify your report design, integration and deployment - and focus
>> on
>> what you do best, core application coding. Discover what's new with
>> Crystal Reports now. http://p.sf.net/sfu/bobj-july
>> _______________________________________________
>> coLinux-users mailing list
>> coL...@li...
>> https://lists.sourceforge.net/lists/listinfo/colinux-users
>>
>
>
|
