Re: TCPIP+LinkSys+Win2K+OpenVMS Adventures
David J. Dachtera
>
> Hi,
>
> *** In words:
> I have installed TCPIP V5.4 on my OpenVMS V7.3-2 Alpha.
>
> My OpenVMS Alpha is on a small Linksys BEFSR41 LAN along with my Win2K
> box. I would like to be able to telnet/X from Win2K to OpenVMS. I would
> also like to have an OpenVMS NFS share accessible by Win2K.
>
> The Alpha. has 2 ethernet network cards. If I've got this right, as you
> face the rear of the Alpha, the lowermost card (next to serial
> interfaces, etc.) is WE0. The other interface is WE1. My ethernet cable
> is attached to WE0.
>
> My Win2K system accesses the net (and the Linksys router) with no
> problems. However, the Win2K system can't/doesn't successfully
> ping/telnet/ftp to the OpenVMS box on WE0. For some strange reason, you
> can get a ping/ftp through on an alternate (see below) IP-address. I
> can't get a telnet through on the alternate IP-address. The OpenVMS box
> cannot ping/telnet/ftp the Win2K box. And, often as not, you get
> timeouts for those things that do work (see below). The OpenVMS box can
> ping the Linksys router.
>
> Both the Win2K and OpenVMS platforms can ping/telnet/ftp to
> themselves.
>
> *** In versions and commands:
> The Linksys router is at firmware V1.46.2.
>
> The Linksys box does static IP-addressing. It is 192.168.1.1 with a
> submask of 255.255.255.0 (MTU 1500).
> The Win2K box has an IP-address/mask of 192.168.1.2/255.255.255.0 with
> default gateway of 192.168.1.1.
> The OpenVMS system has IP-address/mask of 192.168.1.5/255.255.255.0
> with default gateway of 192.168.1.1. The IP-address/mask of
> 192.168.1.6/255.255.255.0 was my attempt to use failover-IP with the
> second ethernet card.
>
> On OpenVMS:
> show interface:
> L00 127.0.0.1 255.0.0.0
> WE0 192.168.1.5 255.255.255.0
> WEB0 192.168.1.5 255.255.255.0
> WE1 192.168.1.6 255.255.255.0
>
> show route:
> AN 0.0.0.0 192.168.1.1
> AH 127.0.0.1 127.0.0.1
> AN 192.168.1.0/24 192.168.1.6
> AN 192.168.1.0.24 192.168.1.5
> AH 192.168.1.5 192.168.1.5
> AH 192.168.1.6 192.168.1.6
> [snip]
Hi, Chuck,
You'll want to check out this post of mine to
vmsnet.networks.tcp-ip.ucx. Note the lack of response to it:
Sorry if the long URL wraps.
Essentially with UCX, having two interfaces on the same subnet is a
major no-no since you can't defeat the round robin routing without
manually editing the dynamic routes.
This is a known issue. The support folks are stumped. I've opened
numerous tickets, none of which have lead to a resolution. There is no
known fix, and only the one known work-around (manually editing the
dynamic routes).
--
David J Dachtera
dba DJE Systems
http://www.djesys.com/
Unofficial OpenVMS Marketing Home Page
http://www.djesys.com/vms/market/
Unofficial Affordable OpenVMS Home Page:
http://www.djesys.com/vms/soho/
Unofficial OpenVMS-IA32 Home Page:
http://www.djesys.com/vms/ia32/
Unofficial OpenVMS Hobbyist Support Page:
http://www.djesys.com/vms/support/
Schnootling
Well ... I WAS ABLE TO GET IN !!!!
I got me 2 ethernet cards on my Alpha. To make a long (see appendix to
this note) story shorter: I disabled one of the cards, the EWA0 card,
via the TCPIP SET NOINTERFACE WE0 command. This was the interface using
192.168.1.5. Now, I have 4 Win2K telnet sessions open to the Alpha. I'm
so happy I think I'll have a chocolate brownie-bite.
Thanks again to everyone on, and off, this newsgroup who helped me.
Chuck's Networking Odyssey
or "The (Interface) Card and I"
P.S. The circuitous route (puns intended):
RUN SYS$SYSTEM:LANCP
LANCP>show device /characteristics
(EWB0 is set to full-duplex+100Mb/s, EWA0 is set to half-duplex+10Mb/s)
LANCP>set device ewa0 /full_duplex /speed=100
... now, EWB0=192.168.1.6 and EWA0=192.168.1.5 . And, I had thought
from day-one that 192.168.1.5 was what I wanted/was-going to use. I
dreamed up 192.168.1.6 as a "failover" address 'cause I thought that
was what you did for failover. And after the SET DEVICE, the PINGs did
seem to run "faster" going from Alpha to Win2K. However I'm still
getting 50% PING packet loss from Win2K to Alpha on 192.168.1.6.
Telnet and PING to 192.168.1.5 still fail miserably. However, telnet to
192.168.1.6 WORKS !
I logout and try it again (i.e. telnet to 192.168.1.6) and it DOESN'T
WORK. High-pitched scream echoes through downtown. Scratch head.
Recycle TCPIP on Alpha. Decide to go-with-the-flow:
TCPIP SET NOINTERFACE WE0 ... (i.e. disable the one=192.168.1.5 that
was originally at half-duplex+10Mb/s... which I had thought was the
'correct' one to use)
Voila' : I get login prompts, thereby demonstrating that all computers
work by a mixture of chance and magic.
Yes, the two cards were messing each other, and me, up. No, I don't
understand what was going on. Yet. Thanks again everyone.
Tom Linden
wrote:
Did you try
ifconfig we0 alias 192.168.1.5 netmask 255.255.0.0
I don't think you needed a second card.
Schnootling
No, I didn't. I was happy just to be able to telnet in.
After installing PL/1 and a few other things, I'll (gulp) try it.
Thanks for the suggestion.
Cautiously Optimistic Chuck