A
Adam Weichel
This problem surfaced over the weekend, and it's quite
frustrating.
We have a small environment in one of our satellite
offices. 1 AD Domain Controller that also serves as a
print server, DHCP/DNS, and some file storage. There are 4
networked printers, and 10 client workstations split
between desktops and laptops. Everything is segregated
behind a SOHO router, and the server itself does NOT
handle Internet requests ala ISA.
Up to and including Friday night past(July 30th), printing
was not an issue.
Today, they get an "unable to connect" message in red in
their respective Printer menus. The printers all respond
to pings, and they all receive test pages as sent by the
server itself. Trying to re-add the printer(s) to each
client machine via Active Directory results in the
printers being displayed, but when you actually select a
printer... it errors out. There are no errors to this
effect in the System event log, nor in the Application log
of each respective machine. Nothing has changed in the
network topology at that location.
The only discrepancy was that it decided that the DC
wanted a new allocation for a NTP server, and one was made
today and the DC was rebooted on top of starting the
Windows Time service. In addition, all workstations and
laptops were rebooted, as were the printers. All printers
receive their allocated reservations in the DHCP scope as
planned.
Any thoughts would be appreciated.
Thanks in advance.
Adam Weichel, MCP
frustrating.
We have a small environment in one of our satellite
offices. 1 AD Domain Controller that also serves as a
print server, DHCP/DNS, and some file storage. There are 4
networked printers, and 10 client workstations split
between desktops and laptops. Everything is segregated
behind a SOHO router, and the server itself does NOT
handle Internet requests ala ISA.
Up to and including Friday night past(July 30th), printing
was not an issue.
Today, they get an "unable to connect" message in red in
their respective Printer menus. The printers all respond
to pings, and they all receive test pages as sent by the
server itself. Trying to re-add the printer(s) to each
client machine via Active Directory results in the
printers being displayed, but when you actually select a
printer... it errors out. There are no errors to this
effect in the System event log, nor in the Application log
of each respective machine. Nothing has changed in the
network topology at that location.
The only discrepancy was that it decided that the DC
wanted a new allocation for a NTP server, and one was made
today and the DC was rebooted on top of starting the
Windows Time service. In addition, all workstations and
laptops were rebooted, as were the printers. All printers
receive their allocated reservations in the DHCP scope as
planned.
Any thoughts would be appreciated.
Thanks in advance.
Adam Weichel, MCP