CUPS printer sharing across subnets?

I am trying to set up my local network printer so that everyone in the house can print from it. However I have two subnets in the house and I don't see how to connect to the Linux server through a Windows 7 client.
My network is like so:
Upstairs: [Modem] <=eth0=> [Router 1] Subnet of 192.168.0.*
[Router 1] <=wlan0 client mode=> Downstairs: [Router 2 with dd-wrt firmware] Subnet of 192.168.1.*
[Router 2] <=eth0=> CUPS server/PC with USB printer attached IP address of 192.168.1.1XX
This works: [Router 2] <=ath0.1 virtual wireless ESSID=> Windows 7 Laptop
This doesn't: [Router 1] <=wlan0=> Windows 7 Laptop
I tried
sudo cupsctl --share-printers --remote-any && sudo systemctl restart cups
on the host PC, but the W7 clients can't connect across subnets. Is there anyway to set it up so it can? They can easily connect to the ath0.1 network and then print, but it's inconvenient for them. The Windows users spend most of the time upstairs, and not downstairs, so they are usually connected to the wlan0 network.
I have the option of putting [Router 2] into client bridged mode so it shares the same subnet of [Router 1], however I can't seem to set it up properly and I run into problems. It is important to have the ath0.1 network downstairs, and I am unsure that client (bridged) mode will allow for the virtual interface.
I do not have Samba installed but I am considering trying that, but a simpler solution would be appreciated.
*Edited for further clarification & error fixing.
Last edited by felixculpa (2012-12-27 20:03:51)

DiverDoc wrote:
if I can share a printer between an XP system and a Win 7 system?
Before I enter all the system data, I just wondered if someone already knew the answer to this one. I was successsfully sharing a non network printer plugged into an XP machine via USB and printing to it via Network Magic from my Vista machine, but since I upgraded Vista to Win 7, I cannot. Everytime I try to install the remote printer or access it in any way from my Win 7 machine, I get the Windows message: " Windows cannot connect to the printer". This also occurs form within the Network Magic Map if I try to Complete Printer Setup. It shows up on my Win 7 machine when I want to ADD a Printer, but I cannot install it. It shows as Shared on the XP machine.
Thanks for any assistance!
S.
Hi S.,
You need to use Network and Sharing Center and open up your computer. You need to use the Public Profile and turn on Network Discovery. Not sitting in front of Windows 7 at the moment.
Otherwise, you need a Wireless Printer or All-In One Machine or a Printer that plugs into the Router using an Ethernet Port.
thecreator - Running Network Magic version -5.5..9195.0-Pure0 on Windows XP Home Edition SP 3
Running Network Magic version -5.5.9195.0-Pure0 on Wireless Computer with McAfee Personal Firewall Build 11.5.131 Wireless Computer has D-Link DWA-552 connecting to D-Link DIR-655 A3 Router.

Similar Messages

Connect mac client to mac printer share across subnets

I need to share printers from a Mac. I need to connect
Mac clients on different subnets to the Mac shared printers. I installed
a Mac mini, connected to printers via HP JetDirect Socket (port 9100), and
shared them. I was able to print from the Mac mini, and connect Mac
clients on the same subnet to the shared printers with Bonjour and print.
I moved the Mac mini to its intended location on another subnet. I
immediately learned that Bonjour does not publish services across
subnets. I could not find documentation on how to connect to a Mac shared
printer across subnets, but I did find some third party documentation (only some incomplete
documentation from Apple) on how to implement DNS-SD Service Discovery. I
enabled DNS-SD and was able to publish the printer shares across subnets, but I
was still unable to connect to the printer shares from a Mac client. I
found some third party documentation (none from Apple) on how to manually connect to a Mac
printer share by specifying the IP address of the server, specifying the CUPS
default IPP protocol, and the print queue name. I was unable to connect
to the shared printers. I receive ping replies from my Mac mini, and port
scan reveals that port 631 for IPP, CUPS default, is open. Printer
sharing is configured so everyone can print. I am able to connect to the Mac
mini with VNC Screen Sharing. I don’t see how this can be a network
issue.
Macs don’t seem to like to connect to our Windows
shared printers because of our PaperCut software, and connecting Mac clients to
Windows printer shares and authentication is beyond the average user,
exacerbated by Macs not behaving the same as Windows when bound to an Active
Directory domain.
I called Apple support, they escalated to Apple Enterprise
support. Apple Enterprise support said they couldn’t help me beyond a
single network with no subnets, but Apple Engineering might be able to solve
the problem for $695.
Why do I need to pay $695 to learn how to connect Mac
clients to Mac shared printers, something that should be easy and intuitive and
have documentation readily available? Windows printer sharing is easy and
intuitive and documentation is readily available, and services are published
across subnets without have to implement DNS-SD.

Thank you for your reply. I followed the instructions in the sybaspot.com site and in some of the included references to set up DNS-SD. DNS-SD worked, but I couldn't connect the Mac client to the Mac shared printers.
I also found http://www.papercut.com/products/ng/manual/ch-mac-printing-10-8-9.html#ch-mac-pr inting-10-8-9-sharing-printers.
I expanded my search and found this: http://support.apple.com/kb/PH13940, last modified May 8, 2014. I started work on my project February 2014. Apple Support could have told me about this document.
PH13940 says: "The computers must be on the same local network as your Mac". Apple must not consider multiple subnets one network.
PH13940 says: "Printer sharing is for printers attached directly to your Mac. You don’t need to share network printers, because they are already shared on the network."
Apple must define "network printers" as any printer with a network interface. Microsoft defines network printers as printers shared by another computer. TCP/IP ports are local ports on a Windows computer, so TCP/IP connected printers are local printers that can be shared. Multiple users on a Mac all see the same connected printers. Multiple users on Windows all see the same local printers, but network printer connections can be different for each user.
Apple must not see any value in accounting for printing and assigning the cost to the user or department. We need to account for printing and cannot have any users bypassing the system by printing directly to printers. I have created Access Control lists on the printers to limit connections to the specific IP addresses of our print servers.
The documents about setting up DNS-SD and IPP connections must have assumed USB connected printers on a Mac. The odd thing is that I was able to share a network printer from the Mac mini when the client Mac was on the same subnet. Is PH13940 wrong?
I am Microsoft Certified Systems Engineer 1999 and Apple Certified Technical Coordinator 2013.

