Sponsored Content
Operating Systems Solaris How do I establish a remote CDE or JDS session on Solaris 10? Post 302091835 by ultra0384 on Thursday 5th of October 2006 10:38:30 AM
Old 10-05-2006
Holy $??? it worked! (XDMCP host connections under MacOS)

When I had a chance to sit down, i thought about the output from my previous Xnest attempt where it said something about interface 192.168.2.1. My iBook has two network interfaces, one for the wired ethernet, and one for the wireless. I already knew this was odd since the host i was connecting to was on the 192.168.1.0 network, which is the network the primary interface was on, while the 192.168.2.0 network's interface was not even active. I checked all of the network configurations making sure there were no firewalls enabled and no services that could be conflicting. Upon first glance there was not. I then noticed that the connection on one interface was being shared to another, and I have found that this feature when enabled, doesnt just route packets and issue dhcp configurations, but also sets up its own DNS server on the local machine among a few other things. For the sake of minimizing possible interfering services, I disabled this feature since I was not using it anyway. I then tried executing Xnest in the same syntax that i have been in the Apple X system and a window appears this time black instead of the default crossweaved pattern, and then soon after I am greeted to the system and asked for a login! I loged in and started the Java Desktop Session and then cried tears of joy! (ok i didn't cry, but i did log in as if i was at the console)

I am absolutely thrilled that this worked and I must say that I am very impressed with the MacOS, although at times I am a bit frustrated with the extra fatware, but never enough to wish it was not included.

So the lesson learned here is that for some odd reason, the "internet sharing " features in the MacOS interfere with XDMCP connections, and the service must be disabled in order for XDMCP and Xnest to work properly.

Thank you grial for your swift responses and patience to continue helping me. I appreciate it very much and I hope the value of what we have found out here will help other users on this forum as well.
 

10 More Discussions You Might Find Interesting

1. HP-UX

remote CDE

Is there a way to connect to CDE remotely? Preferably using 'VNC'. I'd like to do this! (4 Replies)
Discussion started by: satinet
4 Replies

2. AIX

No Keyboard in CDE session

Hi, AIX 5.3 , no Graphical adapter no Keyboard..... I set up CDE to start without graphical boot, dtlogin process is running, when start a xserver from Cygwin to access this box. I can't login, because I have no Keyboard. The Mouse works fine, but when I try to type in the username or... (1 Reply)
Discussion started by: hookerxy
1 Replies

3. Solaris

CDE Remote Login is not Working !!!

Hi , I have SunBlade 150 Workstation (Solaris 9), I installed the OS again then when I try to login to any server using ( Options > Remote Login > Enter Host Name) after I entered any host name nothing happened just white page for 2 or 3 mintues then the login screen reseted to the local... (4 Replies)
Discussion started by: adel8483
4 Replies

4. Solaris

I am not able to login in gnome session and java session in Sun solaris 9& 10

I am not able to login in gnome session and java session in Sun solaris 9& 10 respectively through xmanager as a nis user, I am able to login in common desktop , but gnome session its not allowing , when I have given login credentials, its coming back to login screen, what shoul I do to allow nis... (0 Replies)
Discussion started by: durgaprasadr13
0 Replies

5. Solaris

Not able to login through JDS but able to login through CDE

Dear All I am in a strange situation where I have install the Solaris 10 5/08 OS on Netra 1280 server. When I connect it through my laptop so that I can take the GUI from xmanager. When I try to login as root or any other users also through Java Destop Environment which accepted it after few... (3 Replies)
Discussion started by: girish.batra
3 Replies

6. HP-UX

Can not login to CDE -- only Fail Safe Session permitted

Hi, I am a hobbyist with a very old machine I have been trying to get up and running. I have an HP 9000/C240 with 1G of RAM and 3-8.5G HD. It is configured with 1G SWAP/DUMP. Currently only one drive is in use via LVM. I have not gotten around to creating more volumes just yet. It is running... (11 Replies)
Discussion started by: Dirk_
11 Replies

7. UNIX for Advanced & Expert Users

Xserver connect and run CDE session from Windows PC

Hope someone can help. I have 5 Unix Tru64 ver 4.0/5.1B, boxes and I'm trying to connect and run CDE session from my PC. I have tried using Reflections, and Xming with no luck. Can someone tell me what exactly needs to be running on the Tru64 boxes in order for this to work. Along with what or how... (4 Replies)
Discussion started by: Troberts50
4 Replies

