📎 AI Summary:
The thread discusses a network printing issue affecting wireless users after a recent security update, which disrupted communication with the print server on a mixed wired and wireless network. Troubleshooting included rebooting various network devices, but the problem persisted, and additional issues like IP conflicts with VoIP phones arose. The conversation highlights ongoing challenges in diagnosing network connectivity problems post-update, with suggestions to review device restart sequences and potential DHCP conflicts.
T

TierOneTech

New Member
Joined
Jul 27, 2015
Messages
2
Thread Author #1
I operate a blended network, wired and wireless, on different IP ranges, wired on a 192 and wireless on a 172 range.

Printers are on the wired network.

Last week, wireless users could print to the network printers. Monday they could. After the latest update, all of my wireless users can't print. I can't get a printer to install. All printer functions are controlled by a print server on the wired network.

Now, after the update for the Adobe font vulnerability, all of my wireless clients are unable to print.

I have checked basic settings and firewall settings. The print server is identified on all units by IP. I can ping from wireless to wired IP, no problems. However, there is no other communication. The print server logs show nothing but wired connections and jobs.
 

Solution
bochane
Reboot should be performed in a specific order. First every thing down, than modem on, router on, than servers on, so that every item that is started sees a functioning network with valid parameters.
I suspect there is a second DHCP server active that causes havoc.

Henk
Sort by date Sort by votes
bochane

bochane

Essential Member
Joined
Oct 18, 2012
Messages
1,403
#2
Just for my information, have your routers been reset? If not you should try it.

Henk
 

Upvote 0 Downvote
T

TierOneTech

New Member
Joined
Jul 27, 2015
Messages
2
Thread Author #3
Thank you Henk. Rebooted firewall/router, AP controller, computer with print server, switches. Still no luck plus now half of their Avaya phones are getting IP's out of range. Very weird! Rebooted that controller too but no change.
 

Upvote 0 Downvote
bochane

bochane

Essential Member
Joined
Oct 18, 2012
Messages
1,403
#4
Reboot should be performed in a specific order. First every thing down, than modem on, router on, than servers on, so that every item that is started sees a functioning network with valid parameters.
I suspect there is a second DHCP server active that causes havoc.

Henk
 

Upvote 1 Downvote
Solution
You must log in or register to reply here.