Printer sharing across internet sharing

I hope I don't confuse everyone with this.
I have three computers—an iMac running Snow Leopard, an iMac running Lion, and a Mini running Leopard. The SL iMac has a printer plugged into it. The other two computers are across the house from it.
Those two computers are next to each other. The Lion iMac is connected to the Internet via WiFi. The Mini, which does not have wireless, is connected to the Internet via Internet Sharing over an ethernet cable to the Lion iMac.
Now here's the problem. I can print from the Lion iMac through printer sharing across to the SL iMac. However, I can't figure out how to print from the Mini. It won't find the SL iMac's printer. Enabling printer sharing on the Lion iMac lets the Mini see it as a 'printer,' but it won't print across to the SL iMac.
So with this setup, is it possible to print to the SL iMac from the wireless-less Mini?
Just to ward off possible non-workable solutions, rearranging the computers is not feasable right now. It is also not possible to connect the Mini directly to the internet via ethernet. My cable modem is actually in a near-inaccessable part of the house due to that being where the only cable plug is. I have a Time Capsule attached to it, which broadcasts my wireless signal that the WiFi computers can pick up. And no, I can't connect the printer to the Time Capsule—believe me, I tried. I don't want to have to start buying long cables and drilling holes if there's a simpler solution.
Thanks in advance.

If I switch to the discussed set up (Airport Extreme N router), will adding an AX in between at 15 feet help bridge the link between the G5's Airport extreme card and the living room's AX?
Yes. But I still think you should verify if Wi-Fi interference is the cause of your poor signal only 30' away from the AX before going out and purchase anything. Remember, you will tradeoff bandwidth performance for signal strength. With audio, this can be a negative factor.
If you can get a hold of a laptop, I suggest downloading a copy of iStumbler. Use iStumbler's Inspector feature (select Edit > Inspector from iStumbler's menu) to determine the Signal-to-Noise Ratio (SNR) at different points around your house, by performing a simple RF site survey. Within the Inspector, note the values for "signal" & "noise" at these locations. Start with the laptop near the AX, note the readings, and then, choose the locations between the AX and, finally, where you have the G5.
SNR is the signal level (in dBm) minus the noise level (in dBm). For example, a signal level of -53dBm measured near an access point and typical noise level of -90dBm yields a SNR of 37dB, a healthy value for wireless LANs.
The SNR, as measured from the laptop, decreases as the range to the base station increases because of applicable free space loss. Also an increase in RF interference from microwave ovens and cordless phones, which increases the noise level, also decreases SNR.
SNR Guideline
o 40dB+ SNR = Excellent signal
o 25dB to 40dB SNR = Very good signal
o 15dB to 25dB SNR = Low signal
o 10dB to 15dB SNR = Very low signal
o 5dB to 10dB SNR = No signal
If the SNR is 20dB+ at each of these locations, then you should be getting reasonable performance from your AirPort. If less, either try to locate the source of the Wi-Fi interference or try relocating the base station or the G5 until they are within a 20dB SNR range.

Printer Sharing across platforms - can someone tell me ...

if I can share a printer between an XP system and a Win 7 system?
Before I enter all the system data, I just wondered if someone already knew the answer to this one. I was successsfully sharing a non network printer plugged into an XP machine via USB and printing to it via Network Magic from my Vista machine, but since I upgraded Vista to Win 7, I cannot. Everytime I try to install the remote printer or access it in any way from my Win 7 machine, I get the Windows message: " Windows cannot connect to the printer". This also occurs form within the Network Magic Map if I try to Complete Printer Setup. It shows up on my Win 7 machine when I want to ADD a Printer, but I cannot install it. It shows as Shared on the XP machine.
Thanks for any assistance!
S.

DiverDoc wrote:
if I can share a printer between an XP system and a Win 7 system?
Before I enter all the system data, I just wondered if someone already knew the answer to this one. I was successsfully sharing a non network printer plugged into an XP machine via USB and printing to it via Network Magic from my Vista machine, but since I upgraded Vista to Win 7, I cannot. Everytime I try to install the remote printer or access it in any way from my Win 7 machine, I get the Windows message: " Windows cannot connect to the printer". This also occurs form within the Network Magic Map if I try to Complete Printer Setup. It shows up on my Win 7 machine when I want to ADD a Printer, but I cannot install it. It shows as Shared on the XP machine.
Thanks for any assistance!
S.
Hi S.,
You need to use Network and Sharing Center and open up your computer. You need to use the Public Profile and turn on Network Discovery. Not sitting in front of Windows 7 at the moment.
Otherwise, you need a Wireless Printer or All-In One Machine or a Printer that plugs into the Router using an Ethernet Port.
thecreator - Running Network Magic version -5.5..9195.0-Pure0 on Windows XP Home Edition SP 3
Running Network Magic version -5.5.9195.0-Pure0 on Wireless Computer with McAfee Personal Firewall Build 11.5.131 Wireless Computer has D-Link DWA-552 connecting to D-Link DIR-655 A3 Router.

