network hook up for Win 10 laptop on Freebsd

[al plant]

Aloha List,

I have aquired a Dell Laptop Inspiron 14 -3452 Windows 10 O/S.

Box has Hdmi, USB and media card reader ports . Also Wireless network
hookup.

The network is FreeBSD 8 and has an old HP Laser jet printer and several
desktops with FreeBSD that work with the printer.

We want to print email received on the Dell on the network. The FreeBSD network is hardwired with cables and connectors. The Telcom link to internet is wireless and cable mixed.

Any ideas how I can do this with the new Dell? Can I use converter connectors to the cable and connect the Dell to the switch that the other working units connect to now.

Thanks for any ideas.


~ Al Plant - Honolulu, Hawaii - Phone: [phone] ~
Supporting FreeBSD - UNIX Computer O/S
email: ***@hdk5.net email: alplant.att.net
."All that's really worth doing is what we do for others" - Lewis Carrol

[Warren Block]

Post by al plant
Aloha List,
I have aquired a Dell Laptop Inspiron 14 -3452 Windows 10 O/S.
Box has Hdmi, USB and media card reader ports . Also Wireless network hookup.
The network is FreeBSD 8 and has an old HP Laser jet printer and several
desktops with FreeBSD that work with the printer.
We want to print email received on the Dell on the network. The FreeBSD
network is hardwired with cables and connectors. The Telcom link to internet
is wireless and cable mixed.
Any ideas how I can do this with the new Dell? Can I use converter connectors
to the cable and connect the Dell to the switch that the other working units
connect to now.

Is the "FreeBSD network" connected to the wired port of the cable box?
The wireless portion is probably shared with the wired. From the
notebook, ping the laser printer. Odds are good that will work.

The step after that is adding a printer on the Windows system. The
trick there used to be telling it to use a "local port", then creating a
port for the IP address of the printer. I don't know if or how much
Microsoft might have changed that in later versions of Windows. Which
version do you have?

[al plant]

Post by Warren Block

Post by al plant
Aloha List,
I have aquired a Dell Laptop Inspiron 14 -3452 Windows 10 O/S.
Box has Hdmi, USB and media card reader ports . Also Wireless network
hookup.
The network is FreeBSD 8 and has an old HP Laser jet printer and
several desktops with FreeBSD that work with the printer.
We want to print email received on the Dell on the network. The
FreeBSD network is hardwired with cables and connectors. The Telcom
link to internet is wireless and cable mixed. Any ideas how I can do
this with the new Dell? Can I use converter connectors to the cable
and connect the Dell to the switch that the other working units
connect to now.

Is the "FreeBSD network" connected to the wired port of the cable box?
The wireless portion is probably shared with the wired. From the
notebook, ping the laser printer. Odds are good that will work.
The step after that is adding a printer on the Windows system. The
trick there used to be telling it to use a "local port", then creating
a port for the IP address of the printer. I don't know if or how much
Microsoft might have changed that in later versions of Windows. Which
version do you have?

Thanks Warren, I will look at this.

Windows 10

My wife works with a mix of mac, windows at her job and her It guy has
had a couple of issues that never were reserved mostly to do with age of
printers. This we hoped to side step by the network. I cant figure out
how you get the network hooked to the windows. I am looking to info on
what ports could work on the box.

Thanks


~ Al Plant - Honolulu, Hawaii - Phone: [phone] ~
Supporting FreeBSD - UNIX Computer O/S
email: ***@hdk5.net email: alplant.att.net
."All that's really worth doing is what we do for others" - Lewis Carrol

[Valeri Galtsev]

Post by al plant

Post by Warren Block

Post by al plant
Aloha List,
I have aquired a Dell Laptop Inspiron 14 -3452 Windows 10 O/S.
Box has Hdmi, USB and media card reader ports . Also Wireless network
hookup.
The network is FreeBSD 8 and has an old HP Laser jet printer and
several desktops with FreeBSD that work with the printer.
We want to print email received on the Dell on the network. The
FreeBSD network is hardwired with cables and connectors. The Telcom
link to internet is wireless and cable mixed. Any ideas how I can do
this with the new Dell? Can I use converter connectors to the cable
and connect the Dell to the switch that the other working units
connect to now.

