|
Hi Patrik,
Yes, I am positive. We have the windows printserver ip address in the
/qntc directory on the IBMi and if you drill down, you can see the folders
that are being shared from the windows printserver on the AS400.
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Patrik Schindler
Sent: Friday, May 24, 2024 6:47 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Create a new Windows print server
External eMail: Do not open attachments or click on links unless you
expected to receive them from a trusted sender.
Hello Reggie,
Am 24.05.2024 um 15:20 schrieb Reggie Monroe via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx>:
We currently have an AS400 that has a windows print server configured onit.
We have been sending reports from the AS400 to this windows print serverfor many years. This was setup by someone that no longer works with us. We
would like to add an additional print server on the AS400 to send reports
to another print server. The only thing we know in order to add another
print server is to add the IP address in the /qntc directory. We are not
sure of what other steps are needed to make it work.
Are you sure that we're talking about the IBM i side of affairs?
First, /qntc is the *client* side for Windows file sharing. This is, when
you want to access file shares on Windows servers (or compatible ones, such
as Samba on Linux).
Second, I'm not aware that NetServer (the server part of making an IBM i
machine appear to Windows as a Windows file server) has printing support.
But then, I'm not a Windows guy, and my knowledge is based on a very dated
version of OS/400.
:wq! PoC
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit:
https://urldefense.com/v3/__https://lists.midrange.com/mailman/listinfo/midrange-l__;!!Fat92My4sJ5u0kQe!1f681iF8qDqGvXTFfkCzq88ZuCE4hd-dDClHNovX8vOrCAFUtxQfwsfWsvYX4GY8rgzauBc_66UL8Ckw$
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://urldefense.com/v3/__https://archive.midrange.com/midrange-l__;!!Fat92My4sJ5u0kQe!1f681iF8qDqGvXTFfkCzq88ZuCE4hd-dDClHNovX8vOrCAFUtxQfwsfWsvYX4GY8rgzauBc_6-ctyKGx$
.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
________________________________
This e-mail message, including any attachments, is for the sole use of
the intended recipient, and may contain material that is privileged or
confidential and legally protected from disclosure. If you are not the
intended recipient or have received this message in error, you are not
authorized to copy, distribute, or otherwise use this message or its
attachments. Please notify the sender immediately by return e-mail and
permanently delete this message and any attachments.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.