Networked Printers

I have 2 2k3 print servers. The two servers are in two
different locations, not even in the same town, but there
are people in the 2nd location that need to print to
them. My logic is if they queue on the 2nd server if the
connection is lost they will stay in the queue until
reconnected. Users also wouldn't have to be connected to
both servers, just to their primary server.

Is there a way to setup the printers on the 2nd server to
print to the queue on the 1st server?

If the printers have NICs and an IP# then they can be setup and shared from
the server that is closest to the users in question. It is also possible to
have the users print directly to the printer via its IP# and not go through
a "sharing server" at all.


--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


"Tim" <(E-Mail Removed)> wrote in message
news:1c72101c42238$c17cefc0$(E-Mail Removed)...
> I have 2 2k3 print servers. The two servers are in two
> different locations, not even in the same town, but there
> are people in the 2nd location that need to print to
> them. My logic is if they queue on the 2nd server if the
> connection is lost they will stay in the queue until
> reconnected. Users also wouldn't have to be connected to
> both servers, just to their primary server.
>
> Is there a way to setup the printers on the 2nd server to
> print to the queue on the 1st server?

Thanks for replying, but here's the deal...

All 900+ main site printers are on JetDirects with host
name & IP assigned through DHCP reservations and setup on
the 2k3 main site cluster. Remote sites (63 of them)
have their own servers, but some people need to print to
printers at the main site. Direct IP would work, but
completely invalidates the whole purpose of a print
server, not to mention with over 5000 workstations could
easily turn into a nightmare. Logically, if the remote
server print queues could forward to the main site queues
monitoring and managing this number of printers would be
much easier.

TD


>-----Original Message-----
>If the printers have NICs and an IP# then they can be
setup and shared from
>the server that is closest to the users in question. It
is also possible to
>have the users print directly to the printer via its IP#
and not go through
>a "sharing server" at all.
>
>
>--
>
>Phillip Windell [MCP, MVP, CCNA]
>www.wandtv.com
>
>
>"Tim" <(E-Mail Removed)> wrote in message
>news:1c72101c42238$c17cefc0$(E-Mail Removed)...
>> I have 2 2k3 print servers. The two servers are in two
>> different locations, not even in the same town, but
there
>> are people in the 2nd location that need to print to
>> them. My logic is if they queue on the 2nd server if
the
>> connection is lost they will stay in the queue until
>> reconnected. Users also wouldn't have to be connected
to
>> both servers, just to their primary server.
>>
>> Is there a way to setup the printers on the 2nd server
to
>> print to the queue on the 1st server?
>
>
>.
>

Yes printing direct would not be good to deal with when there is that many
machines. I don't think there is any such thing as "forwarding to another
print queue". The server that is local to the users would have to be setup
with the printers that they want to use (same way the main site servers are)
and then that server would share them to the users. Otherwise you are going
to have the ask the questions, "Is it all worth it? Do they really *need* to
print to those remote servers or do they just *want* to? Is there a
completely better way that hasn't been considered?"

Think of all the things users can/will do wrong when they can't walk over to
the printer to see that it really happen. If they think it didn't print
(when it did) and they do it again, .....and then again. What if they have a
50 page document and tell the printer they want 2 copies and they
accidentally hit an extra 0 and send 20 copies at 50 pages each (it happened
here). And you have all this happeing on a slower WAN link.....not a faster
10/100 LAN link.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


