[EMAIL PROTECTED] wrote, On 11/14/02 15:26:

I checked with our network/netware guy, and he's told me that we're
running "0 interface with an Ethernet_II frame", so I've got fxp0f0
configured with our network number, which he's given me as 0x83a2c800
Yust for fun - 0x83a2c800=131.162.200.0, so your try to hide real IP by "xx"ing it has failed.

Our network is a B-Class, with from x.x.128.x up being divided into
subnets of 8 C-classes each ... so subnet 128, 136, 144, etc ...

our netware server is on subnet 200, which is the 83a2c800 that he's given

Well - we must diferentiate what we are speaking about.

If you are trying to set up IPX network, then the informations about IP network topology is irelevant. You need to know the IPX network topology, IPX network numbers and so on. I don't know what the 0x83A2C800 number is - it seems to be IP not IPX network number, but I'm not sure. You should ask your Netware server administrator.

me ... the computer I'm working on is a laptop, so will be on several
different subnets, but never on subnet 200 ... is 83a2c800 the netnum
The correct IPX network number must be set to the same number as the IPX network number assigned to network avaiable on cable you are connected in. Under Windows seems to be possible set the IPX network to 0x000000 requesting autodetection of the correct value.

As you know, there must be a properly configured IPX router between you and server unless your IPX adress is from the same IPX NET as server's (it is similar law as for IP)

Dan


--
Dan Lukes tel: +420 2 21914205, fax: +420 2 21914206
root of FIONet, KolejNET, webmaster of www.freebsd.cz
AKA: [EMAIL PROTECTED], [EMAIL PROTECTED],[EMAIL PROTECTED]



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message

Reply via email to