Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

HP Print servers over PPP connection

0 views
Skip to first unread message

David H. Funte

unread,
Dec 21, 2000, 3:17:08 PM12/21/00
to
I've writen about this before (months ago) but i'm still having problems

I have two systems connected via 38k ppp

Both servers are running 5.04
Both servers can telnet back and forth

System A is 192.168.0.1 - 255.255.255.0
System B is 192.168.1.1 - 255.255.255.0

I have an HP 170x print server on system B. IP=192.168.1.15
I would like to send print jobs from system A to that print server but it
just doesn't seem to work.

When I ping from System A to the print server, I can see the Print server
LED flash but the Ping doesn't return to the user on System A. I've
noticed this behaviour before with these psevers and it was solved by
entering the Gateway address into the pserver configuration. I tried 0.1
and 1.1 as the Gateway and that didn't help.

Note: 0.10 and 1.10 are NICs


The routint table for System A is:
Destination Gateway Flags Refs Use Interface
127.0.0.1 127.0.0.1 UH 4 527 lo0
192.168 192.168.0.10 UC 1 0 net0
192.168.0.1 127.0.0.1 UGHS 0 6 lo0
192.168.0.10 127.0.0.1 UGHS 1 0 lo0
192.168.1 192.168.1.1 UG 0 9 ppp0
192.168.1.1 192.168.0.1 UH 10 6680 ppp0
224 192.168.0.10 UCS 0 0 net0
#


The routing table for System B is:
Destination Gateway Flags Refs Use Interface
127.0.0.1 127.0.0.1 UH 4 41053 lo0
192.168 192.168.1.1 UGS 0 1660 net1
192.168.0.1 192.168.1.1 UH 9 12520 ppp0
192.168.1 192.168.1.10 UC 1 0 net1
192.168.1.1 127.0.0.1 UGHS 1 2 lo0
192.168.1.10 127.0.0.1 UGHS 0 394 lo0
224 192.168.1.10 UCS 0 0 net1

traceroute command run on system A to 192.168.0.15 shows that it stops at
192.168.1.1. I'm confused.

thanks for any input

Steve Fabac

unread,
Dec 21, 2000, 6:25:41 PM12/21/00
to
David H. Funte wrote:
>
> I've writen about this before (months ago) but i'm still having problems
>
> I have two systems connected via 38k ppp
>
> Both servers are running 5.04
> Both servers can telnet back and forth
>
> System A is 192.168.0.1 - 255.255.255.0
> System B is 192.168.1.1 - 255.255.255.0
>
> I have an HP 170x print server on system B. IP=192.168.1.15
> I would like to send print jobs from system A to that print server but it
> just doesn't seem to work.
>
> When I ping from System A to the print server, I can see the Print server
> LED flash but the Ping doesn't return to the user on System A. I've
> noticed this behaviour before with these psevers and it was solved by
> entering the Gateway address into the pserver configuration. I tried 0.1
> and 1.1 as the Gateway and that didn't help.
>
> Note: 0.10 and 1.10 are NICs

David,

You have made the beginners mistake with PPP connections. And it's
easy to do as the documentation for ppp and networking is/was written
by persons who know the subject but don't know how to tell the reader
the things that they know and don't think about.

1) Each machine should be on a separate LAN: I.E. 192.168.1.X is one
LAN. 192.168.2.X is another LAN.

2) the PPP link between the two machines is a THIRD LAN and must have
a different network address than either of the two machine's LAN's:
PPP-machine-one: 192.168.20.1 and PPP-machine-two: 192.168.20.2.

Then your route table on machine one should have:
192.168.2 192.168.20.1 UH 10 6680 ppp0

And on machine 2:
192.168.1 192.168.20.2 ... ... ..... PPP0

Make sure that your print servers have the local machine's IP is set as
the "gateway" for its network, and make sure that both machines are
set to forward all packets.