Sharing across Subnets

Hi there,
I work for a company where we have a wired lan and a wireless lan.
The wired lan is 192.168.97.* and the wireless is 192.168.98.*
When connected to the wired LAN, we are able to see all shared machine who are also on the .97 subnet.
When connected to the wireless LAN, we are able to see all shared machines who are on the .98 subnet.
When on the wireless, we are able to ping all .97 addresses on the wired LAN no problem.
However, I need the .97 shared machines to show up under 'shared' within finder when users are connected to the .98 network (wireless)
Can anyone point me in the right direction as to how I can do this ?

Buy more expensive routers :-)
If you are using consumer routers, you are limited in what you can do.
The easy thing would be to stop using the 192.168.98.* subnet, tell the WiFi router to become a "Bridge" and share the 192.168.97.* subnet. Depending on the router, this is done by an explicit "Bridge" mode setting (Apple Airport Extreme), or in some cases it is disabling DHCP server on the router, or some routers require you to disable DHCP and NAT servers. But once you do that, it disables routing and turns the device into a "Bridge" that shares the ethernet subnet with WiFi devices.
Of course if your company is so big that you have more than 200'ish devices including routers, networked printers, mobile devices, computers, etc.... just using a single subnet driven by a consumer router may be an issue.
Also if you have that many devices a consumer router may have issues moving all that data.
There are consumer routers that allow you to replace the firmware with an open source router firmware that would give you more flexibility in configuring your subnet, such as changing the router's subnet mask from 255.255.255.0 to something that allows more devices, such as 255.255.0.0, but again, now your router needs to have the horse power to handle all the devices.

Windows file sharing across subnets

