Issues with two separate networks combined to share an Office Printer.

[thecomputerguy]

Mega huge apology for the mega confusing details below!

I have a Law Office that has 4 separate Lawyers (Or Companies) that all share a large Toshiba Office Printer. The office uses Papercut to manage the costs of who uses what out of the printer.

3 of the Lawyers share a single internet connection and LAN on a 192.168.1.1 network - Well call this NETWORK A
The Toshiba printer is on NETWORK A using 192.168.1.200

1 of the Lawyers is on her own internet connection and LAN on a 192.168.15.1 network Well call this NETWORK B
The Papercut Server is on NETWORK B using 192.158.15.10

Another company came in years ago and installed a Sonicwall appliance that allowed NETWORK A (192.168.1.1) to reach over and communicate with the Papercut Server (192.168.15.10) on NETWORK B, and then allowed NETWORK B (192.168.15.1) to reach over and communicate with the Toshiba Printer on NETWORK A (192.168.1.200)

The HD in the Papercut Server completely died and was completely un-recoverable. ALL printing stopped. The printer people came out and removed the printers dependence on the Papercut Server until I was able to drop an SSD and reload W10 and bring it back out.

I brought it out and left it up to the printer people to reinstall Papercut and reconfigure the Toshiba printer etc.

The issue we have now is NETWORK A can no longer reach over into NETWORK B and communicate with the Papercut Server, however NETWORK B can reach over and print without any issue at all. NETWORK B can also communicate with the Papercut Server because they are on the same network.

The issue is NETWORK A cannot communicate with NETWORK B. Can't ping, firewall disabled etc.

We are not entirely sure what the IP was on the Papercut Server before it went down but the printer guy says it's the same IP as it was before (192.168.15.10) on NETWORK B.

We do not have login information for the Sonicwall, and I am not too familiar with Sonicwall appliances and I am afraid if I reset it I could be causing more harm than good since I will have no way to backup the settings in there. The company that installed it is no longer available so getting login info is basically impossible and the device will likely need to be reset.

UNLESS someone has some ideas about this. Sorry for the confusion description ... I just can't explain it any other way.


EDIT:
Now that I've typed it out I think I may be able to workaround... if I can get the Papercut Server onto NETWORK A since B to A works fine but A to B is being blocked ... hmmmmmm

 

[Markverhyden]

if I can get the Papercut Server onto NETWORK A since B to A works fine but A to B is being blocked ... hmmmmmm

Nickel solution to the dime problem. What Sonicwall? Maybe pitch a USG as replacement.

 

[HCHTech]

Well, best case would be to have them get the Sonicwall credentials so you can see how they have done things. If you are not familiar with business-class firewalls, you'll be in for a rude awakening as far as configuration is concerned. There are a TON of options and its not necessarily intuitive if you are used to residential routers.

BUT - you will need one to safely provide access across networks. If you can't get into the Sonicwall, you'll need to reset it to factory (which will remove all configuration), or replace it with some other firewall and configure that.

What model sonicwall is it, and how old is it? If it's a TZ 1xx or 2xx, it's ready for the bin. If it's a SOHO or SOHO 250, it's salvagable, you just need to gain control. If the licensing has expired, it will still work, but you'll need to renew those licenses so the client is protected and you have support.

PM me if you need help or have SonicOS questions. We've got 150 or so of them in the field.

 

[YeOldeStonecat]

I'd guess it's on the correct IP, as...it works for one of the networks.
Is there a managed switch in the mix? Perhaps it was plugged into a different port on the switch, so possible not a port that's a member of both VLANs that were setup?

 

[thecomputerguy]

Hmmm I haven't gone out there yet to verify the model number ... I doubt they are up to date on licensing. I know Sonicwalls are excellent products and I've worked with them when I have the credentials and can see and backup the current config but this one I'm entirely locked out of.

@YeOldeStonecat

The only thing that changed was the papercut computer server died, there was no mixing of cables or anything like that. It died and had a 5200 spinner in it on W7 so I replaced it with a SSD and loaded 10 and reinstalled it so the printer people could install papercut. We all believe the IP to be the same but the crossover isn't working in one direction.

I suppose I could start with a reboot of the Sonicwall. Like I said I haven't been out there yet and I was just looking for ideas.

 

[Sky-Knight]

This is why I use Untangle...

If even ONE of those networks had an Untangle at the edge, all you'd have to do is connect an interface on it to the 2nd network, address it static on that network, and slap a static route in that network's other router for the IP range on the far side of Untangle.

A few firewall rules to limit access to the printer's IP address, and everyone can print. You could even go the extra step of defining a DMZ network, stuff the printer in it all by it's lonesome and utterly isolate both law firms from each other. All while TCPDump and all the logs you could ever want to see what's going on are clicks away from even untrained eyes to troubleshoot.

But you need a real router for that, the Sonicwall can do all of this too... but it sounds like something has gone horribly wrong with it. Also, if it's not on the internet at all... then you'd need routes in both of the other gateways...

So how many routers are we talking about here? 2? 3?

Network A: 192.168.1.0/24?
Network B: 192.168.15.0/24?

.1s are the gateways for the internet? Which one is the Sonicwall?