Steve Fabac
S.M. Fabac & Associates
816/765-1670

Darryl Krasman

unread,
Dec 22, 2000, 9:06:05 PM12/22/00
to
Steve Fabac wrote:
>
> David,
>
> You have made the beginners mistake with PPP connections. And it's
> easy to do as the documentation for ppp and networking is/was written
> by persons who know the subject but don't know how to tell the reader
> the things that they know and don't think about.
>
> 1) Each machine should be on a separate LAN: I.E. 192.168.1.X is one
> LAN. 192.168.2.X is another LAN.
>
> 2) the PPP link between the two machines is a THIRD LAN and must have
> a different network address than either of the two machine's LAN's:
> PPP-machine-one: 192.168.20.1 and PPP-machine-two: 192.168.20.2.
>
> Then your route table on machine one should have:
> 192.168.2 192.168.20.1 UH 10 6680 ppp0
>
> And on machine 2:
> 192.168.1 192.168.20.2 ... ... ..... PPP0
>
> Make sure that your print servers have the local machine's IP is set as
> the "gateway" for its network, and make sure that both machines are
> set to forward all packets.
>
> Steve Fabac
> S.M. Fabac & Associates
> 816/765-1670
>

I get along fine from home to/from work via ppp without the need for a
third network for ppp. You'll need to add "proxy" to the ppp
configuration (SCO PPP). For example, work is 192.168.1. & home is
192.168.37. :

home side:
# grep icg /etc/ppphosts
icg-thor:thor-icg uucp=icgppp accm=0 mask=255.255.255.0 filter=thor
flow=rtsc
ts proxy mru=1536
*ideacom local=thor-icg remote=icg-thor accm=0 filter=thor flow=rtscts
proxy
mru=1536
# ifconfig ppp0
ppp0: flags=4071<UP,POINTOPOINT,WANTIOCTLS,RUNNING,MULTICAST> mtu 1536
inet 192.168.37.9 --> 192.168.1.181 netmask ffffff00
perf. params: recv size: 32768; send size: 32768; full-size
frames: 1
Routing tables


Destination Gateway Flags Refs Use Interface

default 192.168.1.181 UGS 8 76594 ppp0

work side:
# grep thor /etc/ppphosts
*thor local=icg-thor filter=default remote=thor-icg accm=0 idle=2
flow=rtscts mru=
1536
thor-icg:icg-thor filter=default uucp=thorppp retry=0 accm=0
mask=255.255.255.0 id
le=2 flow=rtscts mru=1536
# /etc/ifconfig ppp0
ppp0: flags=4071<UP,POINTOPOINT,WANTIOCTLS,RUNNING,MULTICAST> mtu 1536
inet 192.168.1.181 --> 192.168.37.9 netmask ffffff00
perf. params: recv size: 32768; send size: 32768; full-size
frames: 1
Routing tables


Destination Gateway Flags Refs Use Interface

192.168.37 192.168.37.9 UGS 0 17419 ppp0
192.168.37.9 192.168.1.181 UH 3 591307 ppp0

From home I can ping every PC, printer, diskless workstation
(www.ltsp.org) or ethernet terminal at work and from work, everything at
home.
--
Darryl
Ideal Computer Group Inc.

Steve Fabac

unread,
Dec 23, 2000, 10:31:12 PM12/23/00
to


What's the complete routing table look like? From the above description,
I can't tell what the Office and Home LAN networks are. Without that
information, I am unable to analyze the above information.


Steve Fabac
S.M. Fabac & Associates
816/765-1670


>

Darryl Krasman

unread,
Dec 27, 2000, 12:52:13 AM12/27/00
to
Steve Fabac wrote:

> What's the complete routing table look like? From the above description,
> I can't tell what the Office and Home LAN networks are. Without that
> information, I am unable to analyze the above information.
>

