XDMCP on Windows 95

[J S]

>
>J S wrote:
>
> > Would I be right
> > in saying though that the most likely cause has got to be something 
>windows
> > 95-network related since the original message said invalid address and 
>this
> > only occurs on win 95?
>
>Have you already tried the ls_netdev tool as suggested?
>
>bye
>     ago
>--

Hi Alex,

Sorry I didn't realise what ls_netdev was before. I will try it tomorrow 
when I go back to work. Also I've just tried to run xdmcp from home (over 
PPP) but it failed. Nothing was written to xwin.log but I tried ls_netdev 
and got the following:

BASH-2.05b$ xwin -query 161.2.3.54 -from 161.2.160.45
BASH-2.05b$ ls
Makefile  ls_netdev  ls_netdev-w95.exe  ls_netdev.c  ls_netdev.exe
BASH-2.05b$ ls_netdev.exe
ls_netdev $Id: ls_netdev.c,v 1.6 2002/11/10 16:14:32 ago Exp $
OS Version: Windows 9x 4.10 Build 67766446  A
Querying devices using ioctl
lo: family=TCP/IP (0) addr=127.0.0.1
eth0: family=TCP/IP (0) addr=161.2.160.45
lo: metric=1 mtu=276
eth0: metric=1 mtu=1500
Querying devices using internal function
ifname: "0000"
driver: "NetTrans\0000"
IPAddress: "0.0.0.0", IPMask: "0.0.0.0"
AdapterName: "MS$PPP"
lo: family=TCP/IP (0) addr=127.0.0.1
ppp0: family=TCP/IP (0) addr=0.0.0.0
BASH-2.05b$

Anything suspicious there?

_________________________________________________________________
Protect your PC - get McAfee.com VirusScan Online 
http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963