We have had to revert our network to the original subnet, prior to
converting it en bloc when we can. We run a very old version of DU
(3.0b) on which aliasing is "not supported" - had aliasing been
supported, as it is in later versions then we could have used the
ifconfig statement in inet to configure the system.
> -----Original Message-----
> From: Chris Rogers [SMTP:chrisr_at_kenttec.demon.co.uk]
> Sent: Tuesday, April 07, 1998 4:55 PM
> To: 'Alpha OSF Managers'
> Subject: Printer Addressing
>
>
>
> > -----Original Message-----
> > From: Chris Rogers
> > Sent: Tuesday, April 07, 1998 4:21 PM
> > To: 'Alpha OSF Managers'
> > Subject:
> >
> > Until recently I had a setup whereby I could print to a printer on a
> > Netware network that was connected to my AlphaServer. Then we
> decided
> > to change our networking operations to a Windows NT environment. In
> > the process of doing so our network manager altered the TCP/IP
> address
> > of the printer to a different subnet mask (was 85.5.5.210 - changed
> to
> > 10.1.1.65) and now I can no longer see the printer. The lpstat
> command
> > tells me that the printer is down. I don't know how to tell my
> > alphaserver how to find the printer again. I suspect that I have to
> > play with the /etc/routes, /etc/networks or /etc/gateways files -
> but
> > I'm at a loss to know how exactly to modify these to get the desired
> > effect.
> >
> > If I try to ping any machines on the new subnet mask I get no reply.
> I
> > can still ping machines on the old subnet mask, but as the rollout
> of
> > NT progresses I will not be able to do this for much longer.
> >
> > I'd appreciate a little advice.
> >
> > Chris Rogers
Received on Mon Apr 27 1998 - 15:38:24 NZST