8. HP-UX

Start SAM in TUI from CDE session

how can i start sam in TUI mode from a CDE session. i'm using hp-ux 11iv3 i tried to start SAM from a terminal from CDE session but each time i try to start it System Managment Homepage starts , so i telneted to server from a pc to start sam in TUI mode is there any other way to set my SAM to... (2 Replies)
Discussion started by: h@foorsa.biz
2 Replies

9. UNIX Desktop Questions & Answers

How to migrate Solaris 10 CDE config to HP-UX CDE.

Hello, Do you guys by any chance know what is the best (if any ) way to move CDE configuration from a SOLARIS 10 machine to HP-UX? Just the config (actions, text files etc). Thanks in advance! (0 Replies)
Discussion started by: binary0x01
0 Replies

10. HP-UX

Canīt get a remote desktop login through CDE

Hi all, I canīt get a remote desktop login through CDE only with root user. There are messages in the Xerror file: /usr/bin/X11/xset: bad font path element (#0), possible causes are: Directory does not exist or has wrong permissions Directory missing fonts.dir Incorrect font... (5 Replies)
Discussion started by: the0m3n
5 Replies
GRE(4)							   BSD Kernel Interfaces Manual 						    GRE(4)

NAME
gre -- encapsulating network device SYNOPSIS
To compile the driver into the kernel, place the following line in the kernel configuration file: device gre Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): if_gre_load="YES" DESCRIPTION
The gre network interface pseudo device encapsulates datagrams into IP. These encapsulated datagrams are routed to a destination host, where they are decapsulated and further routed to their final destination. The ``tunnel'' appears to the inner datagrams as one hop. gre interfaces are dynamically created and destroyed with the ifconfig(8) create and destroy subcommands. This driver corresponds to RFC 2784. Encapsulated datagrams are prepended an outer datagram and a GRE header. The GRE header specifies the type of the encapsulated datagram and thus allows for tunneling other protocols than IP. GRE mode is also the default tunnel mode on Cisco routers. gre also supports Cisco WCCP protocol, both version 1 and version 2. The gre interfaces support a number of additional parameters to the ifconfig(8): grekey Set the GRE key used for outgoing packets. A value of 0 disables the key option. enable_csum Enables checksum calculation for outgoing packets. enable_seq Enables use of sequence number field in the GRE header for outgoing packets. EXAMPLES
192.168.1.* --- Router A -------tunnel-------- Router B --- 192.168.2.* / / +------ the Internet ------+ Assuming router A has the (external) IP address A and the internal address 192.168.1.1, while router B has external address B and internal address 192.168.2.1, the following commands will configure the tunnel: On router A: ifconfig greN create ifconfig greN inet 192.168.1.1 192.168.2.1 ifconfig greN inet tunnel A B route add -net 192.168.2 -netmask 255.255.255.0 192.168.2.1 On router B: ifconfig greN create ifconfig greN inet 192.168.2.1 192.168.1.1 ifconfig greN inet tunnel B A route add -net 192.168.1 -netmask 255.255.255.0 192.168.1.1 NOTES
The MTU of gre interfaces is set to 1476 by default, to match the value used by Cisco routers. This may not be an optimal value, depending on the link between the two tunnel endpoints. It can be adjusted via ifconfig(8). For correct operation, the gre device needs a route to the decapsulating host that does not run over the tunnel, as this would be a loop. The kernel must be set to forward datagrams by setting the net.inet.ip.forwarding sysctl(8) variable to non-zero. SEE ALSO
gif(4), inet(4), ip(4), me(4), netintro(4), protocols(5), ifconfig(8), sysctl(8) A description of GRE encapsulation can be found in RFC 2784 and RFC 2890. AUTHORS
Andrey V. Elsukov <ae@FreeBSD.org> Heiko W.Rupp <hwr@pilhuhn.de> BUGS
The current implementation uses the key only for outgoing packets. Incoming packets with a different key or without a key will be treated as if they would belong to this interface. The sequence number field also used only for outgoing packets. BSD
November 7, 2014 BSD
All times are GMT -4. The time now is 03:40 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy