Connecting multiple wireless printers

I need to connect 2 wireless printers. 1st is a multifunction with fax and the 2nd is a multifunction without a fax. I can get both to print, but the HP connect software for faxing and scanning only shows up for the last printer connected. I need to be able to select any printer. Is this possible?

What is the model no of the Router...?
What firmware version you are using on the router..?
Which operating system you are using on your wife's computer...?
As you are able to connect your wireless computer using WPA Security then,make sure that your wife's computer does support WPA/WPA2 Security..Normally Windows XP does not support that and you have to download the patch for the same.

Similar Messages

HP Wireless Printers cannot connect to WPA2-secured WiFi networks with Cisco/Meraki WAPs

In the last two months, I've had the displeasure of working with two very different HP printers and attempting to make them work on a WPA2-secured wireless network. All attempts to authenticate fail with "invalid phassphrase".
I'm not the first person to encounter this, it's a problem with many different HP wireless printers (I just happen to have physical access to the OfficeJet Pro 8610 & Deskjet 3511).
My equipment is a Cisco ASA 5505 Firewall running ASA 9.1x & Cisco Aironet 1142 running IOS 15.3.x.
What does work on the WPA2/AES SSID: Apple MacBook Air running OSX 10.10.2, Three Windows-Based laptops running Windows 8.1 Update 1, an iPhone 5s, Three Windows Phone 8.1 devices, Roku 2, PlayStation 4, PlayStation 3, Sharp Aquos TV, Amazon Streaming Stick, and an Android Tablet (Jellybean). Basically, everything.
What does not work on the WPA2 network: OfficeJet Pro 8610 & Deskjet 3511.
To test the theory there is a problem with HP's implementation of WPA2 with regard to Cisco Aironet IOS, I built out a second SSID that only works in WPA/TKIP mode. This solution works. Both HP printers will join the WPA/TKIP network.
So, I'm able to demonstrate there is a certain connectivity issue. When i look at AAA Debug on the WAP's console, I can observe the HPs attempt to authenticate "Bind I/F" on the WPA2 SSID, however they do not achieve authentication and do not pass the AAA phase. However, on the WPA SSID, they bind and authenticate successfully.
To help illustrate this, here is my WAP running config. It's about as simple as it can get. There is no relevant MAC filtering or ACLs bound to any interface. Noting that I have an ACL on remote access to the WAP (i.e. Locked down to SSH, disabling telnet). The main point being that the ASA firewall is not a factor in this problem as the issue is at the WAP before WPA2 authentication can complete, therefore the printers never reach the network / when the printers connect to the WPA network, the operate fully & correctly.
If anyone at HP can indicate why this particular config is somehow improper or broken, that would be fantastic. There should be no reason why Cisco / Meraki WAP owners have to lower wireless encryption standards just for a printer, be forced into wired, create separate SSIDs with lower encryption specifically for a device.
Building configuration...
Current configuration : 6064 bytes
! Last configuration change at 12:46:47 UTC Fri Aug 20 1993 by admin
version 15.3
no service pad
service timestamps debug datetime msec
service timestamps log datetime msec
service password-encryption
hostname 10-10-50-1
logging buffered 1024768
logging rate-limit console 9
aaa new-model
aaa authentication login default local
aaa authorization exec default local
aaa session-id common
no ip source-route
no ip cef
ip domain name freedom.local
dot11 syslog
dot11 vlan-name inside vlan 50
dot11 vlan-name inside-wpa-only vlan 70
dot11 ssid inside
   vlan 50
   band-select
   authentication open
   authentication key-management wpa version 2
   mbssid guest-mode
   wpa-psk ascii 7 xxxxxx
   information-element ssidl
dot11 ssid inside-wpa-only
   vlan 70
   band-select
   authentication open
   authentication key-management wpa
   mbssid guest-mode
   wpa-psk ascii 7 xxxxxx
   information-element ssidl
dot11 band-select parameters
   cycle-count 3
   cycle-threshold 200
   expire-supression 20
   expire-dual-band 60
   client-rssi 75
dot11 wpa handshake timeout 500
dot11 network-map
username ADMIN privilege 15 secret 5 xxxxxx
ip ssh version 2
bridge irb
interface Dot11Radio0
no ip address
no ip route-cache
encryption vlan 50 mode ciphers aes-ccm
encryption vlan 70 mode ciphers aes-ccm tkip
ssid inside
ssid inside-wpa-only
antenna gain 0
mbssid
speed basic-1.0 basic-2.0 basic-5.5 basic-11.0 6.0 9.0 12.0 18.0 24.0 36.0 48.0 54.0 m0. m1. m2. m3. m4. m5. m6. m7. m8. m9. m10. m11. m12. m13. m14. m15.
channel 2412
station-role root
l2-filter bridge-group-acl
interface Dot11Radio0.50
encapsulation dot1Q 50 native
no ip route-cache
bridge-group 1
bridge-group 1 subscriber-loop-control
bridge-group 1 spanning-disabled
bridge-group 1 block-unknown-source
no bridge-group 1 source-learning
no bridge-group 1 unicast-flooding
interface Dot11Radio0.70
encapsulation dot1Q 70
no ip route-cache
bridge-group 70
bridge-group 70 subscriber-loop-control
bridge-group 70 input-address-list 700
bridge-group 70 output-address-list 700
bridge-group 70 spanning-disabled
bridge-group 70 block-unknown-source
no bridge-group 70 source-learning
no bridge-group 70 unicast-flooding
interface GigabitEthernet0
no ip address
no ip route-cache
duplex auto
speed auto
interface GigabitEthernet0.50
encapsulation dot1Q 50 native
no ip route-cache
bridge-group 1
bridge-group 1 spanning-disabled
no bridge-group 1 source-learning
interface GigabitEthernet0.70
encapsulation dot1Q 70
no ip route-cache
bridge-group 70
bridge-group 70 spanning-disabled
no bridge-group 70 source-learning
interface BVI1
mac-address xxxx.xxxx.xxxx
ip address 10.10.50.1 255.255.255.0
no ip route-cache
ip forward-protocol nd
ip http server
ip http authentication aaa
no ip http secure-server
ip http help-path http://www.cisco.com/warp/public/779/smbiz/prodconfig/help/eag
ip route 0.0.0.0 0.0.0.0 10.10.50.2
logging history size 100
access-list 111 permit tcp any any neq telnet
bridge 1 route ip
line con 0
access-class 111 in
line vty 0 4
access-class 111 in
length 0
transport input ssh
line vty 5 15
access-class 111 in
transport input ssh
end

I get the same behavior with a laserjet m451nw. I need to enable tkip to get the printer working, it doesn't support pure aes-ccm (every other device here supports pure aes-ccm, even cheap ones), although it's advertised as working.
The following snippet of config works, but I still think it should work without the tkip "hack".
dot11 ssid whatever
vlan 1
band-select
authentication open
authentication key-management wpa version 2
interface Dot11Radio0
encryption vlan 1 mode ciphers aes-ccm tkip

Why can't I use two 8500 wireless printers on one router? The 8500 A910 looses it's connection.

Why can't I use two 8500 wireless printers on one router? The 8500 A910 looses it's connection after awhile.

What router? What operating system? Are they both A910s?
Say thanks by clicking "Kudos" "thumbs up" in the post that helped you.
I am employed by HP

Wireless Printers No Longer Connect after BT Infi...

Hi all,
I have a very strange issue - a friend of mine has 3 wireless printers installed at home and used to have a BT home Hub 2.0. They all connected wirelessly without issue and he could print from any computer in the house with the software on.
Last week he had BT infinity fitted and a new home hub supplied.....he then found he could not connect to his printers and asked me to take a look......I firstly uninstalled all his printer software and went through the installation process again. While all 3 printers are wireless, 2 connect independantly (via printer console) and one needs to be connected to the computer to undertake wireless conection and set up.
I installed the 2 printers that could connect wirelessly withouth needing to connect to the PC - I checked the home hub settings and both printers can be seen as connected. I then installed the software to the computer and when they were trying to "find printer" on the "connect wirelessly" page - it kept saying that it could not find the printer or it could not connect to the printer.
I thought it may be the computer with the issue so I tried on 2 other computers including my own windows 7 laptop, but while I could see the printer as connected while on the home hub page, I was unable to access the printer when setting up.
I spent 30 minutes with a technical guy who admitted he did not know the settings for the router and told me to try and switch off the firewall on the router! - I did, it did not work so I swtiched it back on!
I suspect it is a simple setting issue although seeing the issues online I now have my doubts and wondered if anyone here had an idea before he has to pay for help -
Thanks in advance
Solved!
Go to Solution.

Hello,
Diver9, do you have any more information on the actual problem.
When you are unable to print:
1: Can you ping the static IP addresses?
2: What do the printers network status pages state?
3: What channel has the Homehub selected? Have you tried fixing the channel to an unused channel (as found by inssider?)
4: Does the homehub still think the printers are connected? (http://192.168.1.254->Home Network-><Device>)
I know it is a hassle troubleshooting, but it's sensible to find out what has actually gone wrong. Your experience may help someone in the future or give BT something to look at improving in the next firmware. For example, listing the model of each printer in this post might help. The more information the better.
I have used a network printer with v1, v1.5, v2a and v3 of the homehub family and haven't experienced any printing problems. I appreciate that I might just be lucky, but your information might help someone.

The HP (USB connected) and Epson (wireless) printers keep losing their connection with my Mac mini. I have to physically disconnect the HP and then reconnect for the Mac to find it. Turning off the wireless Epson doesn't work. All software is updated.

My HP (USB connected) and Epson (wireless) printers keep losing their connection with my Mac mini. I have to physically disconnect the HP and then reconnect for the Mac to find it. Turning off the wireless Epson doesn't resolve anything. All software/drivers have been updated.

My HP (USB connected) and Epson (wireless) printers keep losing their connection with my Mac mini. I have to physically disconnect the HP and then reconnect for the Mac to find it. Turning off the wireless Epson doesn't resolve anything. All software/drivers have been updated.

Wireless printers refusing to connect to OS 10.9

I have two wireless printers - A HP and an Epson. Neither will connect to a Mac using OS Mavericks 10.9. I have been told by HP that their drivers have not yet been upgraded to deal with 10.9. The Epson support basically said the printer was working perfectly so it was not their problem.
Anyone else have this difficulty

thanks a million for taking the time to reply. My HP printer is a HP Officejet PRO 8500A Plus 910. Over a two day period I spend several hours on the phone to their support people and when they finally concluded it was a problem with the printer talking to the Mac , they admitted that their own HP printer system was not up to date.
I asked if they could email me and tell me when they had their software up to date and was told they could not email me, I would just have to check their website ever day.
The Epson printer is an Expression Home XP 415 (just bought) and basically after 20 minutes on the phone to their helpline they could not bring it any further. They told me the printer was connecting perfectly to the internet (which I knew) and the computer was connecting to the internet (which I also knew) but that they could not talk to each other. They just left it there and said they could not help further.
I suspect, however, that after my HP experience the Epson problem is exactly the same. Everything seems to be linked to upgrading to OS Mavericks 10.9.
Thanks again for the link to the site. HP never mentioned it. Will try that now.

Since upgrading, both our wireless printers are still visible, but OSX will not connect with them. Both work via connecting from other sources via the same wireless router (airport). What do I need to do to get my printing/scanning working again?

Since upgrading, both our wireless printers are still visible, but OSX will not connect with them. Both work via connecting from other sources via the same wireless router (airport). What do I need to do to get my printing/scanning working again?

First thing to try is reset Printing System:
OS X Mavericks: Reset the printing system
Next would be reset the router (power off 15 secs then back on). And, 2 minutes later, reset the printers 1 by 1.

Connecting to epson wireless printers

"upgraded" from linksys-n broadband router to the wrt1900ac, now despite my various attempts, unable to connect my epson workforce545 and workforce 845, these wireless printers connected to N w/o any trouble. any ideas towards resolving this issue. used chat w/spt to no avail. thanks

Hi oldguy70, were you prompted for the password when you tried to connect the printers wirelessly? Was there any error message? I suggest that you delete all networks saved on the printer and try connecting again. Make sure that the name for the 2.4Ghz and the 5Ghz are different so you would know which network they are having an issue with. Try WPA Personal if WPA2 doesn't work. Hope that helps.

Issues connecting multiple machines wirelessly to WRT54G router

I have a WRT54G router and have one wired desktop, two laptops that connect fine and then I have a netbook and another desktop with wireless adapter I am having issues with connecting. I used the wizard and set each machine up with the downloaded executable, it says it works but when I try to connect I get unable to connect to wireless network message. ANy ideas? Any help is greatly appreciated

You have one computer connected with the cable and 2 wireless computers working fine. That means the router is working fine.
I think you should check the wireless settings of the router first.
You have one computer connected to the router with the Ethernet cable. Open the setup page of the router and go to Wireless tab. Check the wireless network name. Go to wireless security sub tab. Check the wireless security mode and make sure that you have the correct password of your wireless network. Go to Wireless MAC address filter sub tab and make sure that it is disabled.
Try to connect to the wireless network again and see if that works.

Problem Connecting Multiple HDs to AEBS

Sounds like this is a recurring theme on this discussion board.
I am able to get 2 drives (WD 500GB My Book Essential) working using a powered USB hub, but when I connect a 3rd drive, the whole system crashes. I've connected the drive in pairs, and the drives will all connect singularly or in a pair, but once all 3 are connected, the AEBS crashes.
I've "upgraded" to firmware 7.1 (before I knew it was causing problems). BTW, I also have 2 printers hooked to the USB hub.
I started with an unpowered hub, and couldn't get even one drive working. Once I went to a powered hub, I was able to run 2. Hopefully this will help someone a little.
CWJ

Power cycle is not normal if your doing it almost everyday.Multiple wireless connection is not an issue here.Check the firmware on your router since you have a lot of cases of disconnection problem.

My Macbook Air won't recognize either of my wireless printers. What can I do?

I've had my MacBook Air for a year with two wireless printers connected. Today, I tried to print something and it seemed my Mac wasn't recognizing my printers anymore. I went into System Preferences - Printers and after trying other things, I deleted both printers assuming that I would just re-add them thereby rebooting the system. However, now when I follow the directions and go into System Preferences - Printers - Add (the plus sign), nothing happens. I can't add anything, nothing shows up, the search function doesn't work. I don't know what else to do. Any ideas??

Thanks for replying so fast. Before I tried your suggestion, I tried another suggestion that I saw that actually did work and I want to list it here for others that might have same issue. This is what I did.
1. Turned off and unplugged printers (I had two).
2. Turned off computer completely
3. Went to bed (this is optional)
4. Next morning - unplugged the router, left it unplugged for 5 minutes, then plugged it back in.
5. Plugged printer in and turned it on and ran it through the set up wizard - some printers may do the set up automatically
6. Turned my computer on
7. Went into Settings - System Preferences - Printers - clicked on the + sign to add and my printer showed up (nothing showed up when I was initially having the problem)
8. Clicked on my printer that I wanted to add and clicked the add button....bottom right of screen
9. Went into my document and printed it
10. Then did the same with second printer - and my Mac recognized that one as well once I turned it on and did set up
Hope this helps anyone experiencing the same issue!

Using 2 separate 8500 wireless printers

I own 2 HP 8500 wireless printers. 1 is at home, and 1 is at my office.
Both of them work perfectly, all features work.
I have a HP tx1410 laptop, running Vista with SP2 installed.
I have the laptop set up so that all the wireless printing features work at my office, but when I bring my laptop home and want to print on the home printer... the wireless feature won't work from my laptop. The printer shows up in the network and sharing, but it seems like the drivers on my laptop are configured to work with the printer at the office.
This is only a problem when using my laptop to use both of the printers.
It is not a problem with the hardware, or the network because using either of the printers separately with a different computer works perfectly.
I've tried to run 'add a printer' in my printers folder. My home wireless shows up as a valid printer to select in the "searching for available printers" window, but the operation fails. error code is 0x00000643
again, the problem is not with the hardware or the network.
If, I uninstall the hp drivers, then reinstall clean at home - then the home wireless works perfectly but then wireless printing on the work printer doesn't work.
for some reason my laptop can't save / keep / use the configuration settings for the exact same 2 HP wireless printers.

Once you install the home printer, insert the installation CD and click on 'Add A Device'. Now select the connection type as ethernet\wireless, and it'll find and add your work printer(you need to be at work).
Make it easier for other people to find solutions, by marking my answer with \'Accept as Solution\' if it solves your problem.
Click on the BLUE KUDOS button on the left to say "Thanks"
I am an ex-HP Employee.

HP Officejet Pro 8000 Wireless: HP printer unable to connect to wireless router.

Installing new printer, getting error msg saying HP printer unable to connect to wireless router. MAC address filtering may be enabled on your wireless router which can prevent HP printer from connecting to your wireless network during setup.
SOLUTION says: If MAC address filtering is enabled and you would like to keep it enabled, you must add the MAC addressof your printer to the list of permitted devices for your wireless router before continuing.
My router is WD My Net N900 Router. MAC filtering is diabled. My security mode is WPA/WPA2 Personal.
I have run out of ideas to try and fix the issues, would appreciate some help.
Thanks,

Hi Jamshidk
I am surprised you are getting that message and you checked the router settings and it is showing that the Mac Filtering is disabled.
I would suggest connecting the printer to the router with a ethernet cable to get a valid IP address and then setup the wireless.
Print a configuration report.
http://h10025.www1.hp.com/ewfrf/wc/document?cc=us&dlc=en&docname=c01554589&lc=en&product=3760410&tmp...
Type the IP address from the configuration page in the address bar into internet explorer browser. This will open the embedded web server for the printer. Click on the Networking tab, on the left hand side select wireless. After this is setup and applied, disconnect the ethernet cable.
Should be on the wireless network. Takes about 1 minute.
Run the add printer wizard.
Go to start, devices and printers and select add a printer. (Win 7)
Test the printer.
If you need more assistance just let me know.
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos Thumbs Up" on the right to say “Thanks” for helping!
Gemini02
I work on behalf of HP

Wicd connects to Wired fine but is unable to connect to wireless

I don't think I have changed anything, but now wicd will not connect to any wireless network (Stuck at optaining IP address, or Verifying association if I use static ip, and then, without saying a specific error, quits connecting and goes back to not connected.)
Latest update:
[2012-06-30 11:22] Running 'pacman -Syyu'
[2012-06-30 11:22] synchronizing package lists
[2012-06-30 11:22] starting full system upgrade
[2012-06-30 11:25] upgraded audacity (2.0.0-1 -> 2.0.1-1)
[2012-06-30 11:25] upgraded ca-certificates-java (20120524-1 -> 20120608-1)
[2012-06-30 11:25] upgraded libsystemd (185-2 -> 185-4)
[2012-06-30 11:25] upgraded systemd-tools (185-2 -> 185-4)
[2012-06-30 11:25] upgraded dbus-core (1.6.0-4 -> 1.6.0-5)
[2012-06-30 11:25] upgraded dbus-glib (0.98-1 -> 0.100-1)
[2012-06-30 11:25] upgraded chromium (19.0.1084.56-1 -> 20.0.1132.47-1)
[2012-06-30 11:25] upgraded cryptsetup (1.4.2-2 -> 1.4.3-1)
[2012-06-30 11:25] upgraded docbook-xsl (1.77.0-1 -> 1.77.1-2)
[2012-06-30 11:25] upgraded git (1.7.11-1 -> 1.7.11.1-1)
[2012-06-30 11:25] upgraded hyphen (2.8.3-1 -> 2.8.4-1)
[2012-06-30 11:25] upgraded imagemagick (6.7.7.7-1 -> 6.7.7.10-1)
[2012-06-30 11:25] upgraded sysvinit (2.88-3 -> 2.88-6)
[2012-06-30 11:25] upgraded initscripts (2012.06.1-1 -> 2012.06.2-1)
[2012-06-30 11:25] upgraded poppler (0.20.0-1 -> 0.20.1-1)
[2012-06-30 11:25] upgraded poppler-glib (0.20.0-1 -> 0.20.1-1)
[2012-06-30 11:25] upgraded inkscape (0.48.3.1-3 -> 0.48.3.1-4)
[2012-06-30 11:25] >> Traceroute is now provided by core/traceroute
[2012-06-30 11:25] upgraded iputils (20101006-2 -> 20101006-3)
[2012-06-30 11:25] upgraded keyutils (1.5.5-2 -> 1.5.5-3)
[2012-06-30 11:25] upgraded lib32-dbus-core (1.4.20-1 -> 1.6.0-1)
[2012-06-30 11:25] upgraded lib32-libtiff (4.0.1-1 -> 4.0.2-1)
[2012-06-30 11:25] upgraded libnl (3.2.9-1 -> 3.2.11-1)
[2012-06-30 11:25] upgraded libusbx (1.0.12-1 -> 1.0.12-2)
[2012-06-30 11:25] upgraded libpcap (1.2.1-2 -> 1.3.0-1)
[2012-06-30 11:25] upgraded libreoffice-en-US (3.5.4-1 -> 3.5.4-2)
[2012-06-30 11:26] upgraded libreoffice-common (3.5.4-1 -> 3.5.4-2)
[2012-06-30 11:26] upgraded libreoffice-base (3.5.4-1 -> 3.5.4-2)
[2012-06-30 11:26] upgraded libreoffice-calc (3.5.4-1 -> 3.5.4-2)
[2012-06-30 11:26] upgraded libreoffice-draw (3.5.4-1 -> 3.5.4-2)
[2012-06-30 11:26] upgraded libreoffice-gnome (3.5.4-1 -> 3.5.4-2)
[2012-06-30 11:26] upgraded libreoffice-impress (3.5.4-1 -> 3.5.4-2)
[2012-06-30 11:26] upgraded libreoffice-kde4 (3.5.4-1 -> 3.5.4-2)
[2012-06-30 11:26] upgraded libreoffice-math (3.5.4-1 -> 3.5.4-2)
[2012-06-30 11:26] upgraded libreoffice-postgresql-connector (3.5.4-1 -> 3.5.4-2)
[2012-06-30 11:26] upgraded libreoffice-sdk (3.5.4-1 -> 3.5.4-2)
[2012-06-30 11:26] upgraded libreoffice-sdk-doc (3.5.4-1 -> 3.5.4-2)
[2012-06-30 11:26] upgraded libreoffice-writer (3.5.4-1 -> 3.5.4-2)
[2012-06-30 11:26] upgraded libwbclient (3.6.5-3 -> 3.6.6-1)
[2012-06-30 11:26] upgraded linux-firmware (20120227-2 -> 20120625-1)
[2012-06-30 11:26] warning: /etc/pacman.d/mirrorlist installed as /etc/pacman.d/mirrorlist.pacnew
[2012-06-30 11:26] upgraded pacman-mirrorlist (20120211-1 -> 20120626-1)
[2012-06-30 11:26] upgraded pciutils (3.1.9-2 -> 3.1.10-1)
[2012-06-30 11:26] upgraded pixman (0.26.0-1 -> 0.26.2-1)
[2012-06-30 11:26] upgraded psmisc (22.18-2 -> 22.19-1)
[2012-06-30 11:26] upgraded python-dbus-common (1.1.0-2 -> 1.1.1-1)
[2012-06-30 11:26] upgraded python2-dbus (1.1.0-2 -> 1.1.1-1)
[2012-06-30 11:26] upgraded qt (4.8.2-1 -> 4.8.2-2)
[2012-06-30 11:26] upgraded raptor (2.0.7-2 -> 2.0.8-1)
[2012-06-30 11:26] upgraded smbclient (3.6.5-3 -> 3.6.6-1)
[2012-06-30 11:26] upgraded vlc (2.0.1-2 -> 2.0.2-1)
[2012-06-30 11:33] Running 'pacman -U android-sdk-r20-2-x86_64.pkg.tar.xz'
[2012-06-30 11:34] You need to source /etc/profile or relogin to add the Android SDK tools to your path.
[2012-06-30 11:34] The android group has been removed, install android packages as root.
[2012-06-30 11:34] upgraded android-sdk (r18-1 -> r20-2)
[2012-06-30 11:35] Running 'pacman -U android-sdk-platform-tools-r12-1-any.pkg.tar.xz'
[2012-06-30 11:36] upgraded android-sdk-platform-tools (r11-2 -> r12-1)
[2012-06-30 11:36] Running 'pacman -U eclipse-android-20.0.0-1-any.pkg.tar.xz'
[2012-06-30 11:36] upgraded eclipse-android (18.0.0-2 -> 20.0.0-1)
[2012-06-30 11:37] Running 'pacman -U eclipse-emf-2.8.0-1-any.pkg.tar.xz'
[2012-06-30 11:38] upgraded eclipse-emf (2.7.2-2 -> 2.8.0-1)
[2012-06-30 11:38] Running 'pacman -U eclipse-gef-3.8.0-1-any.pkg.tar.xz'
[2012-06-30 11:40] upgraded eclipse-gef (3.7.2-2 -> 3.8.0-1)
[2012-06-30 11:41] Running 'pacman -U pgl-2.2.1-2-x86_64.pkg.tar.xz'
[2012-06-30 11:41] warning: directory permissions differ on tmp/
filesystem: 1777 package: 755
[2012-06-30 11:41] upgraded pgl (2.2.1-1 -> 2.2.1-2)
RC.conf
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="moulder"
# Use 'ip addr' or 'ls /sys/class/net/' to see all available interfaces.
# Wired network setup
# - interface: name of device (required)
# - address: IP address (leave blank for DHCP)
# - netmask: subnet mask (ignored for DHCP) (optional, defaults to 255.255.255.0)
# - broadcast: broadcast address (ignored for DHCP) (optional)
# - gateway: default route (ignored for DHCP)
# Static IP example
# interface=eth0
# address=192.168.0.2
# netmask=255.255.255.0
# broadcast=192.168.0.255
# gateway=192.168.0.1
# DHCP example
# interface=eth0
# address=
# netmask=
# gateway=
interface=eth0
address=
netmask=
broadcast=
gateway=
# Setting this to "yes" will skip network shutdown.
# This is required if your root device is on NFS.
NETWORK_PERSIST="no"
# Enable these netcfg profiles at boot-up. These are useful if you happen to
# need more advanced network features than the simple network service
# supports, such as multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network.d
# This requires the netcfg package
#NETWORKS=(main)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
# If something other takes care of your hardware clock (ntpd, dual-boot...)
# you should disable 'hwclock' here.
DAEMONS=(hwclock syslog-ng !network !networkmanager netfs crond dbus !dhcpcd wicd alsa acpid pgl laptop-mode slim)
when trying # dhcpcd wlan0 (Although I use dhclient in wicd)
dhcpcd[2066]: version 5.5.6 starting
dhcpcd[2066]: wlan0: waiting for carrier
dhcpcd[2066]: timed out
iwconfig
eth0 no wireless extensions.
lo no wireless extensions.
wlan0 IEEE 802.11bgn ESSID:"cannedyams"
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=15 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off
wicd log when connecting by wire
2012/06/30 16:28:56 :: Internet Systems Consortium DHCP Client 4.2.3-P2
2012/06/30 16:28:56 :: Copyright 2004-2012 Internet Systems Consortium.
2012/06/30 16:28:56 :: All rights reserved.
2012/06/30 16:28:56 :: For info, please visit https://www.isc.org/software/dhcp/
2012/06/30 16:28:56 ::
2012/06/30 16:28:57 :: Listening on LPF/eth0/b8:70:f4:83:a4:3b
2012/06/30 16:28:57 :: Sending on LPF/eth0/b8:70:f4:83:a4:3b
2012/06/30 16:28:57 :: Sending on Socket/fallback
2012/06/30 16:28:57 :: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
2012/06/30 16:28:58 :: DHCPREQUEST on eth0 to 255.255.255.255 port 67
2012/06/30 16:28:58 :: DHCPOFFER from 10.0.1.1
2012/06/30 16:28:58 :: DHCPACK from 10.0.1.1
2012/06/30 16:28:58 :: bound to 10.0.1.13 -- renewal in 5654 seconds.
2012/06/30 16:28:58 :: DHCP connection successful
2012/06/30 16:28:58 :: Connecting thread exiting.
2012/06/30 16:28:59 :: Sending connection attempt result success
when wirelessly
2012/06/30 16:25:19 :: Internet Systems Consortium DHCP Client 4.2.3-P2
2012/06/30 16:25:19 :: Copyright 2004-2012 Internet Systems Consortium.
2012/06/30 16:25:19 :: All rights reserved.
2012/06/30 16:25:19 :: For info, please visit https://www.isc.org/software/dhcp/
2012/06/30 16:25:19 ::
2012/06/30 16:25:20 :: Listening on LPF/wlan0/bc:77:37:07:fd:96
2012/06/30 16:25:20 :: Sending on LPF/wlan0/bc:77:37:07:fd:96
2012/06/30 16:25:20 :: Sending on Socket/fallback
2012/06/30 16:25:20 :: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
2012/06/30 16:25:26 :: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
2012/06/30 16:25:38 :: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
2012/06/30 16:25:53 :: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
2012/06/30 16:26:07 :: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
2012/06/30 16:26:21 :: No DHCPOFFERS received.
2012/06/30 16:26:21 :: No working leases in persistent database - sleeping.
2012/06/30 16:26:21 :: DHCP connection failed
2012/06/30 16:26:21 :: exiting connection thread
2012/06/30 16:26:26 :: Sending connection attempt result dhcp_failed
lspci
08:00.0 Network controller: Intel Corporation Centrino Wireless-N 1030 (rev 34)
I've already switched to dclient and turned power saving features off
Any Ideas?
Last edited by parkermcg (2012-06-30 21:41:14)

messages.log when connecting to wireless
Jun 30 17:21:42 localhost dhclient: Internet Systems Consortium DHCP Client 4.2.3-P2
Jun 30 17:21:42 localhost dhclient: Copyright 2004-2012 Internet Systems Consortium.
Jun 30 17:21:42 localhost dhclient: All rights reserved.
Jun 30 17:21:42 localhost dhclient: For info, please visit https://www.isc.org/software/dhcp/
Jun 30 17:21:42 localhost dhclient:
Jun 30 17:21:42 localhost dhclient: Listening on LPF/wlan0/bc:77:37:07:fd:96
Jun 30 17:21:42 localhost dhclient: Sending on LPF/wlan0/bc:77:37:07:fd:96
Jun 30 17:21:42 localhost dhclient: Sending on Socket/fallback
Jun 30 17:21:42 localhost dhclient: DHCPRELEASE on wlan0 to 10.0.1.1 port 67
Jun 30 17:21:42 localhost kernel: [ 624.129671] iwlwifi 0000:08:00.0: L1 Enabled; Disabling L0S
Jun 30 17:21:42 localhost kernel: [ 624.136425] iwlwifi 0000:08:00.0: Radio type=0x2-0x2-0x1
Jun 30 17:21:43 localhost kernel: [ 624.290321] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Jun 30 17:21:43 localhost kernel: [ 624.355364] iwlwifi 0000:08:00.0: L1 Enabled; Disabling L0S
Jun 30 17:21:43 localhost kernel: [ 624.362119] iwlwifi 0000:08:00.0: Radio type=0x2-0x2-0x1
Jun 30 17:21:43 localhost kernel: [ 624.500638] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Jun 30 17:21:43 localhost dhclient: Internet Systems Consortium DHCP Client 4.2.3-P2
Jun 30 17:21:43 localhost dhclient: Copyright 2004-2012 Internet Systems Consortium.
Jun 30 17:21:43 localhost dhclient: All rights reserved.
Jun 30 17:21:43 localhost dhclient: For info, please visit https://www.isc.org/software/dhcp/
Jun 30 17:21:43 localhost dhclient:
Jun 30 17:21:43 localhost dhclient: Listening on LPF/eth0/b8:70:f4:83:a4:3b
Jun 30 17:21:43 localhost dhclient: Sending on LPF/eth0/b8:70:f4:83:a4:3b
Jun 30 17:21:43 localhost dhclient: Sending on Socket/fallback
Jun 30 17:21:43 localhost dhclient: DHCPRELEASE on eth0 to 10.0.1.1 port 67
Jun 30 17:21:43 localhost kernel: [ 624.875063] r8169 0000:07:00.0: eth0: link down
Jun 30 17:21:43 localhost kernel: [ 624.876536] ADDRCONF(NETDEV_UP): eth0: link is not ready
Jun 30 17:21:43 localhost kernel: [ 625.050344] r8169 0000:07:00.0: eth0: link down
Jun 30 17:21:43 localhost kernel: [ 625.050842] ADDRCONF(NETDEV_UP): eth0: link is not ready
Jun 30 17:21:43 localhost dhclient: Internet Systems Consortium DHCP Client 4.2.3-P2
Jun 30 17:21:43 localhost dhclient: Copyright 2004-2012 Internet Systems Consortium.
Jun 30 17:21:43 localhost dhclient: All rights reserved.
Jun 30 17:21:43 localhost dhclient: For info, please visit https://www.isc.org/software/dhcp/
Jun 30 17:21:43 localhost dhclient:
Jun 30 17:21:43 localhost dhclient: Listening on LPF/wlan0/bc:77:37:07:fd:96
Jun 30 17:21:43 localhost dhclient: Sending on LPF/wlan0/bc:77:37:07:fd:96
Jun 30 17:21:43 localhost dhclient: Sending on Socket/fallback
Jun 30 17:21:44 localhost dhclient: DHCPRELEASE on wlan0 to 10.0.1.1 port 67
Jun 30 17:21:44 localhost kernel: [ 625.278255] iwlwifi 0000:08:00.0: L1 Enabled; Disabling L0S
Jun 30 17:21:44 localhost kernel: [ 625.285000] iwlwifi 0000:08:00.0: Radio type=0x2-0x2-0x1
Jun 30 17:21:44 localhost kernel: [ 625.441983] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Jun 30 17:21:44 localhost kernel: [ 625.512578] iwlwifi 0000:08:00.0: L1 Enabled; Disabling L0S
Jun 30 17:21:44 localhost kernel: [ 625.519296] iwlwifi 0000:08:00.0: Radio type=0x2-0x2-0x1
Jun 30 17:21:44 localhost kernel: [ 625.672665] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Jun 30 17:21:46 localhost dhclient: Internet Systems Consortium DHCP Client 4.2.3-P2
Jun 30 17:21:46 localhost dhclient: Copyright 2004-2012 Internet Systems Consortium.
Jun 30 17:21:46 localhost dhclient: All rights reserved.
Jun 30 17:21:46 localhost dhclient: For info, please visit https://www.isc.org/software/dhcp/
Jun 30 17:21:46 localhost dhclient:
Jun 30 17:21:47 localhost dhclient: Listening on LPF/wlan0/bc:77:37:07:fd:96
Jun 30 17:21:47 localhost dhclient: Sending on LPF/wlan0/bc:77:37:07:fd:96
Jun 30 17:21:47 localhost dhclient: Sending on Socket/fallback
Jun 30 17:21:47 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
Jun 30 17:21:55 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
Jun 30 17:22:07 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
Jun 30 17:22:19 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 19
Jun 30 17:22:38 localhost dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
Jun 30 17:22:48 localhost dhclient: No DHCPOFFERS received.
Jun 30 17:22:48 localhost dhclient: No working leases in persistent database - sleeping.

Can't connect to wireless printer from Mac

I have 2 wireless printers. My Macs can connect to one, but can not find the other. My PCs can connect to both just find.
The printer I can't connect to is a Lexmark 4650. I'm running the install CD, but when it tries to find the printer, it doesn't find it,
so I can not complete the setup.

If you have the printers IP address open Terminal (Applications/Utilities) and at the prompt type: ping {printerIP}. You will get a reply or failure.
Network Printer Troubleshooting
WiFi Printer to WiFi Network - Connect
Try resetting the printing system.
OS X Mavericks: Reset the printing system Yosemite

Connecting multiple wireless printers

Similar Messages

Maybe you are looking for