G4 and wireless
Hi, all. I have a PowerMac G4 that I would like to use on my wireless network at home (I have a PC laptop I currently use on it). I've not very tech-savvy, so I'm not sure what kind of wireless card I need. Here are some specs:
Processor: 1 GHz Power PC G4, 1 MB L3 cache
Memory: 1.75 GB DDR SDRAM
Machine Model: PowerMac3,6
Number Of CPUs: 1
CPU Speed: 1 GHz
Bus Speed: 133 MHz
I tried an AirPort card, but it wouldn't fit (it was too wide). Would an AirPort Extreme card work instead? Or, is there some kind of USB device I could plug into a port and use (without installing anything inside)?
Thanks, all,
Kevin
Would an AirPort Extreme card work instead?
A PowerMac G4 with a FireWire 800 port has an AirPort Extreme slot.
(39900)
Similar Messages
-
How do i use my HP 4500 as USB and wireless?
Hi
I have my printer set up as wireless. This is fine for mobile devices like my tablets but only 50% of the time it works from my Windows 8.1 PC.
How do i change so it works for USB on PC and wireless for tablet etc?
I tried to resinstall set up cd as USB connection but everytime i keep getting errors and being asked to reinstall disk. It didnt work, so i set it back to wireless only
Please help asap!
Many thanksWelcome to the HP Community @Sav1 ,
I understand you are looking to connect your Windows 8.1 computer to your Envy 4500 via USB connection, and keep the printer on the wireless network for your other devices. This method should work for you however, you may have better luck downloading and installing the printer for the USB connection through the download on our website opposed to using the installation disk.
Click here for the drivers, and run through the USB installation set up. Remember to only plug in the USB cable when the install asks you to connect it: HP Support - Software and Driver Downloads
If you run in to any issues or errors, let me know what they are saying exactly and I will do my best to help you through them!
Good luck
R a i n b o w 7000I work on behalf of HP
Click the “Kudos Thumbs Up" at the bottom of this post to say
“Thanks” for helping!
Click “Accept as Solution” if you feel my post solved your issue, it will help others find the solution! -
Wired and Wireless sometimes work (mostly not) after update.
So I have an issue with my network connection. It sometimes works, sometimes doesn't (mostly doesn't). This is for both wired and wireless. This started to happen a couple of days ago after an update. I had not updated for about a month prior. Prior to the update I used WICD and it worked just fine with no problems. I have no exotic hardware (ipw2200 using its firmware, dell xps gen2 notebook) and I set up everything about 6 months ago based on all the wikis. I have a dlink dir-825 router. Both wired and wireless connections work in windows every boot so it's not hardware.
I've included as much info as possible... sorry for the length.
Things I've tried:
Removing the ! from the INTERFACES=(!eth0 !eth1) in rc.conf
Removing netfs from the daemons
all the hostnames match in hosts and rc.conf
Here is my rc.conf
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="en_US.utf8"
HARDWARECLOCK="local"
USEDIRECTISA="no"
TIMEZONE="America/New_York"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(acpi-cpufreq cpufreq_ondemand cpufreq_powersave cpufreq_conservative cpufreq_userspace fuse ipw2200)
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="yes"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="stupendiousman"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
# DHCP: Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
INTERFACES=(!eth0 !eth1)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need 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 now 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
DAEMONS=(syslog-ng hal cpufreq wicd alsa crond fam bluetooth)
Here is my hosts
# /etc/hosts: static lookup table for host names
#<ip-address> <hostname.domain.org> <hostname>
127.0.0.1 localhost.localdomain localhost stupendiousman
# End of file
Here is my mkinitcpio.conf
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES="piix ide_disk reiserfs"
MODULES=""
CRYPTO_MODULES="aes_generic aes_i586 dm_crypt xts"
# BINARIES
# This setting includes, into the CPIO image, and additional
# binaries a given user may wish. This is run first, so may
# be used to override the actual binaries used in a given hook.
# (Existing files are NOT overwritten is already added)
# BINARIES are dependancy parsed, so you may safely ignore libraries
BINARIES=""
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in anyway. This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options,
# like so:
# FILES="/etc/modprobe.conf"
FILES=""
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'modload' may be used in place of 'udev', but is not recommended
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
# This setup specifies all modules in the MODULES setting above.
# No raid, lvm2, or encrypted root is needed.
# HOOKS="base"
# This setup will autodetect all modules for your system and should
# work as a sane default
# HOOKS="base udev autodetect pata scsi sata filesystems"
# This is identical to the above, except the old ide subsystem is
# used for IDE devices instead of the new pata subsystem.
# HOOKS="base udev autodetect ide scsi sata filesystems"
# This setup will generate a 'full' image which supports most systems.
# No autodetection is done.
# HOOKS="base udev pata scsi sata usb filesystems"
# This setup assembles an pata raid array with an encrypted root FS.
# Note: See 'mkinitcpio -H raid' for more information on raid devices.
# HOOKS="base udev pata raid encrypt filesystems"
# This setup loads an lvm2 volume group on a usb device.
# HOOKS="base udev usb lvm2 filesystems"
HOOKS="base udev autodetect pata scsi sata encrypt lvm2 resume filesystems firmware"
lspci
00:00.0 Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller (rev 03)
00:01.0 PCI bridge: Intel Corporation Mobile 915GM/PM Express PCI Express Root Port (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 (rev 03)
00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev d3)
00:1e.2 Multimedia audio controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller (rev 03)
00:1e.3 Modem: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Modem Controller (rev 03)
00:1f.0 ISA bridge: Intel Corporation 82801FBM (ICH6M) LPC Interface Bridge (rev 03)
00:1f.2 IDE interface: Intel Corporation 82801FBM (ICH6M) SATA Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus Controller (rev 03)
01:00.0 VGA compatible controller: nVidia Corporation NV41.9 [GeForce Go 6800 Ultra] (rev a2)
03:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5705M_2 Gigabit Ethernet (rev 03)
03:01.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev b3)
03:01.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C552 IEEE 1394 Controller (rev 08)
03:01.2 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 17)
03:03.0 Network controller: Intel Corporation PRO/Wireless 2915ABG [Calexico2] Network Connection (rev 05)
ifconfig returns:
[rick@stupendiousman ~]$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:12:F0:3E:CA:66
inet6 addr: fe80::212:f0ff:fe3e:ca66/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:25 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:4454 (4.3 Kb)
Interrupt:17 Base address:0x6000 Memory:dcfef000-dcfeffff
eth1 Link encap:Ethernet HWaddr 00:11:43:72:B5:96
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:18
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:280 (280.0 b) TX bytes:280 (280.0 b)
If I do a iwlist scan I get:
[rick@stupendiousman ~]$ iwlist scan
lo Interface doesn't support scanning.
eth0 No scan results
eth1 Interface doesn't support scanning.
pan0 Interface doesn't support scanning.
Here is a portion of my /var/log/wicd/wicd.log
2009/08/15 09:19:29 :: ---------------------------
2009/08/15 09:19:29 :: wicd initializing...
2009/08/15 09:19:29 :: ---------------------------
2009/08/15 09:19:29 :: wicd is version 1.6.2 436
2009/08/15 09:19:29 :: setting backend to external
2009/08/15 09:19:29 :: trying to load backend external
2009/08/15 09:19:30 :: successfully loaded backend external
2009/08/15 09:19:30 :: trying to load backend external
2009/08/15 09:19:30 :: successfully loaded backend external
2009/08/15 09:19:30 :: Automatically detected wireless interface eth0
2009/08/15 09:19:30 :: setting wireless interface eth1
2009/08/15 09:19:30 :: automatically detected wired interface eth1
2009/08/15 09:19:30 :: setting wired interface eth0
2009/08/15 09:19:30 :: setting wpa driver wext
2009/08/15 09:19:30 :: setting use global dns to False
2009/08/15 09:19:30 :: setting global dns
2009/08/15 09:19:30 :: global dns servers are None None None
2009/08/15 09:19:30 :: domain is None
2009/08/15 09:19:30 :: search domain is None
2009/08/15 09:19:30 :: setting automatically reconnect when connection drops True
2009/08/15 09:19:30 :: Setting dhcp client to 0
2009/08/15 09:19:30 :: Wireless configuration file found...
2009/08/15 09:19:30 :: Wired configuration file found...
2009/08/15 09:19:30 :: chmoding configuration files 0600...
2009/08/15 09:19:30 :: chowning configuration files root:root...
2009/08/15 09:19:30 :: Using wireless interface...eth1
2009/08/15 09:19:30 :: Using wired interface...eth0
2009/08/15 09:19:36 :: Autoconnecting...
2009/08/15 09:19:39 :: Attempting to autoconnect with wired interface...
2009/08/15 09:19:39 :: Putting interface down
2009/08/15 09:19:39 :: Releasing DHCP leases...
2009/08/15 09:19:39 :: Setting false IP...
2009/08/15 09:19:39 :: Flushing the routing table...
2009/08/15 09:19:39 :: Putting interface up...
2009/08/15 09:19:39 :: Running DHCP
2009/08/15 09:19:39 :: dhcpcd: version 5.0.6 starting
2009/08/15 09:19:39 ::
2009/08/15 09:19:39 :: dhcpcd: eth0: broadcasting for a lease
2009/08/15 09:19:39 ::
2009/08/15 09:20:09 :: dhcpcd: timed out
2009/08/15 09:20:09 ::
2009/08/15 09:20:09 :: DHCP connection failed
2009/08/15 09:20:09 :: exiting connection thread
2009/08/15 09:20:11 :: No wired connection present, attempting to autoconnect to wireless network
2009/08/15 09:20:11 :: Unable to autoconnect, you'll have to manually connect
2009/08/15 09:20:11 :: Sending connection attempt result dhcp_failed
2009/08/15 09:21:03 :: trying to load backend ioctl
2009/08/15 09:21:03 :: WARNING: python-iwscan not found, falling back to using iwlist scan.
2009/08/15 09:21:03 :: WARNING: python-wpactrl not found, falling back to using wpa_cli.
2009/08/15 09:21:03 :: trying to load backend external
2009/08/15 09:21:10 :: Putting interface down
2009/08/15 09:21:10 :: Releasing DHCP leases...
2009/08/15 09:21:10 :: Setting false IP...
2009/08/15 09:21:10 :: Flushing the routing table...
2009/08/15 09:21:10 :: Putting interface up...
2009/08/15 09:21:10 :: Running DHCP
2009/08/15 09:21:10 :: dhcpcd: version 5.0.6 starting
2009/08/15 09:21:10 ::
2009/08/15 09:21:10 :: dhcpcd: eth0: broadcasting for a lease
2009/08/15 09:21:10 ::
2009/08/15 09:21:40 :: dhcpcd: timed out
2009/08/15 09:21:40 ::
2009/08/15 09:21:40 :: DHCP connection failed
2009/08/15 09:21:40 :: exiting connection thread
2009/08/15 09:21:40 :: Sending connection attempt result dhcp_failed
2009/08/15 09:22:28 :: Putting interface down
2009/08/15 09:22:28 :: Releasing DHCP leases...
2009/08/15 09:22:28 :: Setting false IP...
2009/08/15 09:22:28 :: Flushing the routing table...
2009/08/15 09:22:28 :: Putting interface up...
2009/08/15 09:22:28 :: Running DHCP
2009/08/15 09:22:28 :: dhcpcd: version 5.0.6 starting
2009/08/15 09:22:28 ::
2009/08/15 09:22:28 :: dhcpcd: eth0: broadcasting for a lease
2009/08/15 09:22:28 ::
2009/08/15 09:22:58 :: dhcpcd: timed out
2009/08/15 09:22:58 ::
2009/08/15 09:22:58 :: DHCP connection failed
2009/08/15 09:22:58 :: exiting connection thread
2009/08/15 09:22:58 :: Sending connection attempt result dhcp_failed
2009/08/15 09:23:17 :: Daemon going down, killing wicd-monitor...
2009/08/15 09:23:17 :: Removing PID file...
2009/08/15 09:23:17 :: Shutting down...
2009/08/15 13:16:59 :: ---------------------------
2009/08/15 13:16:59 :: wicd initializing...
2009/08/15 13:16:59 :: ---------------------------
2009/08/15 13:16:59 :: wicd is version 1.6.2 436
2009/08/15 13:16:59 :: setting backend to external
2009/08/15 13:16:59 :: trying to load backend external
2009/08/15 13:17:00 :: successfully loaded backend external
2009/08/15 13:17:00 :: trying to load backend external
2009/08/15 13:17:00 :: successfully loaded backend external
2009/08/15 13:17:00 :: Automatically detected wireless interface eth0
2009/08/15 13:17:00 :: setting wireless interface eth1
2009/08/15 13:17:00 :: automatically detected wired interface eth1
2009/08/15 13:17:00 :: setting wired interface eth0
2009/08/15 13:17:00 :: setting wpa driver wext
2009/08/15 13:17:00 :: setting use global dns to False
2009/08/15 13:17:00 :: setting global dns
2009/08/15 13:17:00 :: global dns servers are None None None
2009/08/15 13:17:00 :: domain is None
2009/08/15 13:17:00 :: search domain is None
2009/08/15 13:17:00 :: setting automatically reconnect when connection drops True
2009/08/15 13:17:00 :: Setting dhcp client to 0
2009/08/15 13:17:00 :: Wireless configuration file found...
2009/08/15 13:17:00 :: Wired configuration file found...
2009/08/15 13:17:00 :: chmoding configuration files 0600...
2009/08/15 13:17:00 :: chowning configuration files root:root...
2009/08/15 13:17:00 :: Using wireless interface...eth1
2009/08/15 13:17:00 :: Using wired interface...eth0
2009/08/15 13:17:06 :: Autoconnecting...
2009/08/15 13:17:09 :: Attempting to autoconnect with wired interface...
2009/08/15 13:17:09 :: Putting interface down
2009/08/15 13:17:09 :: Releasing DHCP leases...
2009/08/15 13:17:09 :: Setting false IP...
2009/08/15 13:17:09 :: Flushing the routing table...
2009/08/15 13:17:09 :: Putting interface up...
2009/08/15 13:17:09 :: Running DHCP
2009/08/15 13:17:09 :: dhcpcd: version 5.0.6 starting
2009/08/15 13:17:09 ::
2009/08/15 13:17:09 :: dhcpcd: eth0: broadcasting for a lease
2009/08/15 13:17:09 ::
2009/08/15 13:17:39 :: dhcpcd: timed out
2009/08/15 13:17:39 ::
2009/08/15 13:17:39 :: DHCP connection failed
2009/08/15 13:17:39 :: exiting connection thread
2009/08/15 13:17:41 :: No wired connection present, attempting to autoconnect to wireless network
2009/08/15 13:17:41 :: Unable to autoconnect, you'll have to manually connect
2009/08/15 13:17:41 :: Sending connection attempt result dhcp_failed
2009/08/15 13:18:10 :: Daemon going down, killing wicd-monitor...
2009/08/15 13:18:10 :: Removing PID file...
2009/08/15 13:18:10 :: Shutting down...
2009/08/15 13:19:01 :: ---------------------------
2009/08/15 13:19:01 :: wicd initializing...
2009/08/15 13:19:01 :: ---------------------------
2009/08/15 13:19:01 :: wicd is version 1.6.2 436
2009/08/15 13:19:01 :: setting backend to external
2009/08/15 13:19:01 :: trying to load backend external
2009/08/15 13:19:02 :: successfully loaded backend external
2009/08/15 13:19:02 :: trying to load backend external
2009/08/15 13:19:02 :: successfully loaded backend external
2009/08/15 13:19:02 :: Automatically detected wireless interface eth0
2009/08/15 13:19:02 :: setting wireless interface eth1
2009/08/15 13:19:02 :: automatically detected wired interface eth1
2009/08/15 13:19:02 :: setting wired interface eth0
2009/08/15 13:19:02 :: setting wpa driver wext
2009/08/15 13:19:02 :: setting use global dns to False
2009/08/15 13:19:02 :: setting global dns
2009/08/15 13:19:02 :: global dns servers are None None None
2009/08/15 13:19:02 :: domain is None
2009/08/15 13:19:02 :: search domain is None
2009/08/15 13:19:02 :: setting automatically reconnect when connection drops True
2009/08/15 13:19:02 :: Setting dhcp client to 0
2009/08/15 13:19:02 :: Wireless configuration file found...
2009/08/15 13:19:02 :: Wired configuration file found...
2009/08/15 13:19:02 :: chmoding configuration files 0600...
2009/08/15 13:19:02 :: chowning configuration files root:root...
2009/08/15 13:19:02 :: Using wireless interface...eth1
2009/08/15 13:19:02 :: Using wired interface...eth0
2009/08/15 13:19:08 :: Autoconnecting...
2009/08/15 13:19:11 :: Attempting to autoconnect with wired interface...
2009/08/15 13:19:11 :: Putting interface down
2009/08/15 13:19:11 :: Releasing DHCP leases...
2009/08/15 13:19:11 :: Setting false IP...
2009/08/15 13:19:11 :: Flushing the routing table...
2009/08/15 13:19:11 :: Putting interface up...
2009/08/15 13:19:11 :: Running DHCP
2009/08/15 13:19:11 :: dhcpcd: version 5.0.6 starting
2009/08/15 13:19:11 ::
2009/08/15 13:19:11 :: dhcpcd: eth0: broadcasting for a lease
2009/08/15 13:19:11 ::
2009/08/15 13:19:41 :: dhcpcd: timed out
2009/08/15 13:19:41 ::
2009/08/15 13:19:41 :: DHCP connection failed
2009/08/15 13:19:41 :: exiting connection thread
2009/08/15 13:19:43 :: No wired connection present, attempting to autoconnect to wireless network
2009/08/15 13:19:43 :: Unable to autoconnect, you'll have to manually connect
2009/08/15 13:19:43 :: Sending connection attempt result dhcp_failed
2009/08/15 13:30:36 :: Daemon going down, killing wicd-monitor...
2009/08/15 13:30:36 :: Removing PID file...
2009/08/15 13:30:36 :: Shutting down...
2009/08/15 13:31:29 :: ---------------------------
2009/08/15 13:31:29 :: wicd initializing...
2009/08/15 13:31:29 :: ---------------------------
2009/08/15 13:31:29 :: wicd is version 1.6.2 436
2009/08/15 13:31:29 :: setting backend to external
2009/08/15 13:31:29 :: trying to load backend external
2009/08/15 13:31:30 :: successfully loaded backend external
2009/08/15 13:31:30 :: trying to load backend external
2009/08/15 13:31:30 :: successfully loaded backend external
2009/08/15 13:31:30 :: Automatically detected wireless interface eth0
2009/08/15 13:31:30 :: setting wireless interface eth1
2009/08/15 13:31:30 :: automatically detected wired interface eth1
2009/08/15 13:31:30 :: setting wired interface eth0
2009/08/15 13:31:30 :: setting wpa driver wext
2009/08/15 13:31:30 :: setting use global dns to False
2009/08/15 13:31:30 :: setting global dns
2009/08/15 13:31:30 :: global dns servers are None None None
2009/08/15 13:31:30 :: domain is None
2009/08/15 13:31:30 :: search domain is None
2009/08/15 13:31:30 :: setting automatically reconnect when connection drops True
2009/08/15 13:31:30 :: Setting dhcp client to 0
2009/08/15 13:31:30 :: Wireless configuration file found...
2009/08/15 13:31:30 :: Wired configuration file found...
2009/08/15 13:31:30 :: chmoding configuration files 0600...
2009/08/15 13:31:30 :: chowning configuration files root:root...
2009/08/15 13:31:30 :: Using wireless interface...eth1
2009/08/15 13:31:30 :: Using wired interface...eth0
2009/08/15 13:31:37 :: Autoconnecting...
2009/08/15 13:31:39 :: Attempting to autoconnect with wired interface...
2009/08/15 13:31:39 :: Putting interface down
2009/08/15 13:31:39 :: Releasing DHCP leases...
2009/08/15 13:31:39 :: Setting false IP...
2009/08/15 13:31:39 :: Flushing the routing table...
2009/08/15 13:31:39 :: Putting interface up...
2009/08/15 13:31:39 :: Running DHCP
2009/08/15 13:31:39 :: dhcpcd: version 5.0.6 starting
2009/08/15 13:31:39 ::
2009/08/15 13:31:40 :: dhcpcd: eth0: broadcasting for a lease
2009/08/15 13:31:40 ::
2009/08/15 13:32:09 :: dhcpcd: timed out
2009/08/15 13:32:09 ::
2009/08/15 13:32:09 :: DHCP connection failed
2009/08/15 13:32:09 :: exiting connection thread
2009/08/15 13:32:12 :: No wired connection present, attempting to autoconnect to wireless network
2009/08/15 13:32:12 :: Unable to autoconnect, you'll have to manually connect
2009/08/15 13:32:12 :: Sending connection attempt result dhcp_failed
2009/08/15 13:38:00 :: Daemon going down, killing wicd-monitor...
2009/08/15 13:38:00 :: Removing PID file...
2009/08/15 13:38:00 :: Shutting down...
2009/08/15 13:39:19 :: ---------------------------
2009/08/15 13:39:19 :: wicd initializing...
2009/08/15 13:39:19 :: ---------------------------
2009/08/15 13:39:19 :: wicd is version 1.6.2 436
2009/08/15 13:39:19 :: setting backend to external
2009/08/15 13:39:19 :: trying to load backend external
2009/08/15 13:39:20 :: successfully loaded backend external
2009/08/15 13:39:20 :: trying to load backend external
2009/08/15 13:39:20 :: successfully loaded backend external
2009/08/15 13:39:20 :: Automatically detected wireless interface eth0
2009/08/15 13:39:20 :: setting wireless interface eth1
2009/08/15 13:39:20 :: automatically detected wired interface eth1
2009/08/15 13:39:20 :: setting wired interface eth0
2009/08/15 13:39:20 :: setting wpa driver wext
2009/08/15 13:39:20 :: setting use global dns to False
2009/08/15 13:39:20 :: setting global dns
2009/08/15 13:39:20 :: global dns servers are None None None
2009/08/15 13:39:20 :: domain is None
2009/08/15 13:39:20 :: search domain is None
2009/08/15 13:39:20 :: setting automatically reconnect when connection drops True
2009/08/15 13:39:20 :: Setting dhcp client to 0
2009/08/15 13:39:20 :: Wireless configuration file found...
2009/08/15 13:39:20 :: Wired configuration file found...
2009/08/15 13:39:20 :: chmoding configuration files 0600...
2009/08/15 13:39:20 :: chowning configuration files root:root...
2009/08/15 13:39:20 :: Using wireless interface...eth1
2009/08/15 13:39:20 :: Using wired interface...eth0
2009/08/15 13:39:27 :: Autoconnecting...
2009/08/15 13:39:29 :: Attempting to autoconnect with wired interface...
2009/08/15 13:39:29 :: Putting interface down
2009/08/15 13:39:29 :: Releasing DHCP leases...
2009/08/15 13:39:29 :: Setting false IP...
2009/08/15 13:39:29 :: Flushing the routing table...
2009/08/15 13:39:29 :: Putting interface up...
2009/08/15 13:39:29 :: Running DHCP
2009/08/15 13:39:29 :: dhcpcd: version 5.0.6 starting
2009/08/15 13:39:29 ::
2009/08/15 13:39:30 :: dhcpcd: eth0: broadcasting for a lease
2009/08/15 13:39:30 ::
2009/08/15 13:39:59 :: dhcpcd: timed out
2009/08/15 13:39:59 ::
2009/08/15 13:39:59 :: DHCP connection failed
2009/08/15 13:39:59 :: exiting connection thread
2009/08/15 13:40:02 :: No wired connection present, attempting to autoconnect to wireless network
2009/08/15 13:40:02 :: Unable to autoconnect, you'll have to manually connect
2009/08/15 13:40:02 :: Sending connection attempt result dhcp_failed
2009/08/15 13:45:10 :: Daemon going down, killing wicd-monitor...
2009/08/15 13:45:10 :: Removing PID file...
2009/08/15 13:45:10 :: Shutting down...
2009/08/15 13:46:13 :: ---------------------------
2009/08/15 13:46:13 :: wicd initializing...
2009/08/15 13:46:13 :: ---------------------------
2009/08/15 13:46:13 :: wicd is version 1.6.2 436
2009/08/15 13:46:13 :: setting backend to external
2009/08/15 13:46:13 :: trying to load backend external
2009/08/15 13:46:14 :: successfully loaded backend external
2009/08/15 13:46:14 :: trying to load backend external
2009/08/15 13:46:14 :: successfully loaded backend external
2009/08/15 13:46:14 :: Automatically detected wireless interface eth1
2009/08/15 13:46:14 :: setting wireless interface eth1
2009/08/15 13:46:14 :: automatically detected wired interface eth0
2009/08/15 13:46:14 :: setting wired interface eth0
2009/08/15 13:46:14 :: setting wpa driver wext
2009/08/15 13:46:14 :: setting use global dns to False
2009/08/15 13:46:14 :: setting global dns
2009/08/15 13:46:14 :: global dns servers are None None None
2009/08/15 13:46:14 :: domain is None
2009/08/15 13:46:14 :: search domain is None
2009/08/15 13:46:14 :: setting automatically reconnect when connection drops True
2009/08/15 13:46:14 :: Setting dhcp client to 0
2009/08/15 13:46:14 :: Wireless configuration file found...
2009/08/15 13:46:14 :: Wired configuration file found...
2009/08/15 13:46:14 :: chmoding configuration files 0600...
2009/08/15 13:46:14 :: chowning configuration files root:root...
2009/08/15 13:46:14 :: Using wireless interface...eth1
2009/08/15 13:46:14 :: Using wired interface...eth0
2009/08/15 13:46:20 :: Autoconnecting...
2009/08/15 13:46:22 :: No wired connection present, attempting to autoconnect to wireless network
2009/08/15 13:46:22 :: trying to automatically connect to...101
2009/08/15 13:46:22 :: Connecting to wireless network 101
2009/08/15 13:46:23 :: Putting interface down
2009/08/15 13:46:23 :: Releasing DHCP leases...
2009/08/15 13:46:23 :: Setting false IP...
2009/08/15 13:46:23 :: Stopping wpa_supplicant
2009/08/15 13:46:23 :: Flushing the routing table...
2009/08/15 13:46:23 :: Putting interface up...
2009/08/15 13:46:23 :: Generating psk...
2009/08/15 13:46:23 :: Attempting to authenticate...
2009/08/15 13:46:34 :: Running DHCP
2009/08/15 13:46:34 :: dhcpcd: version 5.0.6 starting
2009/08/15 13:46:34 ::
2009/08/15 13:46:34 :: dhcpcd: eth1: broadcasting for a lease
2009/08/15 13:46:34 ::
2009/08/15 13:46:35 :: dhcpcd: eth1: offered 192.168.0.183 from 192.168.0.1
2009/08/15 13:46:35 ::
2009/08/15 13:46:35 :: dhcpcd: eth1: acknowledged 192.168.0.183 from 192.168.0.1
2009/08/15 13:46:35 ::
2009/08/15 13:46:35 :: dhcpcd: eth1: checking for 192.168.0.183
2009/08/15 13:46:35 ::
2009/08/15 13:46:38 :: dhcpcd: eth1: carrier lost
2009/08/15 13:46:38 ::
2009/08/15 13:46:40 :: dhcpcd: eth1: carrier acquired
2009/08/15 13:46:40 ::
2009/08/15 13:46:40 :: dhcpcd: eth1: broadcasting for a lease
2009/08/15 13:46:40 ::
2009/08/15 13:46:45 :: dhcpcd: eth1: offered 192.168.0.183 from 192.168.0.1
2009/08/15 13:46:45 ::
2009/08/15 13:46:45 :: dhcpcd: eth1: acknowledged 192.168.0.183 from 192.168.0.1
2009/08/15 13:46:45 ::
2009/08/15 13:46:45 :: dhcpcd: eth1: checking for 192.168.0.183
2009/08/15 13:46:45 ::
2009/08/15 13:46:51 :: dhcpcd: eth1: leased 192.168.0.183 for 86400 seconds
2009/08/15 13:46:51 ::
2009/08/15 13:46:51 :: dhcpcd: forking to background
2009/08/15 13:46:51 ::
2009/08/15 13:46:51 ::
2009/08/15 13:46:51 :: DHCP connection successful
2009/08/15 13:46:51 :: Connecting thread exiting.
2009/08/15 13:46:55 :: Sending connection attempt result Success
2009/08/15 13:48:50 :: Putting interface down
2009/08/15 13:48:50 :: Releasing DHCP leases...
2009/08/15 13:48:50 :: Setting false IP...
2009/08/15 13:48:51 :: Flushing the routing table...
2009/08/15 13:48:51 :: Putting interface up...
2009/08/15 13:48:51 :: Running DHCP
2009/08/15 13:48:51 :: dhcpcd: version 5.0.6 starting
2009/08/15 13:48:51 ::
2009/08/15 13:48:51 :: dhcpcd: eth0: broadcasting for a lease
2009/08/15 13:48:51 ::
2009/08/15 13:48:51 :: dhcpcd: eth0: carrier lost
2009/08/15 13:48:51 ::
2009/08/15 13:48:53 :: dhcpcd: eth0: carrier acquired
2009/08/15 13:48:53 ::
2009/08/15 13:48:53 :: dhcpcd: eth0: broadcasting for a lease
2009/08/15 13:48:53 ::
2009/08/15 13:48:54 :: dhcpcd: eth0: offered 192.168.0.193 from 192.168.0.1
2009/08/15 13:48:54 ::
2009/08/15 13:48:54 :: dhcpcd: eth0: acknowledged 192.168.0.193 from 192.168.0.1
2009/08/15 13:48:54 ::
2009/08/15 13:48:54 :: dhcpcd: eth0: checking for 192.168.0.193
2009/08/15 13:48:54 ::
2009/08/15 13:49:00 :: dhcpcd: eth0: leased 192.168.0.193 for 86400 seconds
2009/08/15 13:49:00 ::
2009/08/15 13:49:00 :: dhcpcd: forking to background
2009/08/15 13:49:00 ::
2009/08/15 13:49:00 ::
2009/08/15 13:49:00 :: DHCP connection successful
2009/08/15 13:49:00 :: Connecting thread exiting.
2009/08/15 13:49:00 :: Sending connection attempt result Success
2009/08/15 13:53:46 :: Connecting to wireless network 102
2009/08/15 13:53:47 :: Putting interface down
2009/08/15 13:53:47 :: Releasing DHCP leases...
2009/08/15 13:53:47 :: Setting false IP...
2009/08/15 13:53:47 :: Stopping wpa_supplicant
2009/08/15 13:53:47 :: Flushing the routing table...
2009/08/15 13:53:47 :: Putting interface up...
2009/08/15 13:53:47 :: Generating psk...
2009/08/15 13:53:47 :: Attempting to authenticate...
2009/08/15 13:54:03 :: Running DHCP
2009/08/15 13:54:03 :: dhcpcd: version 5.0.6 starting
2009/08/15 13:54:03 ::
2009/08/15 13:54:03 :: dhcpcd: eth1: rebinding lease of 192.168.0.183
2009/08/15 13:54:03 ::
2009/08/15 13:54:03 :: dhcpcd: eth1: acknowledged 192.168.0.183 from 192.168.0.1
2009/08/15 13:54:03 ::
2009/08/15 13:54:03 :: dhcpcd: eth1: checking for 192.168.0.183
2009/08/15 13:54:03 ::
2009/08/15 13:54:05 :: dhcpcd: eth1: carrier lost
2009/08/15 13:54:05 ::
2009/08/15 13:54:06 :: dhcpcd: eth1: carrier acquired
2009/08/15 13:54:06 ::
2009/08/15 13:54:06 :: dhcpcd: eth1: rebinding lease of 192.168.0.183
2009/08/15 13:54:06 ::
2009/08/15 13:54:06 :: dhcpcd: eth1: acknowledged 192.168.0.183 from 192.168.0.1
2009/08/15 13:54:06 ::
2009/08/15 13:54:06 :: dhcpcd: eth1: checking for 192.168.0.183
2009/08/15 13:54:06 ::
2009/08/15 13:54:11 :: dhcpcd: eth1: leased 192.168.0.183 for 86400 seconds
2009/08/15 13:54:11 ::
2009/08/15 13:54:11 :: dhcpcd: forking to background
2009/08/15 13:54:11 ::
2009/08/15 13:54:11 ::
2009/08/15 13:54:11 :: DHCP connection successful
2009/08/15 13:54:11 :: Connecting thread exiting.
2009/08/15 13:54:11 :: Sending connection attempt result Success
2009/08/15 13:55:03 :: Daemon going down, killing wicd-monitor...
2009/08/15 13:55:03 :: Removing PID file...
2009/08/15 13:55:03 :: Shutting down...
2009/08/15 13:55:52 :: ---------------------------
2009/08/15 13:55:52 :: wicd initializing...
2009/08/15 13:55:52 :: ---------------------------
2009/08/15 13:55:52 :: wicd is version 1.6.2 436
2009/08/15 13:55:52 :: setting backend to external
2009/08/15 13:55:52 :: trying to load backend external
2009/08/15 13:55:53 :: successfully loaded backend external
2009/08/15 13:55:53 :: trying to load backend external
2009/08/15 13:55:53 :: successfully loaded backend external
2009/08/15 13:55:53 :: Automatically detected wireless interface eth0
2009/08/15 13:55:53 :: setting wireless interface eth1
2009/08/15 13:55:53 :: automatically detected wired interface eth1
2009/08/15 13:55:53 :: setting wired interface eth0
2009/08/15 13:55:53 :: setting wpa driver wext
2009/08/15 13:55:53 :: setting use global dns to False
2009/08/15 13:55:53 :: setting global dns
2009/08/15 13:55:53 :: global dns servers are None None None
2009/08/15 13:55:53 :: domain is None
2009/08/15 13:55:53 :: search domain is None
2009/08/15 13:55:53 :: setting automatically reconnect when connection drops True
2009/08/15 13:55:53 :: Setting dhcp client to 0
2009/08/15 13:55:53 :: Wireless configuration file found...
2009/08/15 13:55:53 :: Wired configuration file found...
2009/08/15 13:55:53 :: chmoding configuration files 0600...
2009/08/15 13:55:53 :: chowning configuration files root:root...
2009/08/15 13:55:53 :: Using wireless interface...eth1
2009/08/15 13:55:53 :: Using wired interface...eth0
2009/08/15 13:55:59 :: Autoconnecting...
2009/08/15 13:56:02 :: Attempting to autoconnect with wired interface...
2009/08/15 13:56:02 :: Putting interface down
2009/08/15 13:56:02 :: Releasing DHCP leases...
2009/08/15 13:56:02 :: Setting false IP...
2009/08/15 13:56:02 :: Flushing the routing table...
2009/08/15 13:56:02 :: Putting interface up...
2009/08/15 13:56:02 :: Running DHCP
2009/08/15 13:56:02 :: dhcpcd: version 5.0.6 starting
2009/08/15 13:56:02 ::
2009/08/15 13:56:02 :: dhcpcd: eth0: rebinding lease of 192.168.0.193
2009/08/15 13:56:02 ::
2009/08/15 13:56:12 :: dhcpcd: eth0: broadcasting for a lease
2009/08/15 13:56:12 ::
2009/08/15 13:56:32 :: dhcpcd: timed out
2009/08/15 13:56:32 ::
2009/08/15 13:56:32 :: DHCP connection failed
2009/08/15 13:56:32 :: exiting connection thread
2009/08/15 13:56:34 :: No wired connection present, attempting to autoconnect to wireless network
2009/08/15 13:56:34 :: Unable to autoconnect, you'll have to manually connect
2009/08/15 13:56:34 :: Sending connection attempt result dhcp_failed
2009/08/15 13:57:31 :: Daemon going down, killing wicd-monitor...
2009/08/15 13:57:31 :: Removing PID file...
2009/08/15 13:57:31 :: Shutting down...
2009/08/15 13:57:32 :: ---------------------------
2009/08/15 13:57:32 :: wicd initializing...
2009/08/15 13:57:32 :: ---------------------------
2009/08/15 13:57:32 :: wicd is version 1.6.2 436
2009/08/15 13:57:32 :: setting backend to external
2009/08/15 13:57:32 :: trying to load backend external
2009/08/15 13:57:32 :: successfully loaded backend external
2009/08/15 13:57:32 :: trying to load backend external
2009/08/15 13:57:32 :: successfully loaded backend external
2009/08/15 13:57:32 :: Automatically detected wireless interface eth0
2009/08/15 13:57:32 :: setting wireless interface eth1
2009/08/15 13:57:32 :: automatically detected wired interface eth1
2009/08/15 13:57:32 :: setting wired interface eth0
2009/08/15 13:57:32 :: setting wpa driver wext
2009/08/15 13:57:32 :: setting use global dns to False
2009/08/15 13:57:32 :: setting global dns
2009/08/15 13:57:32 :: global dns servers are None None None
2009/08/15 13:57:32 :: domain is None
2009/08/15 13:57:32 :: search domain is None
2009/08/15 13:57:32 :: setting automatically reconnect when connection drops True
2009/08/15 13:57:32 :: Setting dhcp client to 0
2009/08/15 13:57:32 :: Wireless configuration file found...
2009/08/15 13:57:32 :: Wired configuration file found...
2009/08/15 13:57:32 :: chmoding configuration files 0600...
2009/08/15 13:57:32 :: chowning configuration files root:root...
2009/08/15 13:57:32 :: Using wireless interface...eth1
2009/08/15 13:57:32 :: Using wired interface...eth0
2009/08/15 13:57:38 :: Autoconnecting...
2009/08/15 13:57:38 :: Putting interface down
2009/08/15 13:57:38 :: Attempting to autoconnect with wired interface...
2009/08/15 13:57:38 :: Releasing DHCP leases...
2009/08/15 13:57:38 :: Setting false IP...
2009/08/15 13:57:38 :: Flushing the routing table...
2009/08/15 13:57:38 :: Putting interface up...
2009/08/15 13:57:38 :: Running DHCP
2009/08/15 13:57:38 :: dhcpcd: version 5.0.6 starting
2009/08/15 13:57:38 ::
2009/08/15 13:57:38 :: dhcpcd: eth0: rebinding lease of 192.168.0.193
2009/08/15 13:57:38 ::
2009/08/15 13:57:48 :: dhcpcd: eth0: broadcasting for a lease
2009/08/15 13:57:48 ::
2009/08/15 13:58:08 :: dhcpcd: timed out
2009/08/15 13:58:08 ::
2009/08/15 13:58:08 :: DHCP connection failed
2009/08/15 13:58:08 :: exiting connection thread
2009/08/15 13:58:08 :: Sending connection attempt result dhcp_failed
2009/08/15 13:58:10 :: No wired connection present, attempting to autoconnect to wireless network
2009/08/15 13:58:10 :: Unable to autoconnect, you'll have to manually connect
2009/08/15 13:58:46 :: Putting interface down
2009/08/15 13:58:46 :: Releasing DHCP leases...
2009/08/15 13:58:46 :: Setting false IP...
2009/08/15 13:58:46 :: Flushing the routing table...
2009/08/15 13:58:46 :: Putting interface up...
2009/08/15 13:58:46 :: Running DHCP
2009/08/15 13:58:46 :: dhcpcd: version 5.0.6 starting
2009/08/15 13:58:46 ::
2009/08/15 13:58:46 :: dhcpcd: eth0: rebinding lease of 192.168.0.193
2009/08/15 13:58:46 ::
2009/08/15 13:58:56 :: dhcpcd: eth0: broadcasting for a lease
2009/08/15 13:58:56 ::
2009/08/15 13:59:16 :: dhcpcd: timed out
2009/08/15 13:59:16 ::
2009/08/15 13:59:16 :: DHCP connection failed
2009/08/15 13:59:16 :: exiting connection thread
2009/08/15 13:59:16 :: Sending connection attempt result dhcp_failed
2009/08/15 14:10:08 :: Daemon going down, killing wicd-monitor...
2009/08/15 14:10:08 :: Removing PID file...
2009/08/15 14:10:08 :: Shutting down...
2009/08/15 14:10:59 :: ---------------------------
2009/08/15 14:10:59 :: wicd initializing...
2009/08/15 14:10:59 :: ---------------------------
2009/08/15 14:10:59 :: wicd is version 1.6.2 436
2009/08/15 14:10:59 :: setting backend to external
2009/08/15 14:10:59 :: trying to load backend external
2009/08/15 14:10:59 :: successfully loaded backend external
2009/08/15 14:10:59 :: trying to load backend external
2009/08/15 14:10:59 :: successfully loaded backend external
2009/08/15 14:10:59 :: Automatically detected wireless interface eth0
2009/08/15 14:10:59 :: setting wireless interface eth1
2009/08/15 14:10:59 :: automatically detected wired interface eth1
2009/08/15 14:10:59 :: setting wired interface eth0
2009/08/15 14:10:59 :: setting wpa driver wext
2009/08/15 14:10:59 :: setting use global dns to False
2009/08/15 14:10:59 :: setting global dns
2009/08/15 14:10:59 :: global dns servers are None None None
2009/08/15 14:10:59 :: domain is None
2009/08/15 14:10:59 :: search domain is None
2009/08/15 14:10:59 :: setting automatically reconnect when connection drops True
2009/08/15 14:10:59 :: Setting dhcp client to 0
2009/08/15 14:10:59 :: Wireless configuration file found...
2009/08/15 14:10:59 :: Wired configuration file found...
2009/08/15 14:10:59 :: chmoding configuration files 0600...
2009/08/15 14:10:59 :: chowning configuration files root:root...
2009/08/15 14:10:59 :: Using wireless interface...eth1
2009/08/15 14:10:59 :: Using wired interface...eth0
2009/08/15 14:11:06 :: Autoconnecting...
2009/08/15 14:11:09 :: Attempting to autoconnect with wired interface...
2009/08/15 14:11:09 :: Putting interface down
2009/08/15 14:11:09 :: Releasing DHCP leases...
2009/08/15 14:11:09 :: Setting false IP...
2009/08/15 14:11:09 :: Flushing the routing table...
2009/08/15 14:11:09 :: Putting interface up...
2009/08/15 14:11:09 :: Running DHCP
2009/08/15 14:11:09 :: dhcpcd: version 5.0.6 starting
2009/08/15 14:11:09 ::
2009/08/15 14:11:09 :: dhcpcd: eth0: rebinding lease of 192.168.0.193
2009/08/15 14:11:09 ::
2009/08/15 14:11:19 :: dhcpcd: eth0: broadcasting for a lease
2009/08/15 14:11:19 ::
2009/08/15 14:11:39 :: dhcpcd: timed out
2009/08/15 14:11:39 ::
2009/08/15 14:11:39 :: DHCP connection failed
2009/08/15 14:11:39 :: exiting connection thread
2009/08/15 14:11:41 :: No wired connection present, attempting to autoconnect to wireless network
2009/08/15 14:11:41 :: Unable to autoconnect, you'll have to manually connect
2009/08/15 14:11:41 :: Sending connection attempt result dhcp_failed
2009/08/15 14:13:00 :: Daemon going down, killing wicd-monitor...
2009/08/15 14:13:00 :: Removing PID file...
2009/08/15 14:13:00 :: Shutting down...
2009/08/15 14:13:50 :: ---------------------------
2009/08/15 14:13:50 :: wicd initializing...
2009/08/15 14:13:50 :: ---------------------------
2009/08/15 14:13:50 :: wicd is version 1.6.2 436
2009/08/15 14:13:50 :: setting backend to external
2009/08/15 14:13:50 :: trying to load backend external
2009/08/15 14:13:50 :: successfully loaded backend external
2009/08/15 14:13:50 :: trying to load backend external
2009/08/15 14:13:50 :: successfully loaded backend external
2009/08/15 14:13:51 :: Automatically detected wireless interface eth1
2009/08/15 14:13:51 :: setting wireless interface eth1
2009/08/15 14:13:51 :: automatically detected wired interface eth0
2009/08/15 14:13:51 :: setting wired interface eth0
2009/08/15 14:13:51 :: setting wpa driver wext
2009/08/15 14:13:51 :: setting use global dns to False
2009/08/15 14:13:51 :: setting global dns
2009/08/15 14:13:51 :: global dns servers are None None None
2009/08/15 14:13:51 :: domain is None
2009/08/15 14:13:51 :: search domain is None
2009/08/15 14:13:51 :: setting automatically reconnect when connection drops True
2009/08/15 14:13:51 :: Setting dhcp client to 0
2009/08/15 14:13:51 :: Wireless configuration file found...
2009/08/15 14:13:51 :: Wired configuration file found...
2009/08/15 14:13:51 :: chmoding configuration files 0600...
2009/08/15 14:13:51 :: chowning configuration files root:root...
2009/08/15 14:13:51 :: Using wireless interface...eth1
2009/08/15 14:13:51 :: Using wired interface...eth0
2009/08/15 14:13:57 :: Autoconnecting...
2009/08/15 14:13:59 :: No wired connection present, attempting to autoconnect to wireless network
2009/08/15 14:14:00 :: trying to automatically connect to...101
2009/08/15 14:14:00 :: Connecting to wireless network 101
2009/08/15 14:14:00 :: Putting interface down
2009/08/15 14:14:00 :: Releasing DHCP leases...
2009/08/15 14:14:00 :: Setting false IP...
2009/08/15 14:14:00 :: Stopping wpa_supplicant
2009/08/15 14:14:00 :: Flushing the routing table...
2009/08/15 14:14:00 :: Putting interface up...
2009/08/15 14:14:00 :: Generating psk...
2009/08/15 14:14:01 :: Attempting to authenticate...
2009/08/15 14:14:11 :: Running DHCP
2009/08/15 14:14:11 :: dhcpcd: version 5.0.6 starting
2009/08/15 14:14:11 ::
2009/08/15 14:14:11 :: dhcpcd: eth1: rebinding lease of 192.168.0.183
2009/08/15 14:14:11 ::
2009/08/15 14:14:11 :: dhcpcd: eth1: acknowledged 192.168.0.183 from 192.168.0.1
2009/08/15 14:14:11 ::
2009/08/15 14:14:11 :: dhcpcd: eth1: checking for 192.168.0.183
2009/08/15 14:14:11 ::
2009/08/15 14:14:15 :: dhcpcd: eth1: leased 192.168.0.183 for 86400 seconds
2009/08/15 14:14:15 ::
2009/08/15 14:14:15 :: dhcpcd: forking to background
2009/08/15 14:14:15 ::
2009/08/15 14:14:15 ::
2009/08/15 14:14:15 :: DHCP connection successful
2009/08/15 14:14:15 :: Connecting thread exiting.
2009/08/15 14:14:17 :: Sending connection attempt result Success
2009/08/15 14:14:17 :: Autoconnecting...
2009/08/15 14:14:17 :: No wired connection present, attempting to autoconnect to wireless network
2009/08/15 14:14:17 :: trying to automatically connect to...102
2009/08/15 14:14:17 :: Connecting to wireless network 102
2009/08/15 14:14:17 :: Putting interface down
2009/08/15 14:14:17 :: Releasing DHCP leases...
2009/08/15 14:14:18 :: Setting false IP...
2009/08/15 14:14:18 :: Stopping wpa_supplicant
2009/08/15 14:14:18 :: Flushing the routing table...
2009/08/15 14:14:18 :: Putting interface up...
2009/08/15 14:14:18 :: Generating psk...
2009/08/15 14:14:18 :: Attempting to authenticate...
2009/08/15 14:14:19 :: Running DHCP
2009/08/15 14:14:19 :: dhcpcd: version 5.0.6 starting
2009/08/15 14:14:19 ::
2009/08/15 14:14:19 :: dhcpcd: eth1: rebinding lease of 192.168.0.183
2009/08/15 14:14:19 ::
2009/08/15 14:14:19 :: dhcpcd: eth1: acknowledged 192.168.0.183 from 192.168.0.1
2009/08/15 14:14:19 ::
2009/08/15 14:14:19 :: dhcpcd: eth1: checking for 192.168.0.183
2009/08/15 14:14:19 ::
2009/08/15 14:14:24 :: dhcpcd: eth1: leased 192.168.0.183 for 86400 seconds
2009/08/15 14:14:24 ::
2009/08/15 14:14:24 :: dhcpcd: forking to background
2009/08/15 14:14:24 ::
2009/08/15 14:14:24 ::
2009/08/15 14:14:24 :: DHCP connection successful
2009/08/15 14:14:24 :: Connecting thread exiting.
2009/08/15 14:14:29 :: Sending connection attempt result Success
2009/08/15 14:15:02 :: Daemon going down, killing wicd-monitor...
2009/08/15 14:15:02 :: Removing PID file...
2009/08/15 14:15:02 :: Shutting down...
2009/08/15 14:15:52 :: ---------------------------
2009/08/15 14:15:52 :: wicd initializing...
2009/08/15 14:15:52 :: ---------------------------
2009/08/15 14:15:52 :: wicd is version 1.6.2 436
2009/08/15 14:15:52 :: setting backend to external
2009/08/15 14:15:52 :: trying to load backend external
2009/08/15 14:15:52 :: successfully loaded backend external
2009/08/15 14:15:52 :: trying to load backend external
2009/08/15 14:15:52 :: successfully loaded backend external
2009/08/15 14:15:52 :: Automatically detected wireless interface eth0
2009/08/15 14:15:52 :: setting wireless interface eth1
2009/08/15 14:15:52 :: automatically detected wired interface eth1
2009/08/15 14:15:52 :: setting wired interface eth0
2009/08/15 14:15:52 :: setting wpa driver wext
2009/08/15 14:15:52 :: setting use global dns to False
2009/08/15 14:15:52 :: setting global dns
2009/08/15 14:15:52 :: global dns servers are None None None
2009/08/15 14:15:52 :: domain is None
2009/08/15 14:15:52 :: search domain is None
2009/08/15 14:15:52 :: setting automatically reconnect when connection drops True
2009/08/15 14:15:52 :: Setting dhcp client to 0
2009/08/15 14:15:52 :: Wireless configuration file found...
2009/08/15 14:15:52 :: Wired configuration file found...
2009/08/15 14:15:52 :: chmoding configuration files 0600...
2009/08/15 14:15:52 :: chowning configuration files root:root...
2009/08/15 14:15:52 :: Using wireless interface...eth1
2009/08/15 14:15:52 :: Using wired interface...eth0
2009/08/15 14:15:59 :: Autoconnecting...
2009/08/15 14:16:02 :: Attempting to autoconnect with wired interface...
2009/08/15 14:16:02 :: Putting interface down
2009/08/15 14:16:02 :: Releasing DHCP leases...
2009/08/15 14:16:02 :: Setting false IP...
2009/08/15 14:16:02 :: Flushing the routing table...
2009/08/15 14:16:02 :: Putting interface up...
2009/08/15 14:16:02 :: Running DHCP
2009/08/15 14:16:02 :: dhcpcd: version 5.0.6 starting
2009/08/15 14:16:02 ::
2009/08/15 14:16:02 :: dhcpcd: eth0: rebinding lease of 192.168.0.193
2009/08/15 14:16:02 ::
2009/08/15 14:16:12 :: dhcpcd: eth0: broadcasting for a lease
2009/08/15 14:16:12 ::
2009/08/15 14:16:32 :: dhcpcd: timed out
2009/08/15 14:16:32 ::
2009/08/15 14:16:32 :: DHCP connection failed
2009/08/15 14:16:32 :: exiting connection thread
2009/08/15 14:16:34 :: No wired connection present, attempting to autoconnect to wireless network
2009/08/15 14:16:34 :: Unable to autoconnect, you'll have to manually connect
2009/08/15 14:16:34 :: Sending connection attempt result dhcp_failed
2009/08/15 14:17:02 :: Daemon going down, killing wicd-monitor...
2009/08/15 14:17:02 :: Removing PID file...
2009/08/15 14:17:02 :: Shutting down...
2009/08/15 15:39:03 :: ---------------------------
2009/08/15 15:39:03 :: wicd initializing...
2009/08/15 15:39:03 :: ---------------------------
2009/08/15 15:39:03 :: wicd is version 1.6.2 436
2009/08/15 15:39:03 :: setting backend to external
2009/08/15 15:39:03 :: trying to load backend external
2009/08/15 15:39:03 :: successfully loaded backend external
2009/08/15 15:39:03 :: trying to load backend external
2009/08/15 15:39:03 :: successfully loaded backend external
2009/08/15 15:39:03 :: Automatically detected wireless interface eth0
2009/08/15 15:39:03 :: setting wireless interface eth1
2009/08/15 15:39:03 :: automatically detected wired interface eth1
2009/08/15 15:39:03 :: setting wired interface eth0
2009/08/15 15:39:03 :: setting wpa driver wext
2009/08/15 15:39:03 :: setting use global dns to False
2009/08/15 15:39:03 :: setting global dns
2009/08/15 15:39:03 :: global dns servers are None None None
2009/08/15 15:39:03 :: domain is None
2009/08/15 15:39:03 :: search domain is None
2009/08/15 15:39:03 :: setting automatically reconnect when connection drops True
2009/08/15 15:39:03 :: Setting dhcp client to 0
2009/08/15 15:39:03 :: Wireless configuration file found...
2009/08/15 15:39:03 :: Wired configuration file found...
2009/08/15 15:39:03 :: chmoding configuration files 0600...
2009/08/15 15:39:03 :: chowning configuration files root:root...
2009/08/15 15:39:03 :: Using wireless interface...eth1
2009/08/15 15:39:03 :: Using wired interface...eth0
2009/08/15 15:39:10 :: Autoconnecting...
2009/08/15 15:39:13 :: Attempting to autoconnect with wired interface...
2009/08/15 15:39:13 :: Putting interface down
2009/08/15 15:39:13 :: Releasing DHCP leases...
2009/08/15 15:39:13 :: Setting false IP...
2009/08/15 15:39:13 :: Flushing the routing table...
2009/08/15 15:39:13 :: Putting interface up...
2009/08/15 15:39:13 :: Running DHCP
2009/08/15 15:39:13 :: dhcpcd: version 5.0.6 starting
2009/08/15 15:39:13 ::
2009/08/15 15:39:13 :: dhcpcd: eth0: rebinding lease of 192.168.0.193
2009/08/15 15:39:13 ::
2009/08/15 15:39:23 :: dhcpcd: eth0: broadcasting for a lease
2009/08/15 15:39:23 ::
2009/08/15 15:39:43 :: dhcpcd: timed out
2009/08/15 15:39:43 ::
2009/08/15 15:39:43 :: DHCP connection failed
2009/08/15 15:39:43 :: exiting connection thread
2009/08/15 15:39:45 :: No wired connection present, attempting to autoconnect to wireless network
2009/08/15 15:39:45 :: Unable to autoconnect, you'll have to manually connect
2009/08/15 15:39:45 :: Sending connection attempt result dhcp_failed
2009/08/15 15:41:46 :: Daemon going down, killing wicd-monitor...
2009/08/15 15:41:46 :: Removing PID file...
2009/08/15 15:41:46 :: Shutting down...
2009/08/15 15:42:33 :: ---------------------------
2009/08/15 15:42:33 :: wicd initializing...
2009/08/15 15:42:33 :: ---------------------------
2009/08/15 15:42:33 :: wicd is version 1.6.2 436
2009/08/15 15:42:33 :: setting backend to external
2009/08/15 15:42:33 :: trying to load backend external
2009/08/15 15:42:33 :: successfully loaded backend external
2009/08/15 15:42:33 :: trying to load backend external
2009/08/15 15:42:33 :: successfully loaded backend external
2009/08/15 15:42:33 :: Automatically detected wireless interface eth0
2009/08/15 15:42:33 :: setting wireless interface eth1
2009/08/15 15:42:33 :: automatically detected wired interface eth1
2009/08/15 15:42:33 :: setting wired interface eth0
2009/08/15 15:42:33 :: setting wpa driver wext
2009/08/15 15:42:33 :: setting use global dns to False
2009/08/15 15:42:33 :: setting global dns
2009/08/15 15:42:33 :: global dns servers are None None None
2009/08/15 15:42:33 :: domain is None
2009/08/15 15:42:33 :: search domain is None
2009/08/15 15:42:33 :: setting automatically reconnect when connection drops True
2009/08/15 15:42:33 :: Setting dhcp client to 0
2009/08/15 15:42:33 :: Wireless configuration file found...
2009/08/15 15:42:33 :: Wired configuration file found...
2009/08/15 15:42:33 :: chmoding configuration files 0600...
2009/08/15 15:42:33 :: chowning configuration files root:root...
2009/08/15 15:42:33 :: Using wireless interface...eth1
2009/08/15 15:42:33 :: Using wired interface...eth0
2009/08/15 15:42:39 :: Autoconnecting...
2009/08/15 15:42:42 :: Attempting to autoconnect with wired interface...
2009/08/15 15:42:42 :: Putting interface down
2009/08/15 15:42:42 :: Releasing DHCP leases...
2009/08/15 15:42:42 :: Setting false IP...
2009/08/15 15:42:42 :: Flushing the routing table...
2009/08/15 15:42:42 :: Putting interface up...
2009/08/15 15:42:42 :: Running DHCP
2009/08/15 15:42:42 :: dhcpcd: version 5.0.6 starting
2009/08/15 15:42:42 ::
2009/08/15 15:42:42 :: dhcpcd: eth0: rebinding lease of 192.168.0.193
2009/08/15 15:42:42 ::
2009/08/15 15:42:52 :: dhcpcd: eth0: broadcasting for a lease
2009/08/15 15:42:52 ::
2009/08/15 15:43:12 :: dhcpcd: timed out
2009/08/15 15:43:12 ::
2009/08/15 15:43:12 :: DHCP connection failed
2009/08/15 15:43:12 :: exiting connection thread
2009/08/15 15:43:14 :: No wired connection present, attempting to autoconnect to wireless network
2009/08/15 15:43:14 :: Unable to autoconnect, you'll have to manually connect
2009/08/15 15:43:14 :: Sending connection attempt result dhcp_failed
2009/08/15 15:44:27 :: Daemon going down, killing wicd-monitor...
2009/08/15 15:44:27 :: Removing PID file...
2009/08/15 15:44:27 :: Shutting down...
2009/08/15 15:44:48 :: ---------------------------
2009/08/15 15:44:48 :: wicd initializing...
2009/08/15 15:44:48 :: ---------------------------
2009/08/15 15:44:48 :: wicd is version 1.6.2 436
2009/08/15 15:44:48 :: setting backend to external
2009/08/15 15:44:48 :: trying to load backend external
2009/08/15 15:44:48 :: successfully loaded backend external
2009/08/15 15:44:48 :: trying to load backend external
2009/08/15 15:44:48 :: successfully loaded backend external
2009/08/15 15:44:48 :: Automatically detected wireless interface eth0
2009/08/15 15:44:48 :: setting wireless interface eth1
2009/08/15 15:44:48 :: automatically detected wired interface eth1
2009/08/15 15:44:48 :: setting wired interface eth0
2009/08/15 15:44:48 :: setting wpa driver wext
2009/08/15 15:44:48 :: setting use global dns to False
2009/08/15 15:44:48 :: setting global dns
2009/08/15 15:44:48 :: global dns servers are None None None
2009/08/15 15:44:48 :: domain is None
2009/08/15 15:44:48 :: search domain is None
2009/08/15 15:44:48 :: setting automatically reconnect when connection drops True
2009/08/15 15:44:48 :: Setting dhcp client to 0
2009/08/15 15:44:48 :: Wireless configuration file found...
2009/08/15 15:44:48 :: Wired configuration file found...
2009/08/15 15:44:48 :: chmoding configuration files 0600...
2009/08/15 15:44:48 :: chowning configuration files root:root...
2009/08/15 15:44:48 :: Using wireless interface...eth1
2009/08/15 15:44:48 :: Using wired interface...eth0
2009/08/15 15:44:58 :: trying to load backend ioctl
2009/08/15 15:44:58 :: WARNING: python-iwscan not found, falling back to using iwlist scan.
2009/08/15 15:44:58 :: WARNING: python-wpactrl not found, falling back to using wpa_cli.
2009/08/15 15:44:58 :: trying to load backend external
2009/08/15 15:45:57 :: Autoconnecting...
2009/08/15 15:45:57 :: Putting interface down
2009/08/15 15:45:57 :: Attempting to autoconnect with wired interface...
2009/08/15 15:45:57 :: Releasing DHCP leases...
2009/08/15 15:45:57 :: Setting false IP...
2009/08/15 15:45:57 :: Flushing the routing table...
2009/08/15 15:45:57 :: Putting interface up...
2009/08/15 15:45:57 :: Running DHCP
2009/08/15 15:45:57 :: dhcpcd: version 5.0.6 starting
2009/08/15 15:45:57 ::
2009/08/15 15:45:57 :: dhcpcd: eth0: rebinding lease of 192.168.0.193
2009/08/15 15:45:57 ::
2009/08/15 15:46:07 :: dhcpcd: eth0: broadcasting for a lease
2009/08/15 15:46:07 ::
2009/08/15 15:46:27 :: dhcpcd: timed out
2009/08/15 15:46:27 ::
2009/08/15 15:46:27 :: DHCP connection failed
2009/08/15 15:46:27 :: exiting connection thread
2009/08/15 15:46:29 :: No wired connection present, attempting to autoconnect to wireless network
2009/08/15 15:46:29 :: Unable to autoconnect, you'll have to manually connect
2009/08/15 15:46:29 :: Sending connection attempt result dhcp_failedWas able to boot this weekend and did an update which updated the kernel. Rebooted and there was no network. Rebooted again and no network... rebooted again and... had network!? I tried changing wicd to use dhclient only and did the triple reboot test again and it didn't change anything... randomly working network... same with dhcpcd.
So it appears to be a dhcp timeout issue however it makes no sense because before the update a couple weeks ago it was working every time with no hiccup. Am I not providing enough information that will aid in anyone helping me figure this out? -
I have no mouse or keyboard. I have tried USB and wireless. Help?
How can I get back control of my commuter? Cursor floats with mouse, but no clicking. I have used USB and wireless mouses and keyboards. Keyboard will "wake" but no other function . 2011 iMac 27. what can I do?
These are the instructions:
http://support.apple.com/kb/PH3878?viewlocale=en_US
Where does the problem occur? What happens?
Ciao, -
New mac mini and wireless keyboard
how do I set up a new mac mini and wireless keyboard at the same time?
Since the Mac Mini does not come with a Monitor, Keyboard or Mouse those are needed when setting up a Mac Mini. I don't know what brand wireless KB you have or if that even matters.
I have an Apple wireless keyboard (bluetooth), Apple magic trackpad (bluetooth), and Dell DVI monitor. When I initially booted my new Mac Mini, the screen showed it searching for bluetooth devices. It found the keyboard first and then a few seconds later, the mouse. So, I had all devices to finish setup of the Mini. -
Been losing connection for magic mouse and wireless keyboard
When I have my MBP running Mavericks in clamshell mode, I lose connections to both magic mouse and apple wireless keyboard in clamshell mode. I've tried all the PRAM SCM, aluminum foil and paper tricks. What I then did was test what happens when I leave the MBP open rather than in clamshell mode and it appears to avoid losing connection, at least that is what I've concluded with Mavericks for now..... anyone else able to replicate this? Having to leave the MBP open is not ideal.
Barry, thanks, still not working. I've tried every thing I can think of or have read, what I'm concluding is that there is either a problem with Mavericks or something has changed on how bluetooth works in Mavericks. Did not have this problem for the last 4 years. I can reproduce the problem when I close the laptop. I had the Bluetooth and wireless card checked out and replaced about 3 weeks ago. Problem has continued.
-
Magic Mouse and Wireless Keyboard: Should charge off iMac
Apple, you've been shipping Bluetooth peripherals that require disposable batteries for years. It's time to design long-lasting rechargeable batteries into these devices.
Years ago I open-lettered the idea of designing Apple's BT devices with built-in rechargeable batteries. The basic idea consists of a USB cable that is used periodically to connect to the CPU and to the devices. The devices would have a red and green light that become visible when depleted or charged respectively. When the devices require a charge, the USB cable is connected to the iMac and then to the device. The USB cable is put away once the green light indicates a full charge.
No visual clutter, no batteries to dump into the landfill.
While I'm not a rabid environmentalist, the fact that Apple is speaking openly about it's accomplishments in this area (http://www.apple.com/macbookpro/environment.html), while at the same time shipping a Mac that requires disposable batteries is a bit of a letdown to this longtime Mac buyer (since 1986).
Throwaway batteries are unnecessary.
The technology exists to include a long life built-in rechargeable battery. A USB charging cable, used as described above, would not clutter Apple's design intentions for the new iMacs. Instead, it would strengthen Apple's Green Design goals.
Apple has had years to noodle out such a feature. In my opinion, there's no excuse for this oversight.Hi Chillspike. In response to your comment, +"Is one or two wires (keyboard & mouse) too much clutter for people?..."+
Not all of us have a lot of computer space. My iMac is on a small table along with my TV, cable box, DVD player, etc. I have a rats nest of wires in the back, including my internet receiver, USBs for my iPod, wireless keyboard, and wireless trackball, a backup hard drive, and my printer (I have to switch something else out in order to plug it in). I might sit on the edge of my bed and put the keyboard in my lap, although I usually stretch out in bed a few feet away to work.
I had a wired keyboard and trackball a while ago, and nearly pulled the computer off the table a couple of times as I was trying to get settled in! So going wireless is as much a matter of practicality for some of us, as your preference for hard wiring is for you. If you prefer being wired, I hope someone comes up with a product that meets your needs - and maybe by the time they do they will have the "bugs" worked out of this new one. -
How to set up WRT54GS so the wired and wireless connections both work?
I have a DSL line in to a Motorola modem.
The modem is connected to the WRT54GS with an ethernet cable.
When I connect my computers directly into the WRT54GS with an ethernet cable (there are four connection spots at the back of the box), I cannot go to the internet. I have 3 computers plugged in, but none of them connect via Ethernet..
Is there a setting on the router so that I can use the router for both wired and wireless connectivity?
Added info: I tried to connect directly from the computer to the modem, but again, got no connectivity. When I "chatted" with ATT, they told me the modem is set to "bridge", and that I could connect only one device. I don't want to change this setting because I want to use the router for the wireless capability. Besides which, I have more than one computer to connect to the internet.
How come I cannot just plug in and go?
My firmware version is v2.07.1.
I don't know how to find out what hardware version I have.
Other info is "DirectEthernet Connection, Speed: 100.0 Mbps, Signal Strength: Excellent, Status: Connected"
Also "1394 Connection 3, Speed: 400.0 Mbps, Status: Connected"
I don't know what that's for, but thought it might prove useful to those of you who are knowledgeable about such things.
Wireless is ok, but if I'm sitting right next to the router, I'd like to connect with Ethernet and take advantage of the better speed, etc.
Thanks in advance.Just click this link.
-
How to set up an integrated wired and wireless network
I have an iMac 17" 1GHz connected to a ethernet hub which in turn is connected to a DSL modem and from there to my ISP. I also have a MacBook Pro wirelessly connected to an AirPort Express; the AE is connected to the same ethernet hub through its ethernet port.
I can connect to the Internet wirelesly using the MacBook Pro, but I can not seem to connect to the iMac.
How can I keep the iMac wired and the MacBook Pro wireless, but see both on a network? The AE instructions don't seem to have an example for this kind of network.
Any help would be greatly appreciated!
Cheers,
Martin
MacBook Pro Mac OS X (10.4.6)
MacBook Pro Mac OS X (10.4.6)Martin,
As Frank said, you'll need a router with DHCP and NAT abilities (nearly all have this) connected to the modem.
But just in case your "ethernet hub" is actually a router, just re-configure the AE not to distribute IP addresses - AirPort Admin Utility - Network tab. Try that and let us know.
For minimal clutter, if you were DSL broadband instead of cable, you could sell the modem, sell the ethernet router, sell the Airport Express and buy a single Ethernet and Wireless DSL modem router - for less than the price of the AE. Some people like to keep the modem separate to make upgrades to the modem cheaper. My solution is to buy a decent modem in the first place, ie make sure it has ADSL2+. Almost all modem/routers do this now, even my ancient ones have firmware upgrades to offer this.
For minimal spend, you can pick up an Ethernet router for about $30. Just replace your ethernet hub with it. -
Wired and wireless computers on the same network?
Here’s the scenario: I’ve got Verizon FIOS which comes with a modem with four Ethernet ports. I have an Airport Extreme plugged into the modem. There are six macs in the house (three desktops and three laptops) and they can all connect wirelessly although the signal fades in the living room and in my son’s room. I decided to run an Ethernet cable from the modem to the G5 that is in the living room and another one to my son’s room. Everything works fine but the “wired” computers are now no longer on the same network.
(At first I thought it was neat: if I was near the G5 and the signal from the Airport Extreme was weak, I could just hop onto the G5’s network (which has “Internet sharing” via airport enabled) but it’s become a nuisance because we always seem to be needing to change from one network to another: The computer connected to the printers is on Airport Extreme so I can’t print from the G5 unless I change the settings; if we’re in the bedroom connected to the Internet via the AirPort Extreme, we can’t access our iTunes music from the G5 without switching networks.)
I don’t know if there is a solution but it seems there should be.
I’d like to have two computers hard-wired and have all of them be part of the same home network. Is that possible?The solution is simple. Configure the AirPort Extreme base station (AEBS) so that the option to distribute IP addresses is DISABLED.
This will disable the AEBS's DHCP server and NAT. The net effect will be that anything connected to the AEBS's WAN port (anything connected to Verizon's router's LAN ports like your Ethernet computers) on the same subnet as the AEBS's LAN and wireless clients. -
Hello Everyone, I just bought a HP Photosmart Premium All-in-One Printer - C309g but i find it very difficult to connect to it via BLUETOOTH and WIRELESS on my IPAD 3...i will be very greatfull if i'll get a solution as soon as possible. Thanks
Hi Tomiwa,
You cannot print from the iPad to that printer. AirPrint and Bluetooth are completely different.
There may be apps you can buy that will enable using that printer, but that is not an ideal solution.
That particular printer has had many bad reviews, and is unreasonably expensive for its features. Considering that you just bought the printer, as well as its lack of AirPrint, I suggest you return it and buy a printer that supports AirPrint. -
Itunes and wireless devices no longer show up in upper right corner of itunes window
Help! My Internet service was interupted last week and when it returned my iTunes and wireless devices no longer show up in upper right corner of the iTunes window. I finally figured out how to get both of my wireless devices to show up on the left hand column under devices, but nothing else shows up now in the upper right corner! I cannot for the life of me figure this one out and the tech manual is not helping at all. Help!
If you have the left-hand sidebar showing then that is where the store and your devices will show can be selected - if you press option-command-S if you are using a Mac, control-S on a PC, then the sidebar should be hidden and the store and device should go back to the top right. Is that what you mean ?
-
I am buying an iMac to AirPlay mirror on my big screen TV with AppleTV (2nd generation). But my TV is located far away from my iMac and I won't be able to use my magic mouse or wireless keyboard via bluetooth connection. I know I can use an app to simulate both mouse and keyboard, but I really need to use the actual devices.
I wish there was a way to pair them to my iPad or iPhone, via bluetooth, and control my iMac via network. It is a cheap solution, as I wouldn't need to buy any other device. I believe all these devices, without modifications, have enough technology to be able to work as I've imagined. The only need was to adapt the software.
Is there a solution simple as this one, or do I have to buy a Bluetooth extender in order to use my magic mouse and wireless keyboard? If so, which BT extender do you suggest and what is its range?
Thank you!If you are still under warranty, contact Apple to get it serviced. You can also visit an Apple Store or Authorized Apple Service Provider to get it looked at.
iPhone - Contact Support - Apple Support -
Sharing iTunes between wired and wireless Macs
Hi,
I have a Mac laptop connected wirelessly to an Airport Express -- which is wired to a desktop Mac Mini. I'm trying to share music but cannot. I've done all the proper settings in the iTunes preferences and the same in System Preferences -- I think -- on both computers, but on neither computer is anything showing in the Sources window. It says that there are no users online.
Is there something in the System Preferences box that I'm missing? Should I turn the firewall off (I shouldn't need to, since I've checked the iTunes Sharing box)? Is the main problem here that you can't share music between a wired and wireless computer? (This would be a bit strange to me, but you never know.)
One other thing. I was trying out the network and I can only get access to the wired Mini's Public folder as a Guest, not as a Registered User. Is there something very badly wrong here?
Any suggestions welcome. Thanks.Thanks for the rapid response. All of those preferences, however, are already set properly (i.e., as you said) on both computers. When I try to go to the Network, I can access the wired desktop Mini's hard drive, but when I try to do it on the mini to get into the laptop's it can't find the afp. It just keeps searching but then says it doesn't exist. Not sure if this network-connectivity problem is relevant or not for this particular issue of iTunes sharing. Grateful for any advice.
-
Problems with hp laser printing in leopard- wired and wireless
Printing problems in Leopard are slowly eating away at my last nerve!
Here's the background: I have a Macbook Pro 2.33GHz Core 2 Duo, 4GB ram, running 10.5.2. Ever since I upgraded to Leopard, I've been having printing problems, both wired and wireless. I have an HP Laserjet 1160, which is a wonderfully reliable printer- I've had it since 2005 and have never had a problem.
When I installed Leopard, I began getting a popup message after starting up my computer and logging in. The message has a lighthouse icon on it and reads:
"Popup Error: Failed to listen for incoming Popup jobs. You will not be able to use Popup printing for the duration of this session. Please report this incident to a system administrator."
(for the record, I only have one computer, it's not on any system, and I have the administrator account)
Here are the two problems I have:
-First, wired printing is spotty. Half of the time, when I connect the USB cable and click print, nothing prints. Usually, if I unplug the cable and plug it into the other USB port, then printing works. This is in spite of the fact that the computer recognizes that the printer is there- I can delete then re-add the printer to my printer list and still nothing.
-Second, wireless printing does not work at all. Again, the printer is recognized when plugged in to either the time capsule or the airport express, and I can add the printer, but printing doesn't work: the job is sent to the print queue, but the queue stalls on the "connecting to printer" phase.
This problem is a huge pain, and I have no idea how to solve it. Any help is appreciated.
JonThanks for posting this problem Cathjock. I have had the same issue with a NEC Superscript 1400. Thinking it wast he printer, which is getting up there in age, I went out and purchased a new HP P1505 to no avail. I have been researching this for a few days now and think that all of this is related to a user permission in CUPS. I have de-installed, re-installed, re-booted etc as prescribed and got three pages hours after the fact via my Airport Express connected new printer. Generally, however, nothing comes out immediately as was the case in the past either on Airport Express or via USB cable. I am stumped and am starting to get worried.
I can't print invoices for my business and am considering firing up my old Windows machine if you can believe it !
Seriously, Apple has created a monstrous situation with all of htese printing issues and nothing is apparently being done, nothing that I can find in any of the discussion forums at this time.
My last option is to re-install 10.5 with an archive and install as I really cannot afford to start from scratch.
Now if you look at this forum, there are 242,847 views logged with 2,514 questions and 13,848 messages.
This should mean something for Apple as many people need help and are getting really really ******-off.
So pleeeeaaaaase Apple. respond and offer a fix for this problem that is plaguing a ton of people.
Chris -
Wired and Wireless Connections to OfficeJet 8620?
We have a small wired Ethernet network. We are planning to install an HP OfficeJet 8620 multi-function printer tomorrow. I understand that for a wired-only Ethernet network, I would just connect the OfficeJet to our router, then install the drivers on each workstation.
Unfortunately, our situation is more complicated than that. Several people want to use wireless devices to print to the OfficeJet 8620. We have a working wireless network in place, and the wireless devices are able to access it without problem..
All devices on the network (wired and wireless) use the same router, which has both wired Ethernet ports and wireless capability. So, everything is on the same network, going through the same router.
From reading the 8620 documentation, it looks like you can only have a wired OR a wireless connection, but not both. Apparently connecting a CAT-5 cable to the Ethernet port on the printer disables the wireless capability of the printer.
If that is correct, what can we do to enable both wired computers and wireless mobile devices to print to the 8620, given the network structure I have described above?
Thanks very much for any assistance you can offer.
This question was solved.
View Solution.Hi,
You can setup as shown on page #7 of tyhe following guide:
http://www.hp.com/ctg/Manual/c00389927.pdf
Regards.
BH
**Click the KUDOS thumb up on the left to say 'Thanks'**
Make it easier for other people to find solutions by marking a Reply 'Accept as Solution' if it solves your problem.
Maybe you are looking for
-
Music won't correctly play on iPhone 5s
I generally don't have any music on my phone since I keep it all on my iPod but with my iCloud back up, a few songs did load on my phone and I'm having some issues. 1 -- if I don't have the music downloaded to my phone but rather it's playing directl
-
Job cancelled after system exception ERROR_MESSAGE in DB13
Hello All, When i opened the t-code DB13 i saw that this job "Mark tables requiring statistics update" is cancelled. JOB LOG: 12.02.2011 22:00:16 Job started 12.02.2011 22:00:16 Step 001 started (program RSDBAJOB, variant &0000000000085, user ID
-
Showing yesterday's data in SSRS
Hi Guys, I need some help with an expression for SSRS. I need to get only the data for the last date in the query . I just want the previous date information whereas on Monday, it's going to be Friday's information. I tried with this as a test but is
-
Safari 3.0.4 quit unexpectedly Thread 0 crash
Updated software to 10.4.11 and Safari 3.0.4, and now I get a "Safari quit unexpectedly" error every time I launch. It quits every time on launch. I am currently using a saved copy of 2.0.4 that opens without a problem. Here is the Crash Log if anyon
-
Business areawise and profit centre wise debtors balances
Hi All, I want to know the standard T code to see the debtors/Creditors balance report based on business area and profit centre wise (not debtors aging report). Thanx. SP Shukla.