How can I achieve this with my current setup?
-
Damn, the network is all set up and in production LOL
Funny thing is only the printer is not working haha
I'll have to wait till the machines are inactive to change the settings.
-
That also explains why after changing my LAN, I couldn't access WebGUI lol
-
Better to find out now when it's just the printer not remotely accessible than tearing your hair out later trying to solve some client specific issue. ;)
Interesting that pfSense allowed you to use that address.Steve
-
The printer thing and interface are easy fixes. Sounds like you have a network now.
-
I'm splitting hair now. DHCP, Gateway and DNS have automatically assigned 10.0.0.1, yet I cannot access its web interface outside LAN network.
-
Why should you be able to access it unless you are inside your LAN? Thats the way its supposed to be unless you VPN into it or open ports.
I also really don't think that 10.0.0.1 or some really simple addresses are the best way to assign your subnets. The whole point of not giving it a 192.168.1.1 is to get away from a common and likely possible conflict. Moving to another simple address like 10.10.10.10 or 10.0.0.1 doesn't help much. Some, but not much. -
I was able to before, besides the printer can't ping anything yet, also times out contacting NTP server.
-
How many WAN IPs do you have now?
-
The setup I'm doing, only one (xxx.xxx.xxx.98(WAN) - xxx.xxx.xxx.126 /27).
-
Why don't you try assigning a static map to that printer. Put it where you want it to be. Then make sure there are no firewalls in the way, make sure you forward the correct ports and protocols if you need any forwards.
I know very very little about your printer except its got a odd IP and doesn't work. Also, how are you trying to print to it? What protocols? Is this windows or samba or something?
-
The printer gets automatically 10.0.0.99 because I assigned it in the DHCP mappings (10.0.0.100 - 10.0.0.120 for the computers, easier for me to remember :P).
It's a Ricoh MPC2050, every computer in LAN can print through PCL5 and PCL6 and access the web interface. I want to print and access its web interface from another computer over the Internet (I was able to before this setup).
It scans and saves through SAMBA, but there's a known bug with the printer since it's using SAMBA1 and I have to do some workaround about it with Windows 7 by disabling Samba2, which I have not done yet, but it's unrelated to my current issue.
I'm going to try to assign staticly from the printer itself and report back. Thanks.
-
I got tired of broadcast dependent printers some time ago. I've converted all my stuff to internet printing protocol. Very simple. Just point to the port and fire. No worrying about windows network crap or samba this and that.
Personally, I'm glad your printer isn't visible to the public internet. Thats just not smart.
I think what you are experiencing is a safety feature… ;D
-
Damn, I'd be mad >:(
Any way to confirm or override?
-
Confirm or over ride what?
-
The safety feature.
-
Whilst having a publicly addressable printer is perhaps… unwise, it should work.
If you are doing 1:1 NAT, and have it setup exactly as the other LAN clients which are working, I can't see why it wouldn't work. Even if it had some code to prevent it using a public IP (which seems very unlikely) it doesn't know because it's behind NAT.
The fact that it can't ping out seems like a clue, NAT not working correctly perhaps. Can it ping the pfSense VM? When it fails to ping is there any error message?Steve
-
With my samba server stuff, it always needs to know it subnet and workgroup in the samba config. That and telling it to accept anonymous clients etc.
Check your setup to see if its set up thinking it should be looking at this or that subnet that has changed. -
Take a break guys, I'm at home, will report tomorrow. Have a good night.
-
Let the fun begins. ;D
Printer can ping pfSense's public IP (xxx.xxx.xxx.98) and can ping any LAN clients (10.0.0.100 - 10.0.0.120)
Again, printer can't ping anything outside LAN. (Err: Ping has failed)It gets subnet automatically (255.255.255.0), has SAMBA Workname and Name set up. But printer only uses SAMBA for saving scans.
-
I frankly cannot see why printer should ping anything, in or outside LAN. Maybe you should make clear what is the issue here.