Is the "FreeBSD network" connected to the wired port of the cable box?
The wireless portion is probably shared with the wired. From the
notebook, ping the laser printer. Odds are good that will work.
The step after that is adding a printer on the Windows system. The
trick there used to be telling it to use a "local port", then creating
a port for the IP address of the printer. I don't know if or how much
Microsoft might have changed that in later versions of Windows. Which
version do you have?

They didn't change anything. You can create two kind of ports (at least
two). Namely: you can create "raw" port, and give there IP address of the
printer. This printer has to listen to "jetdirect" port (9100) for this to
work. The other way is if printer listens to LPD ("spooler") port (port
number 515) (or better: print server, - I usually set up all printer to
only accept print jobs from print server - easier to manage especially if
something is wrong with some client). In this case, you need to enable two
services on Windows side (through "turning on features"): UNIX printing
related: "LPD Print Service" and "LPR Port Monitr". This teaches Windows
talk UNIX printing language, you then create local port of type LPD (and
put remote LPD server's IP there). I found this to be the most robust way
of having Windows printing to UNIX print queues.

I hope, this helps.

Valeri

Post by al plant
Thanks Warren, I will look at this.
Windows 10
My wife works with a mix of mac, windows at her job and her It guy has
had a couple of issues that never were reserved mostly to do with age of
printers. This we hoped to side step by the network. I cant figure out
how you get the network hooked to the windows. I am looking to info on
what ports could work on the box.
Thanks
~ Al Plant - Honolulu, Hawaii - Phone: [phone] ~
Supporting FreeBSD - UNIX Computer O/S
."All that's really worth doing is what we do for others" - Lewis Carrol
_______________________________________________
https://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to

++++++++++++++++++++++++++++++++++++++++
Valeri Galtsev
Sr System Administrator
Department of Astronomy and Astrophysics
Kavli Institute for Cosmological Physics
University of Chicago
Phone: [phone]
++++++++++++++++++++++++++++++++++++++++

[al plant]

Post by Valeri Galtsev

Post by al plant

Post by Warren Block

Post by al plant
Aloha List,
I have aquired a Dell Laptop Inspiron 14 -3452 Windows 10 O/S.
Box has Hdmi, USB and media card reader ports . Also Wireless network
hookup.
The network is FreeBSD 8 and has an old HP Laser jet printer and
several desktops with FreeBSD that work with the printer.
We want to print email received on the Dell on the network. The
FreeBSD network is hardwired with cables and connectors. The Telcom
link to internet is wireless and cable mixed. Any ideas how I can do
this with the new Dell? Can I use converter connectors to the cable
and connect the Dell to the switch that the other working units
connect to now.

Is the "FreeBSD network" connected to the wired port of the cable box?
The wireless portion is probably shared with the wired. From the
notebook, ping the laser printer. Odds are good that will work.
The step after that is adding a printer on the Windows system. The
trick there used to be telling it to use a "local port", then creating
a port for the IP address of the printer. I don't know if or how much
Microsoft might have changed that in later versions of Windows. Which
version do you have?

They didn't change anything. You can create two kind of ports (at least
two). Namely: you can create "raw" port, and give there IP address of the
printer. This printer has to listen to "jetdirect" port (9100) for this to
work. The other way is if printer listens to LPD ("spooler") port (port
number 515) (or better: print server, - I usually set up all printer to
only accept print jobs from print server - easier to manage especially if
something is wrong with some client). In this case, you need to enable two
services on Windows side (through "turning on features"): UNIX printing
related: "LPD Print Service" and "LPR Port Monitr". This teaches Windows
talk UNIX printing language, you then create local port of type LPD (and
put remote LPD server's IP there). I found this to be the most robust way
of having Windows printing to UNIX print queues.
I hope, this helps.
Valeri

Post by al plant
Thanks Warren, I will look at this.
Windows 10
My wife works with a mix of mac, windows at her job and her It guy has
had a couple of issues that never were reserved mostly to do with age of
printers. This we hoped to side step by the network. I cant figure out
how you get the network hooked to the windows. I am looking to info on
what ports could work on the box.
Thanks
~ Al Plant - Honolulu, Hawaii - Phone: [phone] ~
Supporting FreeBSD - UNIX Computer O/S
."All that's really worth doing is what we do for others" - Lewis Carrol
_______________________________________________
https://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to

++++++++++++++++++++++++++++++++++++++++
Valeri Galtsev
Sr System Administrator
Department of Astronomy and Astrophysics
Kavli Institute for Cosmological Physics
University of Chicago
Phone: [phone]
++++++++++++++++++++++++++++++++++++++++
_______________________________________________
https://lists.freebsd.org/mailman/listinfo/freebsd-questions

Thanks Valeri,

~ Al Plant - Honolulu, Hawaii - Phone: [phone] ~
Supporting FreeBSD - UNIX Computer O/S
email: ***@hdk5.net email: alplant.att.net
."All that's really worth doing is what we do for others" - Lewis Carrol

[Warren Block]

Post by Valeri Galtsev
They didn't change anything. You can create two kind of ports (at least
two). Namely: you can create "raw" port, and give there IP address of the
printer. This printer has to listen to "jetdirect" port (9100) for this to
work. The other way is if printer listens to LPD ("spooler") port (port
number 515) (or better: print server, - I usually set up all printer to
only accept print jobs from print server - easier to manage especially if
something is wrong with some client). In this case, you need to enable two
services on Windows side (through "turning on features"): UNIX printing
related: "LPD Print Service" and "LPR Port Monitr". This teaches Windows
talk UNIX printing language, you then create local port of type LPD (and
put remote LPD server's IP there). I found this to be the most robust way
of having Windows printing to UNIX print queues.

I've used raw port 9100 printing to HP JetDirects many times. It's nice
because it has no other dependencies.

[Valeri Galtsev]

Post by Warren Block

Post by Valeri Galtsev
They didn't change anything. You can create two kind of ports (at least
two). Namely: you can create "raw" port, and give there IP address of
the
printer. This printer has to listen to "jetdirect" port (9100) for this
to
work. The other way is if printer listens to LPD ("spooler") port (port
number 515) (or better: print server, - I usually set up all printer to
only accept print jobs from print server - easier to manage especially
if
something is wrong with some client). In this case, you need to enable
two
services on Windows side (through "turning on features"): UNIX printing
related: "LPD Print Service" and "LPR Port Monitr". This teaches Windows
talk UNIX printing language, you then create local port of type LPD (and
put remote LPD server's IP there). I found this to be the most robust
way
of having Windows printing to UNIX print queues.

I've used raw port 9100 printing to HP JetDirects many times. It's nice
because it has no other dependencies.

I agree if you have one to 5 or so clients. If you have 100+ clients, you
better don't let them print directly to the printer, and instead make them
print through print server. One client acts up (say, hits consistently bug
in postscript implementation of the printer that knocks printer out; and
keeps re-sending print job every time you power cycle printer) - you will
see the world of difference. You can pinpoint what comes from which client
if all goes through print server. UNIX machine as print server will
provide you with much more than brainless embedded system printers have
inside. But for few clients, as you said, the effort is not worth it.

Valeri

++++++++++++++++++++++++++++++++++++++++
Valeri Galtsev
Sr System Administrator
Department of Astronomy and Astrophysics
Kavli Institute for Cosmological Physics
University of Chicago
Phone: [phone]
++++++++++++++++++++++++++++++++++++++++

[Polytropon]

Post by Valeri Galtsev

Post by Warren Block

Post by Valeri Galtsev
They didn't change anything. You can create two kind of ports (at least
two). Namely: you can create "raw" port, and give there IP address of
the
printer. This printer has to listen to "jetdirect" port (9100) for this
to
work. The other way is if printer listens to LPD ("spooler") port (port
number 515) (or better: print server, - I usually set up all printer to
only accept print jobs from print server - easier to manage especially
if
something is wrong with some client). In this case, you need to enable
two
services on Windows side (through "turning on features"): UNIX printing
related: "LPD Print Service" and "LPR Port Monitr". This teaches Windows
talk UNIX printing language, you then create local port of type LPD (and
put remote LPD server's IP there). I found this to be the most robust
way
of having Windows printing to UNIX print queues.

I've used raw port 9100 printing to HP JetDirects many times. It's nice
because it has no other dependencies.

I agree if you have one to 5 or so clients. If you have 100+ clients, you
better don't let them print directly to the printer, and instead make them
print through print server. One client acts up (say, hits consistently bug
in postscript implementation of the printer that knocks printer out; and
keeps re-sending print job every time you power cycle printer) - you will
see the world of difference. You can pinpoint what comes from which client
if all goes through print server. UNIX machine as print server will
provide you with much more than brainless embedded system printers have
inside. But for few clients, as you said, the effort is not worth it.

There is another advantage, in case it should matter:

You can have all your clients submit PS (using a generic Postscript
driver) and let the UNIX machine postprocess it into whatever format
is needed for the printer. Most normal printers speak PS, PCL and PDF
(or at least one of those), but if you're unlucky and your printer
doesn't, and maybe even worse, MICROS~1 decided your printer became
"too old" and there is no driver support anymore, this might be an
extendable solution: You got a new printer? No client-side change is
needed, just a different postprocessing filter on the server, which
is O(1) instead of O(n). ;-)