I have a SonicWall TZ170 wireless router that will not allow the LAN and WLAN to have the same subnet IP address. I have a WinXP Pro desktop on the LAN at 192.168.70.100 and a PowerBook on the WLAN at 192.168.71.100. The router firewall is set up to allow all traffic (any IP address) between the two subnets. However, no matter what i do, I cannot get the PowerBook to connect to the PC. (I've also tried SMB://192.168.70.100/share, where "share" is the name of the shared folder on the PC.) I know the file sharing settings are correct, since I can mount the PC share when the PowerBook is connected to the LAN.
I've since read that SMB does not work over different subnets. Is this correct? If so, is there any other way to share files on the PC with the PowerBook?
PowerBook G4 15 Mac OS X (10.4.8)

Ideas?
I'm downloading the manuals, to see if I can glean any clues from there as far as configuring the firewall rules in the device.
I suggest that you do the same.
http://www.sonicwall.com/us/support/3134.html
There are several product guides and how-to PDF's...
The other idea that might work would be to follow their suggestion: "Specifics at this point are probably best dealt with in the form of a call to our technical support team."
this is looking less like a mac issue and more like a SonicWall issue.

Print Sharing across a wireless network.

Hello fellow Macsters,
I am trying to share my HP printer across my wireless network. here is my network setup. I have a wireless network throughout my house. an iMac 20'' desklamp without an airport card is connected to a belkin router via an ethernet cord. That router creates my wireless network, allowing my iBook G4 to conenct to it wirelessly. The wireless signal is continued by an AX in WDS bridge mode, on the second floor of my house. Currently, I can share the printer connected to the iMac, but only when the iMac is on. I would like to be able to share it without leaving the computer on. I know there are multiple ways to do it, but do not know the specifics of them. Could somebody please tell me what they are. Thank you very much.

Well if its a non network HP printer it will have to be a AEBS. HP dosent make network operable drivers for thier non-network ready printers s and thos eprinters tend to only be PCL and not PostSCript. Since all the network print protocols on the mac rely on PS youre out of liuck unless its connected directly to MAC hardware.
If youre geeky and feeling ambitious you can probably finde a driver/ppd withh the support you need on linuxprinting.org but good luck trying to get it to work properly. I tried without success for a week to get our HP3500CLat work to work over any network protocol i could get my hands on with no luck. if you (or anyone else reading this) fares better please let me know...

RV220W Printer Sharing Across VLANs

We have 2 VLANs configured to keep 2 groups of PCs apart. Is it possible to allow both VLANs to access the same printer without allowing other traffic between these VLANs ?
Any advice would be much appreciated.
Sent from Cisco Technical Support iPhone App

Thanks for the reply Simon.
Should I place the printer in a third VLAN (as opposed to one of the exclusive VLANs containing the PCs)? If so, will it be enough to enable"Inter VLAN Routing" on this third 3rd VLAN only?
Sent from Cisco Technical Support iPhone App

Network Computer Can't See My CUPS Printer

I've installed my printer, and tried to follow the CUPS printer sharing wiki, but I haven't been able to get another computer to list it as a network printer. My printer (a HP LaserJet 1200) installed successfully on my up-to-date Arch Linux system, and prints normally. The cups and cups-browsed daemons have been enabled and are running. I have another Linux computer on my network running Fedora 17. When I go to the CUPS page (localhost:631) it does not show the Arch Linux printer. Running "nmap 192.168.1.0/24" on the Fedora computer shows the ArchLinux machine, but reports that all 1000 ports are closed.
My research on this issue has identified that there was a major change going from cups 1.5 to cups 1.6, affecting printer discovery. I note that ArchLinux is running cups 1.6.1-6, while Fedora has cups 1.5.4-11, so this may be related to my problem. However, I don't think it is normal for all ports to be closed. I have modified the cupsd.conf file to allow 192.168.1.*, but is there more I have to do to enable communication between the computers?
Any suggestions would be appreciated.

jasonwryan wrote:... older cups clients can still connect to the newer version, it just doesn't work the other way...
You seem to be saying that it should work in my case: an older cups client attempting to connect to the newer version on my server. In that case, there must be something else wrong with my configuration. Is it normal for port 631 to appear closed from a client computer?

Airprint in the Enterprise across subnets [Solution]

This is a message to help folks figure out how to setup
Airprint across wired/wireless subnets. Hopefully it will help a few people.
Airprint was designed to work with Bonjour on a local subnet/broadcast domain.
To print in the enterprise where we have wired/wireless infrastructure,
we need to use a DNS server to find the printer resources
Assumptions:
Our internal domain is: foocompany.com
We create a new subdomain: bonjour.foocompany.com
Creating a new subdomain allows up to apply DNS views so we can show print/bonjour services in
close proximity of the user.
You have a CUPS printer server (linux/apple) running at printserver.bonjour.foocompany.com
1. Setup a DNS server
If you setting up a test domain server, you can setup forwarding to your primary production server.
This way all DNS queries continue to work
In your named.conf file setup forwarding
options {
forwarders { YOURTOPNAMESERVER_IPADDR; YOURTOPNAMESERVER_IPADDR2; };
forward first;
allow-query-cache { any; }; // Allow client queries from other subnet to query from cache
Create a new zone, "bonjour.foocompany.com"
zone "bonjour.foocompany.com." { type master; file "/etc/bind/db.home"; };
zone "foocompany.com" { type forward; forward only; forwarders { YOURTOPNAMESERVER_IPADDR; YOURTOPNAMESERVER_IPADDR2; }; };
Create the following entries to support bonjour browsing
#=======DNS====Begin======
lb.dns-sd.udp IN PTR @
b.dns-sd.udp IN PTR @
dr.dns-sd.udp IN PTR @
db.dns-sd.udp IN PTR @
cf.dns-sd.udp IN PTR @
printserver IN A 10.47.203.188
# For every printer queue defined at the printer server you need to create a TXT and SRV entry
# The visual printer name that show up in the iOS listbox will be the part before .ipp.tcp, example "hpv8a", "hpv8acolor"
# _ipp and _printer seem to be equivalents, either seem to work on iOS.
# Printer 1
cups._sub._ipp.tcp IN PTR hpv8a.ipp.tcp
universal._sub._ipp.tcp IN PTR hpv8a.ipp.tcp
#Printer 2
cups._sub._ipp.tcp IN PTR hpv8acolor.printer.tcp
universal._sub._ipp.tcp IN PTR hpv8acolor.printer.tcp
hpv8a.ipp.tcp IN SRV 0 0 631 printserver
hpv8acolor.printer.tcp IN SRV 0 0 631 printserver
# The "adminurl" points to the printer queue url on the CUPS server
# The "rp" key points to the queue name as well
hpv8a.ipp.tcp IN TXT ( "txtvers=1" "qtotl=1" "rp=printers/V8A08A246LJ" "adminurl=http://printserver:631/printers/V8A_08A24
6_LJ" "ty=HP Laserjet V8A" "product=(HP LaserJet 4200)" "transparent=t" "copies=t" "duplex=t" "color=f" "pdl=application/octet-stream,
application/pdf,application/postscript,image/jpeg,image/png,image/urf" "URF=W8,SRGB24,CP1,RS600" )
hpv8acolor.printer.tcp IN TXT ( "txtvers=1" "qtotl=1" "rp=printers/V8A08A246_ColorLJ" "adminurl=http://printserver:
631/printers/V8A08A246_ColorLJ" "ty=HP Laserjet V8A Color" "product=(HP color LaserJet 4650)" "transparent=t" "copies=t" "duplex=t" "
color=t" "pdl=application/octet-stream,application/pdf,application/postscript,image/jpeg ,image/png,image/urf" "printer-type=0x801046" "URF=
W8,SRGB24,CP1,RS600" )
####Printer TEMPLATE
#cups._sub._ipp.tcp IN PTR NAMEX.printer.tcp
#universal._sub._ipp.tcp IN PTR NAMEX.printer.tcp
#NAMEX.ipp.tcp IN SRV 0 0 631 PRINTSERVERDNSNAME
#NAMEX.ipp.tcp IN TXT ( "txtvers=1" "qtotl=1" "rp=printers/QUEUENAME"
# "adminurl=http://PRINTSERVERDNSNAME:631/printers/QUEUENAME"
# "ty=Printer name"
# "product=(Printer PPD model line)" "transparent=t" "copies=t" "duplex=t" "color=f"
# "pdl=application/octet-stream,application/pdf,application/postscript,image/jpeg ,image/png,image/urf"
# "URF=W8,SRGB24,CP1,RS600" )
#=======DNS====End======
2. Setup CUPS
Add printers to the CUPS server.
Enable access to the printer queue from remote machines,
GUI: "System->Admin->Printing->Server->Server Setting: Allow printing from the internet"
Also make sure the following lines are present in /etc/cups/cupsd.conf
# Allow remote access
Port 631
Listen /var/run/cups/cups.sock
AccessLog syslog
AccessLogLevel all
LogLevel debug
MaxLogSize 0
SystemGroup lpadmin
# Enable printer sharing and shared printers.
Browsing On
BrowseOrder allow,deny
BrowseAllow all
BrowseRemoteProtocols CUPS
BrowseAddress @LOCAL
BrowseLocalProtocols CUPS dnssd
BrowseProtocols all
DefaultAuthType Basic
3. Change iPAD configs
Add your DNS server as the first DNS server in the network settting page.
Add "bonjour.foocompany.com" to the DNS domains to search
4. Test printing
Open up Photos application.
Select a picture
Select "Send To->Print"
Select "Printer", now a list of printer names should show up as defined in the DNS server
Select a printer and hit "Print"
Fast task switch to Print Center to verify print job is being sent
Thanks
Ashish Desai
Security Architect
Fidelity Investments
email: [email protected]

Update for ios 8:
With ios 8 it appears that _printer and _ipp are no longer equivalent. For this to work it looks like you have to use _ipp._tcp
Also - the underscore characters are important and they are missing from the example above.
Last - you can use the "note" field to add a second line that is displayed in smaller text below the printer name in ios 8.
Here is an updated template:
####Printer TEMPLATE
cups._sub._ipp._tcp IN PTR NAMEX._ipp._tcp
universal._sub._ipp._tcp IN PTR NAMEX._ipp._tcp
NAMEX._ipp._tcp IN SRV 0 0 631 PRINTSERVERDNSNAME
NAMEX._ipp._tcp IN TXT ( "txtvers=1" "qtotl=1" "rp=printers/QUEUENAME"
"adminurl=http://PRINTSERVERDNSNAME:631/printers/QUEUENAME"
"note=more info about printer"
"ty=Printer name"
"product=(Printer PPD model line)" "transparent=t" "copies=t" "duplex=t" "color=f"
"pdl=application/octet-stream,application/pdf,application/postscript,image/jpeg ,image/png,image/urf"
"URF=W8,SRGB24,CP1,RS600" )

FAX server in 10.5 server and across subnets

We can use 10.5 Server as a FAX server. Since I got this working a while ago, it has run reliably.
This is how we are doing it. Hopefully this will help others get it working too.
Our server: 10.5.2, Pro Intel 2x2.8 quad with a USB Apple faxmodem attached to the front USB port plugged into a standard phone line. Print service is set up and running and happens to be serving printers for us. Once the FAX seemed to get confused and not receive or send. I unplugged the USB fax, plugged it back in and it was fine again.
At the server I opened a text edit document and told the server to fax from Print > PDF > Fax PDF. A fax printer was automatically created on the server. While the fax was printing I told the printer in the Dock to "keep in dock." Opened that fax printer, choose "info" icon in top of window and renamed the fax from "external modem" to a new name so that it would be easy for our staff to use and find it. The server now has a fax on it. As anyone who has tried this has found you CANNOT edit the FAX from ServerAdmin. You can now see it as a queue with the new name it was given but editing it not possible from SA.
At the server still in System Preferences > Fax and print > the new fax appears in the bottom of the printers list under "Faxes." Select the fax. Select "receive options" and set up how the fax is to receive and place received faxes. Ours go in to a folder in a share point which is available and automounted to everyone on our network so anyone, anywhere can get the incoming faxes. The next point assumes that you will do the same.
In 10.4 and once in 10.5 I had to delete the fax manually from System Preferences and recreate it as above when everything seemed to stop working and unplugging the modem and rebooting the server did not fix the stall. As long as everything is named exactly the same when you recreate the fax, no other changes or repeat of what is described below was needed.
For each of the users in our OD:
Tell them each to do the following: Open Applications > Applescript > Folder actions setup. Check off "enable folder actions," hit the + under the left box and select the folder in the share where the faxes are being received. Now select the fax folder in the left and hit the + under the right box and choose "add - new item alert." Save as necessary. The users who do this will now get notification when a new fax arrives and is deposited by the server in the Fax folder.
Now to get the fax to the clients to fax out on. The following will also get all of your shared printers onto any off server's subnet clients. For us the fax did not even show up in local subnet clients as printers usually do. So I kept working and eventually came up with the following:
Our network:
Main location 192.168.1.* server is here.
Remote locations connected via Verizon T1 and routers with no firewalling
192.168.2.*
192.168.3.*
Our client machines :
Intel white iMacs all running 10.5.2 with no special software for faxing. Our clients are bound to and controlled by our server.
I have been trying to get our server to serve the FAX across our 2 remote subnets since 10.3. With the newer CUPS coming with 10.5 and Apple now owning it I hoped that there would be an easy solution to get non local subnet computers the ability to see shared faxes and printers. Sent a forum question and got the following which was great news
Erich Wetzel wrote:
Can anyone advise, now that Apple owns CUPS, how to allow my other
two subnets to BrowsePoll our server for its printers?
The simplest way is to change the "Allow from @LOCAL" lines to be
"Allow from all". You can also use the web interface and check the
"Allow printing from the Internet", which does the same. If you
don't want to open up that much, just add "Allow from" lines for
each subnet.
Once you make this change, *do not* toggle the printer sharing box,
or you'll have to make the changes all over again.
Michael Sweet, Easy Software Products mike at easysw dot com
Michael,
Thanks for the reply, sounds like you have my solution. Small problem, upon selecting "allow printing from internet" in the web interface and committing the changes, the server restarts and the check box is empty again. In quick tests, the other options can be turned on and off as you would expect. Is there something particular to the Apple 10.5.1 install that would not permit internet printing or not permit this change?
I think the check box state in the web interface is a known bug in
CUPS 1.3.4.
I used the web interface for cups on the server and manually added the networks as described by Michael above. I don't know if it is required but I restarted the server. Open > Safari > browse to localhost:631 and you will get the CUPS web interface. The CUPS web interface is available on servers and clients. You can also browse to an IP or FDQN:631 to get the web interface from a receptive other machine.
The server was now supposedly ready to accept "browsepoll" requests from clients. I had played with this before so I was somewhat familiar with what to do next. Essentially each client needs to be told to contact the server and ask it for its printers. That is what browsepoll does in CUPS.
At the client, be logged in as an admin user OF THE CLIENT. Using Terminal and a text editor, edit as root /etc/cups/cupsd.conf
A few lines down look for:
# Show shared printers on the local network.
Browsing On
BrowseOrder allow,deny
BrowseAllow all
After that we added :
#*added by Erich*
BrowseProtocols all
BrowseRemoteProtocols all
BrowsePoll yourserver:631
BrowsePort 631
#*added by Erich*
where "yourserver" is either the IP address or FDQN of your server as seen by the client machine.
Save the file. Reboot the client. The CUPS system on the client will now ask your server CUPS system for its printers directly and repeatedly until it gets them. If it does not get any you will not be notified in anyway other than log messages on the client, see Console > /var/log > cups to review them, and the fact that you don't get your server's printers being available on the client.
This last piece came from a discussion started by Alessandro Dellavedova : check the starting post
http://discussions.apple.com/thread.jspa?messageID=5702731&#5702731
If you go to Safari > Localhost:631 on the client, CUPS should now see both the printers and the fax which are being hosted by your server.
Here's the fun part for me, with no additional playing I was now able to see the fax we created long ago in the print dialog printer list. You do not have to go to Print > PDF > Fax PDF, you can but do not have to. Just select the fax from the printer list and the dialog changes to fax appropriate options. Now we were able to print any document to the fax directly.
Odd behavior I have yet to figure out. I do not see the fax in the System Preferences > print and fax pane on the client machines. However, I can now fax through our server from all of our clients no matter what subnet they are on.
Making the same additions to the cupsd.conf file on remote machines which VPN via the internet to your network will get them the printers and fax in the same way. I do this with a powerbook and Imac from home so i can print at and fax from work.
This is what I did to get it working for us. Hope this helps.
-Erich

This is Great! Thanks a lot, this was exactly what I was looking for!

Solution to use Airprint across subnets wired/wireless

A lot of companies are trying to figure out how to setup airprint to print
in the workplace, wired+wireless across subnets.
We finally figured it out with some DNS magic and a CUPS server.
I have documented the solution at a live document hosted at
http://sites.google.com/site/iwastepaper/
Hopefully it helps a few folks.
<Edited by Host>

You will want to make sure your APs can route from where ever you install them to the WLC managment address.
How APs find the controller can happen a few different ways:
1) DNS A record
2) Layer 2 broadcast (which you seen already)
3) IP Route Forward
4) DHCP Option 43
5) Manual Prime the AP
Most folks lead with option 43.
http://www.my80211.com/cisco-wlc-labs/2009/7/4/cisco-dhcp-option-43-configuration-nugget.html
if you check the config guide you will explain the other processes.

