FVS336G Printer Sharing

First - the FVS336G has no impact on the sharing of resources across the LAN, however, whether or not the FVS336G plays a role in the problem will depend on how the printer is being shared.

You say the "host computer" can print OK - which suggests that the printer is connected to a computer, rather that being directly attached to the network or via a print server - if this is correct, focus on that computer, and it's firewall settings.

Second - you say the printer worked fine before the FVS33G was added - ho/why was the FVS336G "added"? If it replaced an existing router it should not cause any problems, apart from a possible change in the ip range being used, however, if it was "added" to the network, so that there are now two routers, that could be a problem.

Thanks for getting back to me.

Apologies if that wasn't very clear.

Yes, the printer is locally connected via USB to the host computer, and the other computer is trying to connect to it as a shared printer through our network.

Previously our BT2700 modem/router was acting as the router on the network. Right now it's on the 10.x.x.x IP range and the FVS336G is acting as the router and DHCP server. By adding it to the network, I meant that previously it wasn't there, now it is there.

However, the printer sharing issue seems to have been resolved, and I'm not entirely sure why. It could be down to any of the following:

1. Yesterday we noticed that the host computer had the LAN network type as 'Public' rather than 'Work'. We changed that, but it still didn't work. We also tried completely disabling the Firewall on both computers to see if that worked, but no change. Hence me assuming that perhaps it was the FVS336G firewall.

2. Today I changed the name of the shared printer from "Citizen CL-S521" to "Citizen". As a network printer it was seen as "Citizen_CL-S521", so perhaps something to do with the underscore or hyphen was affecting it - no idea.

It's now working today as "Citizen" and I'm not entirely sure what has changed overnight other than the printer name. Sorry this isn't more helpful to other people experiencing the same issue, but it appears to be working and I'm hesitant to change anything to debug it further.