<(E-Mail Removed)> wrote in message
news:1cd2301c42245$4c18d480$(E-Mail Removed)...
> Thanks for replying, but here's the deal...
>
> All 900+ main site printers are on JetDirects with host
> name & IP assigned through DHCP reservations and setup on
> the 2k3 main site cluster. Remote sites (63 of them)
> have their own servers, but some people need to print to
> printers at the main site. Direct IP would work, but
> completely invalidates the whole purpose of a print
> server, not to mention with over 5000 workstations could
> easily turn into a nightmare. Logically, if the remote
> server print queues could forward to the main site queues
> monitoring and managing this number of printers would be
> much easier.
>
> TD
>
>
> >-----Original Message-----
> >If the printers have NICs and an IP# then they can be
> setup and shared from
> >the server that is closest to the users in question. It
> is also possible to
> >have the users print directly to the printer via its IP#
> and not go through
> >a "sharing server" at all.
> >
> >
> >--
> >
> >Phillip Windell [MCP, MVP, CCNA]
> >www.wandtv.com
> >
> >
> >"Tim" <(E-Mail Removed)> wrote in message
> >news:1c72101c42238$c17cefc0$(E-Mail Removed)...
> >> I have 2 2k3 print servers. The two servers are in two
> >> different locations, not even in the same town, but
> there
> >> are people in the 2nd location that need to print to
> >> them. My logic is if they queue on the 2nd server if
> the
> >> connection is lost they will stay in the queue until
> >> reconnected. Users also wouldn't have to be connected
> to
> >> both servers, just to their primary server.
> >>
> >> Is there a way to setup the printers on the 2nd server
> to
> >> print to the queue on the 1st server?
> >
> >
> >.
> >

Need is a definate yes for records and reports. The
powers that be think it's worth it, I'm just stuck with
making it work. Fortunately, the main site is done and
I'm able to work with one remote site to test and debug,
then whatever works will be implemented enterprise wide...

>-----Original Message-----
>Yes printing direct would not be good to deal with when
there is that many
>machines. I don't think there is any such thing
as "forwarding to another
>print queue". The server that is local to the users
would have to be setup
>with the printers that they want to use (same way the
main site servers are)
>and then that server would share them to the users.
Otherwise you are going
>to have the ask the questions, "Is it all worth it? Do
they really *need* to
>print to those remote servers or do they just *want* to?
Is there a
>completely better way that hasn't been considered?"
>
>Think of all the things users can/will do wrong when
they can't walk over to
>the printer to see that it really happen. If they think
it didn't print
>(when it did) and they do it again, .....and then again.
What if they have a
>50 page document and tell the printer they want 2 copies
and they
>accidentally hit an extra 0 and send 20 copies at 50
pages each (it happened
>here). And you have all this happeing on a slower WAN
link.....not a faster
>10/100 LAN link.
>
>--
>
>Phillip Windell [MCP, MVP, CCNA]
>www.wandtv.com
>
>
><(E-Mail Removed)> wrote in message
>news:1cd2301c42245$4c18d480$(E-Mail Removed)...
>> Thanks for replying, but here's the deal...
>>
>> All 900+ main site printers are on JetDirects with host
>> name & IP assigned through DHCP reservations and setup
on
>> the 2k3 main site cluster. Remote sites (63 of them)
>> have their own servers, but some people need to print
to
>> printers at the main site. Direct IP would work, but
>> completely invalidates the whole purpose of a print
>> server, not to mention with over 5000 workstations
could
>> easily turn into a nightmare. Logically, if the remote
>> server print queues could forward to the main site
queues
>> monitoring and managing this number of printers would
be
>> much easier.
>>
>> TD
>>
>>
>> >-----Original Message-----
>> >If the printers have NICs and an IP# then they can be
>> setup and shared from
>> >the server that is closest to the users in question.
It
>> is also possible to
>> >have the users print directly to the printer via its
IP#
>> and not go through
>> >a "sharing server" at all.
>> >
>> >
>> >--
>> >
>> >Phillip Windell [MCP, MVP, CCNA]
>> >www.wandtv.com
>> >
>> >
>> >"Tim" <(E-Mail Removed)> wrote in message
>> >news:1c72101c42238$c17cefc0$(E-Mail Removed)...
>> >> I have 2 2k3 print servers. The two servers are in
two
>> >> different locations, not even in the same town, but
>> there
>> >> are people in the 2nd location that need to print to
>> >> them. My logic is if they queue on the 2nd server if
>> the
>> >> connection is lost they will stay in the queue until
>> >> reconnected. Users also wouldn't have to be
connected
>> to
>> >> both servers, just to their primary server.
>> >>
>> >> Is there a way to setup the printers on the 2nd
server
>> to
>> >> print to the queue on the 1st server?
>> >
>> >
>> >.
>> >
>
>
>.
>