Can't find printer shared on Windows machine

I don't know how to connect my MacBook Pro to a printer shared by a Windows machine on my network. I have the Windows path to the printer but I don't know how to get Leopard to see the printer. (I tried the Windows tab in the Print and Fax control panel.) Can someone please tell me what is going on?

Okay, some things you need to confirm for me.
What is the workgroup name of the computer sharing the printer?
What is the ip address and subnet mask of the computer sharing the printer?
What is your Mac's ip address and subnet mask?
If your Mac and the PC have the same subnet (usually the first three numbers of the ip address) and the workgroup name is the same, then you should be able to see the share. If not, there is a manual method of connecting to a Windows share.
What you need to do is customise the add printer browser. After selecting to add a printer, control-click next to the More Printers icon to see a menu. Choose Customize Toolbar. Move the Advanced icon to the toolbar. Now click the Advanced icon to see a new menu. Change the top menu to Windows Printing. In the field after smb://, you can enter the computer name or ip address of the sharing computer, followed by a / then the printer share name. For example,
smb://192.168.40.12/Canon
Note that sometimes you have to also use account information in the queue name, especially when the guest account is disabled. In these cases, the queue name would be entered as follows;
smb://username:password@computer_name/printer_sharename
Once you enter the queue name you can then select the printer model. For some models of printers, you cannot use the driver supplied by the vendor. So you have to look at using CUPS based drivers such as those provided by Gutenprint.
HTH
PaHu

