On Apr 29, 3:53 pm, Jake <jak...@gmail.com> wrote:
> Hi,
>
> We put a second NIC with IP 192.168.3.10 in our w2003 domain controller.
> The first nic was at 192.168.1.10 where the dc also shared a printer
> with IP 192.168.0.20.
>
> Naturally workstations on the second NIC's 192.168.3.0 subnet won't be
> able to use the printer connected to the first nic.
>
> What do we need to do to enable or route printing from the 192.168.3.0
> workstations to the printer?
>
> Thanks a lot for comments and solutions to this.
>
Let me see if I understand ...
subnet ZERO: 192.168.0.0 mask 255.255.255.0
subnet ONE: 192.168.1.0 mask 255.255.255.0
subnet THREE: 192.168.3.0 mask 255.255.255.0
\\DOMAINDC: domain controller, dual homed on 192.168.1.10 / ONE
and 192.168.3.10 / THREE
printer: 192.168.0.20 / ZERO
I don't see how machines (including your DC) on subnet ONE are seeing
the printer on subnet ZERO anyway. Perhaps this was a typo, and your
printer is at 192.168.1.20 / ONE.
But if there is already a working share on \\DOMAINDC\ThePrinter, then
machines that can reach \\DOMAINDC on either subnet should have no
problem queuing print jobs to \\DOMAINDC\ThePrinter.
If there is not such a working share yet, then make one, and that
solves your problem.
Your other choice is to set up Routing and Remote Access on \
\DOMAINDC, which will let it transparently route packets from one
subnet to the other. But maintaining that is potentially a much larger
task.
|
Similar Threads