What other information are you specifically looking for. I included all
the nasty bits including each end of the PPP link configurations. The
only other thing not included was the usual mapping SCOPPP does of the
local side of the PPP link to 127.0.0.1.

Steve Fabac

unread,
Dec 27, 2000, 5:59:51 AM12/27/00
to


What is the LAN IP address of
each SCO box at each end of the
PPP link? Without that information how can
anyone tell if your network configuration is
sane?

Darryl Krasman

unread,
Dec 28, 2000, 12:55:54 AM12/28/00
to
Steve Fabac wrote:

>
> Darryl Krasman wrote:
> What is the LAN IP address of
> each SCO box at each end of the
> PPP link? Without that information how can
> anyone tell if your network configuration is
> sane?

Nice spacing. Home SCO box is 192.168.37.1, work SCO box is
192.168.1.180 with netmasks of 255.255.255.0 all 'round.

Steve Fabac

unread,
Dec 27, 2000, 8:16:10 PM12/27/00
to
> Steve Fabac wrote:
> >
> > Darryl Krasman wrote:
> > What is the LAN IP address of
> > each SCO box at each end of the
> > PPP link? Without that information how can
> > anyone tell if your network configuration is
> > sane?
>
> Nice spacing. Home SCO box is 192.168.37.1, work SCO box is
> 192.168.1.180 with netmasks of 255.255.255.0 all 'round.
> --
> Darryl
> Ideal Computer Group Inc.

Thank you for your information. I have never tried the "proxy" statement
in ppphosts. From your description and success, I'll have to give it
a try.

Darryl Krasman

unread,
Dec 28, 2000, 5:57:53 AM12/28/00
to
Steve Fabac wrote:
>
> Thank you for your information. I have never tried the "proxy" statement
> in ppphosts. From your description and success, I'll have to give it
> a try.

Yep, the "proxy" option in ppphosts does the trick. I looked back at the
information I posted and see that I also have the mru=1536. That did not
increase the performance much if any but it didn't seem to hurt it
either so I guess I left it. To get more performance out of SCO PPP
crank up the recv-size & send-size via modifying your /etc/ppphook.sh
(or specified ppphosts one) to do an '/etc/ifconfig $2 perf 32768 32768
1' in the 'add' section or use inconfig to set /etc/default/inet default
values.

David H. Funte

unread,
Dec 28, 2000, 1:39:43 PM12/28/00
to

>
> I get along fine from home to/from work via ppp without the need for a
> third network for ppp. You'll need to add "proxy" to the ppp
> configuration (SCO PPP). For example, work is 192.168.1. & home is
> 192.168.37. :
>
> home side:
> # grep icg /etc/ppphosts
> icg-thor:thor-icg uucp=icgppp accm=0 mask=255.255.255.0 filter=thor
> flow=rtsc
> ts proxy mru=1536
> *ideacom local=thor-icg remote=icg-thor accm=0 filter=thor flow=rtscts
> proxy
> mru=1536


Interesting stuff: But I noticed that the "proxy" statement was only added
in your home system. Does this prevent people at the office from pinging
you?

In my case, I'll have print servers on both sides of the network. I assume
I'll need to add the "proxy" statement to both ppphosts files?

Thanks for All your help - sorry I didn't reply sooner

Darryl Krasman

unread,
Jan 2, 2001, 9:27:44 PM1/2/01
to
"David H. Funte" wrote:
> Interesting stuff: But I noticed that the "proxy" statement was only added
> in your home system. Does this prevent people at the office from pinging
> you?

Looks like I'm being a little sloppy. Originally my home machine was an
only child with no network card and part of the 192.168.1.x network.
That setup seemed to require the "proxy" for all PCs at work to know
about it. Now with the separate networks at both ends the "proxy" really
isn't required.


> In my case, I'll have print servers on both sides of the network. I assume
> I'll need to add the "proxy" statement to both ppphosts files?

Nope, just have your routing correct and you should be fine.

0 new messages