Ethernet printer sharing

Both machines are g4 933mhz running OS 10.4.11 and connected by Ethernet hub to each other and the net. Printer is a Brother CUPS driver, and driver is installed on both machines. Printer only shows up and prints on its host machine #1 but does not show in any dialog box for the 2nd machine. I have tried re-installing drivers, appletalk on and off, sharing on and off. When the machines were first connected, there was no problem, then one day the printer disappeared from the 2nd machine. I have done all I know to do (pram zaps, disk rebuild, tossing preferences, disk warrior) and am no further ahead.
I just connected another printer Samsung to machine #2 so I could at least print from it, and see that machine #1 doesn't see it either..... must be a network problem, but I am stumped.

I am at a total loss here. Let me explain my quandry:
First, I had asked for a tcpdump on the computer with the printer attached to it. You now say that what you provided was from the "slave" (machine without printer attached via USB). So first thing is that since that computer does not have a printer to share with anyone, it should not have printer sharing enabled. If printer sharing isn't enabled on that machine, I don't understand why it is spitting out these announcement messages.
Second, you have a machine without a printer tethered to it. It's IP address is 70.67.163.133, it's router (at Shaw) is 70.67.160.1, and it's subnet mask is 255.255.252.0. That subnet mask means that the "local" subnet has 2^10 possible IP addresses to it (actually, 2^10 - 2, coz 160.0 and 163.255 are "reserved values"), so the subnet that this computer belongs to is the 70.67.160.0-70.67.163.255 subnet. We can see that the router and this computer are in this subnet, as they should be.
Third, you have a machine with the printer tethered to it. It's IP address is 70.67.165.67, it's router (at Shaw) is 70.67.164.1, and it's subnet mask is 255.255.252.0. That subnet mask means that it, too, has "2^10 - 2" possible IP addresses in it's "local" subnet, so the subnet that this computer belongs to is the 70.67.164.0-70.67.167.255 subnet. We can see that the router and this computer are in this subnet, as they should be.
Looking at the valid subnet ranges to which these two computers are assigned, it can also be seen (assuming that I did my "network mathematics" correctly) that these two computers are in different subnets! Therefore, when the computer with printer sharing enabled sends out a subnet-wide broadcast message announcing the availability of its printer to be shared, the other computer to which you wanted to share that printer ignores that broadcast message, because that other computer is in a different subnet.
Frankly, I do not understand how or why two computers, plugged into the same modem and going back to the same ISP, would be put on two different subnets. Somebody smarter than me will have to explain that to me. Are you paying extra money for two DHCP addresses?
Unless somebody out there, that has a similar configuration to yours, can explain to me, or rather, explain to you, the advantages of having a configuration like what I think you have, over having a router with NAT and DHCP and its own firewall, if I were you, I would be inclined to buy an inexpensive combo 4-port ethernet router with built-in WPA or WPA2 wireless access point (D-Link, Belkin, Netgear, etc.), that does NAT and DHCP and has a built-in firewall, too, and replace your hub with it. You'll have one external IP address assigned by Shaw to your residential LAN, your computers on your personal residential LAN will be all on the same subnet and things like printer sharing will work and the broadcast messages won't be sent out past your router onto the internet.
Anyways, this is what I think is going on. It seems really weird to me. If anybody else cares to weigh in on this, I certainly encourage them to do so.

