> We're running the 5.3 stack, and our systems guy did the "mandatory
> TCPIP update" as part of the upgrade to VMS 7.3-1. We're running on an
> alpha DS10. We aren't sure what the stack was under 7.3. Our alpha can
> talk to PLCs and other machines. Our systems guy broke down the
> connect packets and they look the same as the packets coming from
> machines that succeed in talking to the motor controller. He's
> scratching his head; I was hoping some resourceful puzzle-solver sys
> admin out there would say, "Oh, yeah, we've seen that; just diddle the
> Bill Manwaring, IUCF
Try showing some of the counters from the TCPIP utility and see if anything
is being dropped. You aren't running the two stacks at the same time,
right? It's possible that you have turned something on/off in the upgrade
that doesn't match your previous configuration. If the controller is really
dumb, is it possible that it has checksumming turned off?
> > Hi,
> > I think it's not VMS you have problems with, but the TCP/IP stack.
> > Which version do you run now ($ TCPIP SHOW VERSION) and which did you
> > run before ? Perhaps you've got a TCP/IP upgrade wioth your VMS upgrade!
> > Thomas
> > On Mon, 23 Jun 2003 11:46:31 -0500, Irving F. Snurd
> >> We upgraded from 7.3 to 7.3-1 and now cannot talk to a TCPIP motor
> >> controller (Parker CompuMotor 6k). We cannot telnet or "connect"
> >> (socket code), whereas we could do both with 7.3. We tried Linux,
> >> and vms 7.2, and they're both able to talk to it.
> >> The motor controller is sort of stupid; it does not respond to ARP
> >> broadcasts, so we bind the MAC address to the IP number in vms before
> >> we connect, but the source and destination MAC addresses are in the
> >> connect packet. The motor controller just does not want to respond
> >> to 7.3.
> >> Has anyone else had tcpip trouble? I guess we'll have to go back to
> >> 7.3.
> >> regards, Bill Manwaring, IUCF