08-11-2009
XDMCP is a protocol in its own right. It may well be that this protocol is blocked by the router/switch/firewall/whatever is connecting the two subnets.
Firewalls are known to block most things not absolutely necessary and it might well be that you have to request it specifically to be opened for the necessary port/protocol.
You could examine what comes through to the AIX machine by setting up a tcpdump (man tcpdump) and then trying to connect from home via XDMCP. Chances are your packets don't come even near the AIX machine.
I hope this helps.
bakunin
10 More Discussions You Might Find Interesting
1. AIX
Hello.
I want to know how to start CDE on AIX, to export the console under reflection.
What commands are necesary to run on AIX to start CDE and after start It export the console using Reflection X.
Someboy know how to do that.
Regards (1 Reply)
Discussion started by: hmoday
1 Replies
2. AIX
When we as normal user try to login, the session startup terminates and we are presented with the login screen.The root user is able to login without any problem.I can log in to the Aix server as normal user through telnet & using xmanager but not directly through server terminal .The Aix version... (1 Reply)
Discussion started by: ranadeep
1 Replies
3. Solaris
i am connected to SC port
i can use cde mode connecting SC
if yes kindly tell me the procedure (2 Replies)
Discussion started by: rizwan225
2 Replies
4. AIX
Hi, can somebody please, please help me?
After a power loss and server restart my server running AIX 4.2.2 could not boot. Following the procedure in my user guide
I checked the hd's with
# fsck -y /dev/hd1
# fsck -y /dev/hd2
# fsck -y /dev/hd3
# fsck -y /dev/hd4
# fsck -y /dev/hd9var
I... (0 Replies)
Discussion started by: semso
0 Replies
5. UNIX for Dummies Questions & Answers
Hi, can somebody please, please help me?
After a power loss and server restart my server running AIX 4.2.2 could not boot. Following the procedure in my user guide
I checked the hd's with
# fsck -y /dev/hd1
# fsck -y /dev/hd2
# fsck -y /dev/hd3
# fsck -y /dev/hd4
# fsck -y /dev/hd9var
... (4 Replies)
Discussion started by: semso
4 Replies
6. UNIX Desktop Questions & Answers
I recently acquired an IBM RS6000 43P with only the bare OS (AIX 5.1) loaded. I would like to run Common Desktop Environment but I don't know
the prerequisite s/w to get, the order in which to load it, and any variables I need to define when loading.
I would appreciate any directions offered.... (1 Reply)
Discussion started by: ki6bxp
1 Replies
7. AIX
Hi all,
I want to install CDE on AIX 5.3 - TL 10 , X server already installed and most X applications works fine.
i made iso files for 3 out of 8 volumes for the aix ( itried only 3 out of 8 with no luck ), and i mounted them as if they were filesystems.
then i ran
#smit install_all
and... (2 Replies)
Discussion started by: h@foorsa.biz
2 Replies
8. Red Hat
Greetings!
Theres an application in my RHEL 6 server that has a GUI (which we'd like to use). When I run the AppGui.sh is says it needs Server X11.
I know its gotta do something with X server (and I installed it).I found some tutorial for auto configuration and then I was supposed to access... (0 Replies)
Discussion started by: RedSpyder
0 Replies
9. AIX
Dears
I am looking for this binary to complete my X11 installation and I can not find it in the media , can any one help me where can I download it
X11.loc.en_US.Dt.rte AIX CDE Locale Configuration - U.S. English (1 Reply)
Discussion started by: thecobra151
1 Replies
10. AIX
On other unix systems,simply set "dtsession" on .xstartup file of vnc
start the cde session.
On aix i have this problem when i start the session,appear only an error message
The DT messaging system could not be started
to correct the problem
1. Choose ok to return to the login... (2 Replies)
Discussion started by: Linusolaradm1
2 Replies
LEARN ABOUT FREEBSD
ipresend
IPRESEND(1) General Commands Manual IPRESEND(1)
NAME
ipresend - resend IP packets out to network
SYNOPSIS
ipresend [ -EHPRSTX ] [ -d <device> ] [ -g <gateway> ] [ -m <MTU> ] [ -r <filename> ]
DESCRIPTION
ipresend was designed to allow packets to be resent, once captured, back out onto the network for use in testing. ipresend supports a num-
ber of different file formats as input, including saved snoop/tcpdump binary data.
OPTIONS
-d <interface>
Set the interface name to be the name supplied. This is useful with the -P, -S, -T and -E options, where it is not otherwise possi-
ble to associate a packet with an interface. Normal "text packets" can override this setting.
-g <gateway>
Specify the hostname of the gateway through which to route packets. This is required whenever the destination host isn't directly
attached to the same network as the host from which you're sending.
-m <MTU>
Specify the MTU to be used when sending out packets. This option allows you to set a fake MTU, allowing the simulation of network
interfaces with small MTU's without setting them so.
-r <filename>
Specify the filename from which to take input. Default is stdin.
-E The input file is to be text output from etherfind. The text formats which are currently supported are those which result from the
following etherfind option combinations:
etherfind -n
etherfind -n -t
-H The input file is to be hex digits, representing the binary makeup of the packet. No length correction is made, if an incorrect
length is put in the IP header.
-P The input file specified by -i is a binary file produced using libpcap (i.e., tcpdump version 3). Packets are read from this file
as being input (for rule purposes).
-R When sending packets out, send them out "raw" (the way they came in). The only real significance here is that it will expect the
link layer (i.e. ethernet) headers to be prepended to the IP packet being output.
-S The input file is to be in "snoop" format (see RFC 1761). Packets are read from this file and used as input from any interface.
This is perhaps the most useful input type, currently.
-T The input file is to be text output from tcpdump. The text formats which are currently supported are those which result from the
following tcpdump option combinations:
tcpdump -n
tcpdump -nq
tcpdump -nqt
tcpdump -nqtt
tcpdump -nqte
-X The input file is composed of text descriptions of IP packets.
SEE ALSO
snoop(1m), tcpdump(8), etherfind(8c), ipftest(1), ipresend(1), iptest(1), bpf(4), dlpi(7p)
DIAGNOSTICS
Needs to be run as root.
BUGS
Not all of the input formats are sufficiently capable of introducing a wide enough variety of packets for them to be all useful in testing.
If you find any, please send email to me at darrenr@pobox.com
IPRESEND(1)