Jumpstart across subnets

Hello
I am having trouble configuring my jet toolkit to boot across subnets.
It works fine in the same subnet but when it goes across subnets it seems to lose the default router for the client.
{0} ok boot net:dhcp - install
Resetting...
POST Sequence 01 CPU Check
POST Sequence 02 Banner
LSB#00 (XSB#00-0): POST 2.12.0 (2009/09/09 15:17)
POST Sequence 03 Fatal Check
POST Sequence 04 CPU Register
POST Sequence 05 STICK
POST Sequence 06 MMU
POST Sequence 07 Memory Initialize
POST Sequence 08 Memory
POST Sequence 09 Raw UE In Cache
POST Sequence 0A Floating Point Unit
POST Sequence 0B SC
POST Sequence 0C Cacheable Instruction
POST Sequence 0D Softint
POST Sequence 0E CPU Cross Call
POST Sequence 0F CMU-CH
POST Sequence 10 PCI-CH
POST Sequence 11 Master Device
POST Sequence 12 DSCP
POST Sequence 13 SC Check Before STICK Diag
POST Sequence 14 STICK Stop
POST Sequence 15 STICK Start
POST Sequence 16 Error CPU Check
POST Sequence 17 System Configuration
POST Sequence 18 System Status Check
POST Sequence 19 System Status Check After Sync
POST Sequence 1A OpenBoot Start...
POST Sequence Complete.
Sun SPARC Enterprise M4000 Server, using Domain console
Copyright 2009 Sun Microsystems, Inc. All rights reserved.
Copyright 2009 Sun Microsystems, Inc. and Fujitsu Limited. All rights reserved.
OpenBoot 4.24.12, 32768 MB memory installed, Serial #91113890.
Ethernet address 0:21:28:6e:49:a2, Host ID: 856e49a2.
Rebooting with command: boot net:dhcp - install
Boot device: /pci@0,600000/pci@0/pci@8/pci@0/network@2:dhcp File and args: - install
1000 Mbps full duplex Link up
Timed out waiting for BOOTP/DHCP reply
Timed out waiting for BOOTP/DHCP reply
Timed out waiting for BOOTP/DHCP reply
Timed out waiting for TFTP reply
Timed out waiting for TFTP reply
Timed out waiting for TFTP reply
Timed out waiting for TFTP reply
I have entered the router info in the defaultrouters file
kenapps08g:global# cat defaultrouters
# You can use this file to allow templates to be auto-populated with additional
# default router settings, especially useful for managing large numbers o
# server templates.
# Format:
# <subnet> <mask> <default router>
# Example:
# 192.168.1.0 255.255.255.0 192.168.1.254
10.0.1.0 255.255.255.0 10.0.1.1
10.0.2.0 255.255.255.0 10.0.2.1
10.0.3.0 255.255.255.0 10.0.3.1
</opt/SUNWjet/etc>
kenapps08g:global# more dhcp.conf
# This file is used to control some of the options for the DHCP boot
# environment
# DHCPDIR: The replies sent out by DHCP are limited in length; we use
# this directory to create symlinks to the actual Solaris
# media dirs; the intention is to keep paths short!
# N.B. If you change this, please make sure the new area is
# properly shared in /etc/dfs/dfstab
DHCPDIR="/dhcp"
# DEBUG_DHCP keep temporary files around after client_allocate_pdhcp.SunOS
# has run. Non-null invokes debug
DEBUG_DHCP=""
# REMOTE_DHCP define the hostname of the Sun server running Sun's DHCP daemon
REMOTE_DHCP="kenapps08g"
# REMOTE_DHCP_METHOD define what method to use to propogate. ssh is currently
# supported and requires you set up a trust relationship
# between this server and it.
REMOTE_DHCP_METHOD="ssh"
# DHCP_FORMAT Which dhcp server type is supported. SUN is currently supported,
# however, ISC is still in development. If REMOTE_DHCP is set,
# you must set DHCP_FORMAT to SUN. Valid entries are "SUN"
# and "NOOP". NOOP can be used if you are manually setting
# up your own DHCP server with the required parameters.
DHCP_FORMAT="SUN"
kenapps08g:global# more dhcp_servers
# You can use this file to define the DHCP servers responsible
# for different subnets.
# This is only required if you have multiple DHCP servers.
# If a match is found, the settings in this file will be used,
# otherwise the DHCP server defined in dhcp.conf will be used.
# Format:
# <client network> <client mask> <dhcp-server-name> <dhcp-server-tyep> <method>#
# <dhcp-server-name> overrides the REMOTE_DHCP setting
# <dhcp-server-type> overrides the DHCP_FORMAT setting
# <method> overrides the REMOTE_DHCP_METHOD setting
# Example:
# 192.168.1.0 255.255.255.0 dhcpserver1 SUN ssh
10.0.1.210 255.255.255.0 kenapps08g SUN ssh
10.245.64.10 255.255.255.0 lisjump01g SUN ssh
kenapps08g:global# more jumpstart.conf
# This config file defines the jumpstart specific variables.
# Version: $Revision: 1.8 $
# Last Updated; $Date: 2009/04/15 12:41:29 $
# Location of the additional media for patches and packages:
# These paths should be URI form e.g. nfs://<serverip>/<path> or <path>
# Currently only PKG_DIR and PATCH_DIR can be on a remote NFS server.
# If they are just <path>, the appropriate address of the JumpStart server
# will be added.
# N.B. if the media location is on a different server, please ensure it is
# routable from the client !
# You can specify an alternative location for where the client can
# NFS mount the /opt/SUNWjet directory. Simply provide the IP address
# of the server or the IP address and path on the remote server
# in the JS_CFG_SVR variable. However, this MUST be mounted
# on the JET server in /opt/SUNWjet as well, and be rw by root.
# e.g. JS_CFG_SVR="nas_server1" or
# JS_CFG_SVR="nas_server1:/unixshare/SUNWjet"
# When using an NFS server for images, even though the JET server
# MUST have the boot media locally, it is possible to have the client
# net boot from the remote NFS server. By default, clients will boot from
# the JET server. To override this, set JS_CLIENT_BOOT to "remote".
JS_Default_Root_PW=M4JVhMPO9CaQw
JS_BUILD_DIR=/var/opt/sun/jet
JS_PKG_DIR=/vendor/jumpstart/pkgs
JS_PATCH_DIR=/vendor/jumpstart/patches
JS_CFG_SVR=
JS_SOLARIS_DIR=/vendor/jumpstart
#JS_DHCP_VENDOR="SUNW.Ultra-5_10 SUNW.Ultra-30"
JS_DHCP_VENDOR="SUNW.Sun-Fire-T1000 SUNW.Sun-Fire-V240 SUNW.SPARC-Enterprise"
#JS_CLIENT_MANAGEMENT="bootp"
JS_CLIENT_BOOT="local"
kenapps08g:global# more server_interfaces
# You can use this file to help JET determine the correct IP address to
# use when it is configured on multi-homed hosts. It is also used to
# define which servers on different subnets whcih can be used in conjnction
# with dhcp.
# As we don't know which side of the server clients will connect through,
# you can set things up here - especially useful if this server is not
# a router either.
# Format:
# <client network> <client mask> <our preferred ip address>
# Example:
# 192.168.1.0 255.255.255.0 10.0.0.1
10.245.64.0 255.255.255.0 10.0.1.210
10.0.3.0 255.255.255.0 10.0.1.210
It has to be a defaultrouter setting somewhere because I can ping the server during jumpstart only from its own subnet.
during the dhcp part it looks like the traffic is coming thru and it gets its offer then during the tftp part no traffic comes across anymore
I am stuck on this one.
thanks

this file is in place with the interfaces
kenapps08g:global# cat defaultrouters
# You can use this file to allow templates to be auto-populated with additional
# default router settings, especially useful for managing large numbers o
# server templates.
# Format:
# <subnet> <mask> <default router>
# Example:
# 192.168.1.0 255.255.255.0 192.168.1.254
10.0.1.0 255.255.255.0 10.0.1.1
10.0.3.0 255.255.255.0 10.0.3.1
183.1.2.0 255.255.255.0 183.1.2.209
</opt/SUNWjet/etc>
kenapps08g:global# cat server_interfaces
# You can use this file to help JET determine the correct IP address to
# use when it is configured on multi-homed hosts. It is also used to
# define which servers on different subnets whcih can be used in conjnction
# with dhcp.
# As we don't know which side of the server clients will connect through,
# you can set things up here - especially useful if this server is not
# a router either.
# Format:
# <client network> <client mask> <our preferred ip address>
# Example:
# 192.168.1.0 255.255.255.0 10.0.0.1
10.0.1.0 255.255.255.0 10.0.1.210
10.0.3.0 255.255.255.0 10.0.1.210
183.1.2.0 255.255.255.0 10.0.1.210

CUPS printer sharing across subnets?

Similar Messages

Maybe you are looking for