[al plant]

Post by Polytropon

Post by Valeri Galtsev

Post by Warren Block

Post by Valeri Galtsev
They didn't change anything. You can create two kind of ports (at least
two). Namely: you can create "raw" port, and give there IP address of
the
printer. This printer has to listen to "jetdirect" port (9100) for this
to
work. The other way is if printer listens to LPD ("spooler") port (port
number 515) (or better: print server, - I usually set up all printer to
only accept print jobs from print server - easier to manage especially
if
something is wrong with some client). In this case, you need to enable
two
services on Windows side (through "turning on features"): UNIX printing
related: "LPD Print Service" and "LPR Port Monitr". This teaches Windows
talk UNIX printing language, you then create local port of type LPD (and
put remote LPD server's IP there). I found this to be the most robust
way
of having Windows printing to UNIX print queues.

I've used raw port 9100 printing to HP JetDirects many times. It's nice
because it has no other dependencies.

I agree if you have one to 5 or so clients. If you have 100+ clients, you
better don't let them print directly to the printer, and instead make them
print through print server. One client acts up (say, hits consistently bug
in postscript implementation of the printer that knocks printer out; and
keeps re-sending print job every time you power cycle printer) - you will
see the world of difference. You can pinpoint what comes from which client
if all goes through print server. UNIX machine as print server will
provide you with much more than brainless embedded system printers have
inside. But for few clients, as you said, the effort is not worth it.

You can have all your clients submit PS (using a generic Postscript
driver) and let the UNIX machine postprocess it into whatever format
is needed for the printer. Most normal printers speak PS, PCL and PDF
(or at least one of those), but if you're unlucky and your printer
doesn't, and maybe even worse, MICROS~1 decided your printer became
"too old" and there is no driver support anymore, this might be an
extendable solution: You got a new printer? No client-side change is
needed, just a different postprocessing filter on the server, which
is O(1) instead of O(n). ;-)

many thanks for all the ideas put forward.

We have an old b&w hp printer on the Freebsd server and have a wireless
link to another color at least a few ways to go on this now.


~ Al Plant - Honolulu, Hawaii - Phone: [phone] ~
Supporting FreeBSD - UNIX Computer O/S
email: ***@hdk5.net email: alplant.att.net
."All that's really worth doing is what we do for others" - Lewis Carrol