Well, like I said,...the server that is local to the users would have to be
setup
with the printers that they want to use (same way the main site servers are)
and then that server would share them to the users.


--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


"Tim" <(E-Mail Removed)> wrote in message
news:180bc01c4224d$51b5c670$(E-Mail Removed)...
> Need is a definate yes for records and reports. The
> powers that be think it's worth it, I'm just stuck with
> making it work. Fortunately, the main site is done and
> I'm able to work with one remote site to test and debug,
> then whatever works will be implemented enterprise wide...
>
> >-----Original Message-----
> >Yes printing direct would not be good to deal with when
> there is that many
> >machines. I don't think there is any such thing
> as "forwarding to another
> >print queue". The server that is local to the users
> would have to be setup
> >with the printers that they want to use (same way the
> main site servers are)
> >and then that server would share them to the users.
> Otherwise you are going
> >to have the ask the questions, "Is it all worth it? Do
> they really *need* to
> >print to those remote servers or do they just *want* to?
> Is there a
> >completely better way that hasn't been considered?"
> >
> >Think of all the things users can/will do wrong when
> they can't walk over to
> >the printer to see that it really happen. If they think
> it didn't print
> >(when it did) and they do it again, .....and then again.
> What if they have a
> >50 page document and tell the printer they want 2 copies
> and they
> >accidentally hit an extra 0 and send 20 copies at 50
> pages each (it happened
> >here). And you have all this happeing on a slower WAN
> link.....not a faster
> >10/100 LAN link.
> >
> >--
> >
> >Phillip Windell [MCP, MVP, CCNA]
> >www.wandtv.com
> >
> >
> ><(E-Mail Removed)> wrote in message
> >news:1cd2301c42245$4c18d480$(E-Mail Removed)...
> >> Thanks for replying, but here's the deal...
> >>
> >> All 900+ main site printers are on JetDirects with host
> >> name & IP assigned through DHCP reservations and setup
> on
> >> the 2k3 main site cluster. Remote sites (63 of them)
> >> have their own servers, but some people need to print
> to
> >> printers at the main site. Direct IP would work, but
> >> completely invalidates the whole purpose of a print
> >> server, not to mention with over 5000 workstations
> could
> >> easily turn into a nightmare. Logically, if the remote
> >> server print queues could forward to the main site
> queues
> >> monitoring and managing this number of printers would
> be
> >> much easier.
> >>
> >> TD
> >>
> >>
> >> >-----Original Message-----
> >> >If the printers have NICs and an IP# then they can be
> >> setup and shared from
> >> >the server that is closest to the users in question.
> It
> >> is also possible to
> >> >have the users print directly to the printer via its
> IP#
> >> and not go through
> >> >a "sharing server" at all.
> >> >
> >> >
> >> >--
> >> >
> >> >Phillip Windell [MCP, MVP, CCNA]
> >> >www.wandtv.com
> >> >
> >> >
> >> >"Tim" <(E-Mail Removed)> wrote in message
> >> >news:1c72101c42238$c17cefc0$(E-Mail Removed)...
> >> >> I have 2 2k3 print servers. The two servers are in
> two
> >> >> different locations, not even in the same town, but
> >> there
> >> >> are people in the 2nd location that need to print to
> >> >> them. My logic is if they queue on the 2nd server if
> >> the
> >> >> connection is lost they will stay in the queue until
> >> >> reconnected. Users also wouldn't have to be
> connected
> >> to
> >> >> both servers, just to their primary server.
> >> >>
> >> >> Is there a way to setup the printers on the 2nd
> server
> >> to
> >> >> print to the queue on the 1st server?
> >> >
> >> >
> >> >.
> >> >
> >
> >
> >.
> >