Wireless card

what would i need to have wireless internet like in a car?
like we have a wireless pc card for my dell. but i just recently bought a macbook, and want to have wireless internet like when we go on trips and what not.

I have a card for my Powebook G4 and it's costly. About $79.00 a month, not including the card from Verizon. Unless you have the money which doesn't include another adaptor for the wireless card to work with the Macbook, I would recommend checking out Smith Micro. They carry USB adapters for connecting a cell phone to a laptop. Otherwise, joining a hotspot would the alternative.
http://www.smithmicro.com/default.tpl?group=subsolutions&id1=1&id2=88

Similar Messages

Wireless-Card doesn't not work with WPA/WPA2 but with WEP [Solved]

Hello I have a MacBook (late 2007) with a wireless-card from Broadcam, the card works with WEP and the classic configuration over rc.conf very well. But I can't get the card running with WPA and the net network-profiles.
Here is the link to the driver - http://www.broadcom.com/support/802.11/linux_sta.php
eth2 = wireless-card
eth1 = firewireanything
eth0 = wired-card
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="UTC"
USEDIRECTISA="no"
TIMEZONE="Europe/Berlin"
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=(sky2 snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore)
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="macbook"
# 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.1.220 netmask 255.255.255.0 broadcast 192.168.1.255"
INTERFACES=(!eth0 !eth1 eth2)
# 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.1.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=(wireless)
# 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 network net-profiles netfs alsa crond portmap fam hal)
/etc/network.d/wireless
CONNECTION="wireless"
INTERFACE=eth2
HOSTNAME=macbook
IP="static"
IFOPTS="192.168.1.225 netmask 255.255.255.0 broadcast 192.168.1.255"
GATEWAY=192.168.1.1
DNS1=192.168.1.1
# Wireless Settings (optional)
ESSID=3Com
#KEY=
IWOPTS="mode managed essid $ESSID channel 11"
#WIFI_INTERFACE=wlan0 # use this if you have a special wireless interface
# that is linked to the real $INTERFACE
#WIFI_WAIT=5 # seconds to wait for the wireless card to
# associate before bringing the interface up
USEWPA="yes" # start wpa_supplicant with the profile
WPAOPTS="" # use "" for normal operation or specify additional
# options (eg, "-D ipw")
# see /etc/wpa_supplicant.conf for configuration
Can I set here the WPA/WPA2-Key also? Why here ESSID? Do I need still a configuration in wpa_supplicant.conf?
Thats very confusing and not explained.
WPAOPTS? Do I need to add something like "-D wext"?
/etc/wpa_supplicant.conf
# This is a network block that connects to any unsecured access point.
# We give it a low priority so any defined blocks are preferred.
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
network={
key_mgmt=NONE
priority=-9999999
network={
ssid="3Com"
proto=WPA
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=CCMP TKIP
psk="topsecret"
priority=5
# WPA2
# proto=WPA RSN
I need help. Please
Last edited by hoschi (2009-01-04 20:21:58)

fwojciec wrote:If this info is not in the wiki it might be worth it to add it -- it's all detailed in /etc/network.d/examples/complete.example though.
Thats the reason why I was so confused.
My new and well working configuration:
# /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="UTC"
USEDIRECTISA="no"
TIMEZONE="Europe/Berlin"
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=(sky2 snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore)
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="macbook"
# 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.1.220 netmask 255.255.255.0 broadcast 192.168.1.255"
INTERFACES=(!eth0 !eth1 !eth2)
# 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.1.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=(3com)
# 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 network net-profiles netfs alsa crond portmap fam hal)
CONNECTION="wireless"
DESCRIPTION="Very verbose complete wireless example"
INTERFACE=eth2
HOSTNAME=macbook
# Interface Settings (use IP="dhcp" for DHCP)
IP="static"
IFOPTS="192.168.1.225 netmask 255.255.255.0 broadcast 192.168.1.255"
GATEWAY=192.168.1.1
# DNS Settings (optional)
DOMAIN=localdomain
DNS1=192.168.1.1
DNS2=
SEARCH=
# Standard Wireless Settings
ESSID=3Com
SECURITY=wpa-config # One of wep, wpa, wpa-config, none
KEY=""
# Scans to see if network is available before connecting (reccomended)
SCAN="YES"
# Time to wait to connect to a network. Default 15.
TIMEOUT=10
# Pass *custom* options to iwconfig. Usually not needed (optional)
IWOPTS="mode managed essid $ESSID channel 6 key restricted $KEY"
# Any extra arguments for wpa_supplicant
WPA_OPTS=
# For SECURITY='wpa-config' only - filename of a wpa-supplicant config
WPA_CONF=/etc/wpa_supplicant.conf
# This is a network block that connects to any unsecured access point.
# We give it a low priority so any defined blocks are preferred.
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
network={
key_mgmt=NONE
priority=-9999999
network={
ssid="Linksys"
proto=WPA RSN
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=CCMP TKIP
psk="areulookingatmybreasts"
priority=5
network={
ssid="3Com"
proto=WPA
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=CCMP TKIP
psk="nomam"
priority=5
# WPA2
# proto=WPA RSN
There are also profiles for the Linksys-Router and for wired cable.
Thanks for the help!
Last edited by hoschi (2009-01-04 20:21:23)

PCI-e wireless card causes lock ups Z87 MPower MAX

I've already asked this question once, but was part of an epic essay that I've decided to break down into smaller more manageable chunks (as unsurprisingly that one got no replies).
I've got an ASUS PCE-A66 wireless ac pci-e card. Had absolutely no issues with it in my old Z77 board, but I seem to be having a lot of issues with it in my new Z87 MPower MAX. System was locking up like mad when I was trying to install the drivers at first. Had to rip out the WiFi/Bluetooth/WiDi module to get the drivers installed but the system randomly hangs on boot up? Don't get the issues with the card unplugged and don't always get it with it plugged in, but there seems to be some form of conflict with it that I can't resolve. Has anyone else had any such issues with any PCI-e add in cards on this motherboard?
Specs are:
i7 4770k
MSI MPower MAX using .128 bios (will try the .131 later)
2x4GB Corsair Dominator Platinum 2400
Coolermaster Silent Pro Hybrid 1050w
EVGA NVidia GTX 780 SC ACX
Windows 8 Pro 64bit

Yes, old system was Win8 Pro 64 bit too and the drivers are Windows 8 certified. As I say though, I had no issues with it on the old build? Even got a replacement sent out by Amazon in case the card itself was damaged Did initially try to do a warm update of the hardware into the same OS installation but didn't play well so did a full re-install in the end. Tried standard and UEFI installs (just in case) and after a problem with my OCZ Vector 2 not being recognised I bought a new Samsung 840 Pro so was a virgin SSD installed on to as well.
I'll raise it directly with MSI but just wanted to know if anyone else had experienced anything similar with any wireless cards in this mobo.
Cheers for the reply though

Wireless card BCM4313 no connection at boot

Hi,
I have an HP Pavilion dv6 with a Broadcom BCM4313 wireless card. I use NETCFG and before the last kernel upgrade I was able to connect to my home wireless connection at boot without troubles. Now I have to do it manually and I need to try 2 or 3 times to see my connection active.
lspci -vnn
02:00.0 Network controller [0280]: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller [14e4:4727] (rev 01)
Subsystem: Hewlett-Packard Company Device [103c:1483]
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at c3400000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: brcmsmac
Kernel modules: bcma, wl, brcmsmac
lsmod
Module Size Used by
cpufreq_stats 3890 0
radeon 992718 0
ttm 54360 1 radeon
ipv6 290407 22
cpufreq_ondemand 6132 4
uvcvideo 64931 0
videodev 78006 1 uvcvideo
media 10437 2 uvcvideo,videodev
usbhid 35256 0
hid 81635 1 usbhid
v4l2_compat_ioctl32 8292 1 videodev
snd_hda_codec_hdmi 22092 1
joydev 9895 0
snd_hda_codec_idt 55175 1
i915 707307 7
snd_hda_intel 22122 0
snd_hda_codec 77927 3 snd_hda_codec_hdmi,snd_hda_codec_idt,snd_hda_intel
drm_kms_helper 25409 2 radeon,i915
lib80211_crypt_tkip 8506 0
drm 183380 5 radeon,ttm,i915,drm_kms_helper
snd_hwdep 6325 1 snd_hda_codec
snd_pcm 73856 3 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec
snd_timer 19416 1 snd_pcm
r8169 42643 0
lib80211 4158 1 lib80211_crypt_tkip
snd 57786 7 snd_hda_codec_hdmi,snd_hda_codec_idt,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
sg 25557 0
hp_accel 13864 0
lis3lv02d 10508 1 hp_accel
i2c_i801 8187 0
serio_raw 4294 0
iTCO_wdt 12717 0
hp_wmi 7738 0
intel_agp 10904 1 i915
arc4 1410 2
btusb 11577 0
evdev 9530 9
bluetooth 138465 1 btusb
soundcore 6146 1 snd
bcma 13762 0
i2c_algo_bit 5199 2 radeon,i915
sparse_keymap 3088 1 hp_wmi
mei 31249 0
i2c_core 20133 7 radeon,videodev,i915,drm_kms_helper,drm,i2c_i801,i2c_algo_bit
iTCO_vendor_support 1929 1 iTCO_wdt
pcspkr 1819 0
snd_page_alloc 7121 2 snd_hda_intel,snd_pcm
intel_ips 11213 0
psmouse 55224 0
intel_gtt 14423 3 i915,intel_agp
mii 3995 1 r8169
input_polldev 2882 1 lis3lv02d
battery 10905 0
wmi 8411 1 hp_wmi
ac 3265 0
button 4470 1 i915
brcmsmac 594624 0
thermal 7863 0
video 11228 1 i915
brcmutil 6563 1 brcmsmac
mac80211 215605 1 brcmsmac
cfg80211 160516 2 brcmsmac,mac80211
rfkill 15402 3 hp_wmi,bluetooth,cfg80211
crc_ccitt 1331 1 brcmsmac
acpi_cpufreq 5877 1
freq_table 2451 3 cpufreq_stats,cpufreq_ondemand,acpi_cpufreq
processor 24256 1 acpi_cpufreq
mperf 1275 1 acpi_cpufreq
ext4 369556 2
mbcache 5817 1 ext4
jbd2 71074 1 ext4
crc16 1297 2 bluetooth,ext4
sr_mod 14951 0
sd_mod 28307 4
cdrom 36329 1 sr_mod
ahci 20865 3
libahci 18885 1 ahci
libata 173297 2 ahci,libahci
ehci_hcd 39511 0
scsi_mod 131482 4 sg,sr_mod,sd_mod,libata
usbcore 142544 5 uvcvideo,usbhid,btusb,ehci_hcd
dmesg | grep wlan0
[ 11.715805] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 13.791409] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 16.885059] wlan0: authenticate with 50:67:f0:ab:4f:d4 (try 1)
[ 16.886567] wlan0: authenticated
[ 16.890100] wlan0: associate with 50:67:f0:ab:4f:d4 (try 1)
[ 16.892793] wlan0: RX AssocResp from 50:67:f0:ab:4f:d4 (capab=0x471 status=0 aid=1)
[ 16.892798] wlan0: associated
[ 16.894146] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 26.697130] wlan0: deauthenticating from 50:67:f0:ab:4f:d4 by local choice (reason=3)
[ 87.612906] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 89.754106] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 92.849882] wlan0: authenticate with 50:67:f0:ab:4f:d4 (try 1)
[ 92.851661] wlan0: authenticated
[ 92.851823] wlan0: associate with 50:67:f0:ab:4f:d4 (try 1)
[ 92.854142] wlan0: RX AssocResp from 50:67:f0:ab:4f:d4 (capab=0x471 status=0 aid=1)
[ 92.854150] wlan0: associated
[ 92.855920] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 103.719958] wlan0: no IPv6 routers present
[ 105.980215] wlan0: deauthenticating from 50:67:f0:ab:4f:d4 by local choice (reason=3)
[ 120.237260] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 122.316759] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 125.422195] wlan0: authenticate with 50:67:f0:ab:4f:d4 (try 1)
[ 125.423760] wlan0: authenticated
[ 125.423960] wlan0: associate with 50:67:f0:ab:4f:d4 (try 1)
[ 125.426083] wlan0: RX AssocResp from 50:67:f0:ab:4f:d4 (capab=0x471 status=0 aid=1)
[ 125.426090] wlan0: associated
[ 125.428085] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 136.398877] wlan0: no IPv6 routers present
You could see that first I get the connection and then I lost it... for 2 or 3 times, then I could connect without problems.
ifconfig
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:338 errors:0 dropped:0 overruns:0 frame:0
TX packets:338 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:27772 (27.1 Kb) TX bytes:27772 (27.1 Kb)
wlan0 Link encap:Ethernet HWaddr E0:2A:82:A2:B5:88
inet addr:192.168.1.33 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::e22a:82ff:fea2:b588/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:12484 errors:0 dropped:0 overruns:0 frame:0
TX packets:9606 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:13841736 (13.2 Mb) TX bytes:1241490 (1.1 Mb)
iwconfig
wlan0 IEEE 802.11bgn ESSID:"WLAN_A9"
Mode:Managed Frequency:2.452 GHz Access Point: 50:67:F0:AB:4F:D4
Bit Rate=54 Mb/s Tx-Power=19 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=40/70 Signal level=-70 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:82 Missed beacon:0
my wirelessCasa netcfg profile
CONNECTION='wireless'
DESCRIPTION='A simple WEP encrypted wireless connection'
INTERFACE='wlan0'
SECURITY='wep'
ESSID='WLAN_A9'
KEY='s:mykey'
IP='dhcp'
POST_UP="notify-send -u critical -i /usr/share/icons/Faenza/status/48/connect_established.png -t 15000 'Connected to WLAN_A9'"
POST_DOWN="notify-send -u critical -i /usr/share/icons/Faenza/status/48/gnome-netstatus-disconn.png -t 15000 'Connection lost'"
# Uncomment this if your ssid is hidden
#HIDDEN=yes
rc.conf
NETWORKS=(wirelessCasa)
DAEMONS=(syslog-ng dbus net-profiles net-auto-wired !network !netfs crond laptop-mode alsa slim @acpid @cups)
When I execute netcfg for the first time (after boot) I see:
#NETCFG_DEBUG=yes netcfg wirelessCasa
DEBUG: Loading profile wirelessCasa
DEBUG: Configuring interface wlan0
:: wirelessCasa up [BUSY] DEBUG: status reported to profile_up as:
DEBUG: Loading profile wirelessCasa
DEBUG: Configuring interface wlan0
DEBUG: wireless_up stop_wpa wlan0
DEBUG: wireless_up start_wpa wlan0 /run/network//wpa.wlan0/wpa.conf nl80211,wext
DEBUG: wireless_up stop_wpa wlan0
DEBUG: wireless_up Configuration generated at /run/network//wpa.wlan0/wpa.conf
DEBUG: wireless_up ifup
DEBUG: wireless_up start_wpa wlan0 /run/network//wpa.wlan0/wpa.conf nl80211,wext
DEBUG: wireless_up wpa_check
DEBUG: wpa_cli -p /run/wpa_supplicant -i wlan0 status
DEBUG: Loading profile wirelessCasa
DEBUG: Configuring interface wlan0
DEBUG: ethernet_iproute_up ifup
DEBUG: ethernet_up dhcpcd -qL -t 10 wlan0
DEBUG:
> DHCP IP lease attempt failed.
DEBUG: Loading profile wirelessCasa
DEBUG: Configuring interface wlan0
DEBUG: Loading profile wirelessCasa
DEBUG: Configuring interface wlan0
DEBUG: ethernet_down if_down
DEBUG: wireless_down stop_wpa wlan0
DEBUG: profile_up connect failed
[FAIL]
And the second one:
#NETCFG_DEBUG=yes netcfg wirelessCasa
DEBUG: Loading profile wirelessCasa
DEBUG: Configuring interface wlan0
:: wirelessCasa up [BUSY] DEBUG: status reported to profile_up as:
DEBUG: Loading profile wirelessCasa
DEBUG: Configuring interface wlan0
DEBUG: wireless_up stop_wpa wlan0
DEBUG: wireless_up start_wpa wlan0 /run/network//wpa.wlan0/wpa.conf nl80211,wext
DEBUG: wireless_up stop_wpa wlan0
DEBUG: wireless_up Configuration generated at /run/network//wpa.wlan0/wpa.conf
DEBUG: wireless_up ifup
DEBUG: wireless_up start_wpa wlan0 /run/network//wpa.wlan0/wpa.conf nl80211,wext
DEBUG: wireless_up wpa_check
DEBUG: wpa_cli -p /run/wpa_supplicant -i wlan0 status
DEBUG: Loading profile wirelessCasa
DEBUG: Configuring interface wlan0
DEBUG: ethernet_iproute_up ifup
DEBUG: ethernet_up dhcpcd -qL -t 10 wlan0
DEBUG:
DEBUG: ethernet_iproute_up hostname archlap
[DONE]
I've tried to use the wl driver but it doesn't seems to work properly.
Could anyone help me please?
Thank you,
enrico

litemotiv wrote:
Hmm it seems your card now takes longer to connect, the 'deauthenticating by local choice' often means that the default timeout is reached and netcfg disconnects. You can try adding a specific timeout parameter to your netcfg profile:
TIMEOUT=60
That doesn't explain why it takes longer to connect than before, but at least you should be able to connect in 1 try again.
Hi,
thank you for your time!
I'v tried adding the timeout line to my profile but it doesn't change nothing
I could connect at 3rd try.
Any other idea?

Startup gets 'Network cable unplugged' on mini-PCI wireless card

I recently installed a Netgear DG834GT wireless router and now have an intermittent problem connecting my Tecra 9100 to it. If the 9100 has been shutdown for a while (like overnight), when I restart I always get 'Network cable unplugged' for the wireless connection. Rebooting a number of times (anything from 3 upwards) I eventually get connected to the router and all then works fine for hours. Even a quick restart at this point (i.e. once the wireless card has connected) does not cause a problem but as soon as I leave the machine shutdown for a length of time it fails again at reboot.
There are no errors in the Event log.
I am using the built in mini-PCI wireless card and have already upgraded to the latest driver.
Any ideas gratefully recieved, at the moment each morning is a 20-30 minute frustration of rebooting trying to get my connection working.
(Running Win2K Professional)

Checking other boards for help (Netgear etc.) it seems that the 'Network cable unplugged' is a common message when wireless connectivity is failing. However, to prove the point, I have disabled the other LAN card (for which I was also getting 'network cable unplugged' but as expected since it was). I still get the same issue with the wireless card, although now the reboots are slightly more predictable - it normally seems to succeed on the third reboot. I guess disabling the other card has changed the startup timing slightly and in that way made things slightly better.
Again, any other suggestions gratefully received. As this seems to be a timing issue at startup, I am suspicious that one of the other things that runs at that time is causing the problem.

Startup gets 'Network cable unplugged' on mini-PCI wireless card (again)

Reposting as previous topic has been locked although has not been resolved. Original post below, please see previous post for more details
I recently installed a Netgear DG834GT wireless router and now have an intermittent problem connecting my Tecra 9100 to it. If the 9100 has been shutdown for a while (like overnight), when I restart I always get 'Network cable unplugged' for the wireless connection. Rebooting a number of times (anything from 3 upwards) I eventually get connected to the router and all then works fine for hours. Even a quick restart at this point (i.e. once the wireless card has connected) does not cause a problem but as soon as I leave the machine shutdown for a length of time it fails again at reboot.
There are no errors in the Event log.
I am using the built in mini-PCI wireless card and have already upgraded to the latest driver.
Any ideas gratefully recieved, at the moment each morning is a 20-30 minute frustration of rebooting trying to get my connection working.
(Running Win2K Professional)

More info : I have found that this is time related rather than related to the number of reboots. It always fails on the first reboot after being shut down for a period of time. At this point, however long I wait the connection never comes up. However, if I wait a few minutes and then reboot, the second reboot will always successfully establish the connection.
On this basis, the problem has become slightly less annoying as I have a workaround - boot once, wait a few minutes and reboot. That being said, any information on how I can isolate this further (e.g. tracing what is running at startup) would be gratefully recieved.

Audigy 2 will not work with my PCI wireless card......causes freezing mouse ......HELP,!

Hi All,
I am just about beat with my Audigy2 Plat. card !!!!! .
IT WORKS A TREAT ON IT'S OWN . but when I attatch my wireless PCI Card all hell breaks loose.
My wireless card works great with a SoundBlaster Li've card,,,,,,,,,,,,,,,,,,,,,but not the Audigy 2.
Device manager can't see any conflics.................... I have updated all drivers , but no luck.
I have had "looking for ctgame.sys " messages ...................managed to find that file on the Installation Disk, but still it won't give me a break.....................just when you think you might be getting some where the mouse freezes and you have to reboot !!!!! What is it about the Audigy 2 ?
I have a feeling it might be something to do with the Game Port ................... I don't wan't to play games !
Please help.........
Cheers
Blackbob

Blackbob wrote:
Hi All,I am just about beat with my Audigy2 Plat. card !!!!! . IT WORKS A TREAT ON IT'S OWN . but when I attatch my wireless PCI Card all hell breaks loose.My wireless card works great with a SoundBlaster Li've card,,,,,,,,,,,,,,,,,,,,,but not the Audigy 2.Device manager can't see any conflics.................... I have updated all drivers , but no luck. I have had "looking for ctgame.sys " messages ...................managed to find that file on the Installation Disk, but still it won't give me a break.....................just when you think you might be getting some where the mouse freezes and you have to reboot !!!!! What is it about the Audigy 2 ?I have a feeling it might be something to do with the Game Port ................... I don't wan't to play games !Please help.........CheersBlackbob
Just disable the gameport on "Device Manager" to see if it's the culprit.
Have you also played with mouse settings (acceleration and saple rate)?
.jtp

Satellite Pro 4600 Wireless card does not work with WIN2K ?

I have a Satellite Pro 4600 with UK dealer installed PA3070U-1MPC wireless card running with Windows 2000
The wireless client manager finds the network of my wireless router and reports the signal is excellent and I see all green bars swhowing.
However I can't mske a connection, in 'connections' the wireless one says 'network cable is disconnected'
the router works ok with other laptops in my house.
I have latest version of Win2K also have downloaded and installed latest versions of client manager and WLAN card driver for win2k from toshiba website.
The 'toshiba support in Turkey' told me 'I need a different driver for Win2K for my wireless card cause the win2K driver on the toshiba website is not for 'this' wireless card'. I have waited for this for 3 weeks now and have been unable to reach the elusive UK Level 3 support who supposedly have this driver. I have seen on the internet the same wireless card is has been sold as a 'made by toshiba' accessory and it says it is compatible with Wim2K
What do I do next please ? Does this run at all with Win2K , is there 'another driver' and so on ?
Thanks

hello
please be more scpecific - what do you mean by 'disconnect the LAN' - I have nothing conneced there anyway ? do you mean 'disable' the LAN even though there is nothing plugged in ? can you please post the exact sequence of this so I can try ir too.
In the meantime my laptop has been to Toshiba for them to sort out at their highest level UK support base. I was hoping my troubles would be over - but no, read below what happened. They are basically saying my win2k is not in order but I had just installed and updated it so right now I haven't a clue what to do next.
START QUOTE of Toshiba Support response:
Sat Pro 4600
Serial No: 31474181G
Windows 2000 SP4 (customers build not recovery CD)
BIOS V1.80 not current therefore updated to V2.60
The notebooks wireless card is functional and has the correct driver installed, it also has the correct and latest version of the Wireless Client Manager. The wireless function appears to see the router but will not connect and obtain an IP address. Irrespective of the settings applied within Internet Explorer or the Wireless client manager you cannot obtain a connection. The customer did not have any Toshiba utilities installed such as, Power Saver, Common Modules, Chipset drivers, network device switch, I therefore installed these missing components and updated the BIOS to the most current revision. However despite this the unit will still not connect to the wireless.
I therefore removed the customers HDD and replaced his HDD with a Toshiba loan HDD with a fresh build that I had created. When using the machine with this build the wireless connected without issue and I was able to browse the internet etc. I placed the customers HDD into our machine and the problem with the wireless was replicated on our machine here, therefore the problem is not with the wireless card or any hardware aspect of the machine, the problem lies with the customer's build of Win 2000. I examined for anything obvious but could not find anything, therefore I'm sending this machine back to customer with the advice that his build needs addressing or he needs to reload Win 2000 his machine.
As you can see from the above comments, the machine performs as per specification with loan HDD and fresh build of Win 2000 installed, the problem is only present with you HDD and build in the machine. In addition to this I have replaced the missing screws on the base of the machine ensuring the machine is structure is maintained.
5 x B16 Screws
1 x B6 Screw
1 x Memory Cover Screw
END QUOTE

Connecting a PC with an external wireless card

I have an iMac and am connected wirelessly to the Internet through the Airport Extreme. My roommate has a new Dell Laptop with Windows XP and has been connected through ethernet to the base station. She just recently purchased an external wireless card, and we can't seem to get her connected wirelessly. When searching for available networks to join on her computer, it recognizes my network and says that it has an excellent signal, but when we type in the WEP, it doesn't do anything. It does not give us an error, and it does not connect. Any idea what we are doing wrong and what we can do to fix it?

I still can't figure it out. I unchecked the option that says "enable encryption (using WEP)" and she was immediately connected. I don't think I have a huge problem leaving the network up without a password, I'm in a small residential area. Does that just mean that neighbors would be able to connect? How far does the signal generally travel? And is there any way to see the IP addresses of people connected to this specific network?

G500 Driver_Power_State_Failure problem most likely related to Wireless Card

I recently upgraded my Lenovo G500 laptop to 8.1.
After that, I've been constantly getting BSOD every time I modify some settings on my WIreless card (Broadcom 802.11n Network Adapter). For instance, changing my MAC under the"Locally Administered MAC Address" causes the Wireless configuration window to stop responding, then my wireless adapter becomes permanently disabled (I try to enable it and it says that it is enabling but the adapter remains faded out and locked in a disabled state) unless I restart or power down my laptop. If I restart, the laptop hangs for 3-5 minutes and then a BSOD comes up and suggests that I look online for DRIVER_POWER_STATE_FAILURE.
I have updated the adapter as well as most, if not all outdated drivers on my laptop with the 8.1 drivers offered on Lenovo's support pages (This includes power management, BIOS, LAN, Audio, etc.). Even attempting to voluntarily disable my wireless card causes the BSOD.
As long as I don't touch/modify such settings, I have wireless internet and all seems fine but once I do what I stated above, my laptop crashes with a BSOD. I have looked up and searched about such a BSOD but my laptop has zero problems when I put it to sleep or wake it up. My laptop functions practically flawless except for when changing/modifying settings on my wireless card.
For instance, on Whocrashed.exe:
On Thu 11/7/2013 9:33:19 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\110713-17031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x150B36)
Bugcheck code: 0x9F (0x4, 0x12C, 0xFFFFE00000EB5040, 0xFFFFD000205F8860)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 11/7/2013 9:33:19 AM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x9F (0x4, 0x12C, 0xFFFFE00000EB5040, 0xFFFFD000205F8860)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time
On bluescreenview:
Bug check string: DRIVER_POWER_STATE_FAILURE
Bug check code: 0x0000009f
Parameter 1: 00000000`00000004
Parameter 2: 00000000`0000012c
Parameter 3: ffffe000`00eb8040
Parameter 4: ffffd000`20472860
Processor: x64
Caused by driver: NETIO.SYS
Caused by address: NETIO.SYS+1ddb2
Crash address: ntoskrnl.exe+150b36
I ran SFC /scannow and it did detect corrupted files but that has been resolved using the Restorehealth command prompt. I have tried booting to safe mode, uninstalling the adapter and then updating straight to the most current 8.1 driver and that still causes the BSOD.
I'm almost certain that my wireless card probably is defective, or the laptop is defective. I'm still under warranty but I'm hoping to fix this issue before resorting to what I deem as last resorts of factory restoring the laptop or calling Lenovo support.
I am also providing minidumps, driver lists and a whole ton of useful information on my Skydrive:
http://sdrv.ms/17OIYda
Any suggestions or help on this matter would be greatly appreciated as I feel like I've exhausted all other methods.
Moderator Note; subject edited; system type added

"If I restart, the laptop hangs for 3-5 minutes and then a BSOD comes up and suggests that I look online for DRIVER_POWER_STATE_FAILURE."
I had the exact same problem on a Thinkpad Helix after upgrading to Windows 8.1, although I do not know if it was in anyway related to the wireless hardware as you described. However, I noted that in the Device Manager many wireless hardware components had been highlighted with an exclamation mark since the problem had occured (e.g. Bluetooth, Geolocation, Broadband). Here is how I fixed it:
1. I went to System Settings / Device Manager.
2. Disabled all devices that were highlighted with an exclamation mark. I noted that the Device Manager would not respond after disabling so I closed it and then chose to not wait (i.e. forced the Device Manager to close).
3. Repeated step (2.) until all devices highlighted with an exclamation mark were disabled.
4. Restarted the laptop (I don't know if I had to force the shut down via power off at that time, but it may be necessary or you wait for the BSOD).
5. Repeated step (1.) and uninstalled all the drivers of the devices disabled in steps (2.) to (3.), enabling the option to remove the driver from the system, where possible.
6. Restarted the system. This time the shutdown should only take a few seconds.
So far, everything works fine again and I cannot identify any limitations through the disabling and uninstalling of devices (esp. wireless devices do work flawlessly).
Hope this works for some of you guys out there as well. Let me know.
Good luck!
neophilos

Can I put an Intel Advanced-N 6230 wireless card into my Pavilion dm4-3050us laptop?

I have been having problems with the wireless connection on my dm4-3050us laptop for several months now and am hoping to replace the wireless card in order to solve these issues.
Will I be able to put an Intel Advanced-N 6230 adapter into my machine?
If so, is there anything special I will need to do in order to make it work as it normally would? (i.e. special adapters to make it fit into the machine, driver updates, etc.)

You can use one of these:
Intel Centrino Advanced-N 6230 WLAN module 631956-001
Intel Centrino Ultimate-N 6300 WLAN module 572511-001
It HAS to be an HP branded card with the HP number. It is not good enough if it is another card with the same wifi chip. Only HP branded and numbered cards will allow the system to POST.
Here is the Service Manual:
Manual
See page 41. You may find that you need 3 antenna leads and the laptop only has 2. It is very hard to string another antenna lead but it can be done.
Here is the Advanced-N card on eBay which appears to have only 2 leads:
http://www.ebay.com/itm/GENUINE-OEM-HP-Pavilion-DV6-6000-WIFI-Wireless-Board-631956-001-/36077457082...
You will need to load the correct Intel driver and I would just have it downloaded to the laptop before you do the swap:
http://h10025.www1.hp.com/ewfrf/wc/softwareDownloadIndex?softwareitem=ob-104707-1&cc=us&dlc=en&lc=en...
Link to the Windows 7 driver above. Good luck. This should be pretty much plug and play for you but post back if you need more help.
If this is "the Answer" please click "Accept as Solution" to help others find it.

Can't change MAC address of my wireless card on Windows XP

Dear Forum Members,
I have recently bought a notebook, Lenovo IdeaPad G550L (I haven't found section for the G series here on the forum) and would like to use its WiFi adapter (BCM4310 according to Everest) with explicitly changed MAC address. I installed the recommended driver, available from Lenovo's website, version 5.10.38.14. I tried the common way to change the MAC address, went to Control Panel -> Network Interfaces -> Broadcom Wireless Network Adapter -> Configure... -> Advanced -> Locally administered MAC address, and changed it to a different address (without ":" or any separator characters). Unfortunately this common solution won't work at all. Although, no error messages are produced when changing it (so it seems successful) my wireless router shows me the original MAC address of my integrated wifi card. Tried to restart my computer, my router, everything.
* Tried different drivers, downloaded a driver from HP which had a separate wireless configurator, Broadcom Wireless Utility. It worked like the driver from Lenovo (except this one hasn't got the utility), but I was still unable to change my MAC address.
* Tried a different driver from SoftPedia, version 5.10.79.14 (this is newer than Lenovo's), it didn't work either.
* Tried Nathan True's MACShift utility. It seemed to change the MAC address, but my router showed the original, so it didn't.
* Tried to look for official Broadcom drivers on www.broadcom.com but found nothing for BCM4310.
* Finally, I booted my alternative OS, the latest Ubuntu Linux, and used the kernel driver b43 for my wireless adapter. I tried to change my MAC address using the command ifconfig wlan0 hw ether .... and connected to my network. It worked, my router showed the changed MAC so the hardware (or the firmware) is capable of doing this by the right driver/firmware.
I tried to address Broadcom with the issue, sent them a letter like this post they replied that they are not competent, they wrote the following (I guess this was an automatically generated message because it got back in 10 seconds ) from [email protected]:
"As the chipset supplier, Broadcom provides driver support to our customers - the manufacturers of wireless devices - that ultimately provide products to end customers, such as wireless LAN vendors, cable modem vendors, and notebook providers. It is up to these manufacturers to provide product-specific drivers and software support to their end customers. Please contact the manufacturer of your wireless device for their current drivers"
Then I addressed Lenovo with the problem, their answer:
"Dear ******,
Thank you for contacting Lenovo, the makers of ThinkPad and ThinkCentre products. As I understand, you have purchased a Lenovo IdeaPad G550L and would like to use its WiFi adapter (BCM4310 according to Everest) with explicitly change MAC address.and you would like to know is there an official driver for Windows XP that allows you this basic feature like b43 in Linux. We apologize,Please do speak with our Idea pad technical Team at 877-453-6686 Option 1-2-1-2 for further assistance.
If you have further questions or concerns, please feel free to contact us at 866-42-THINK (84465) option number 2. We will be happy to assist at that time.
Once again, thank you for contacting Lenovo.
Sincerely,
Lenovo Websales/CustServe"
So this means I should call them and spend extra money for phone bill of international calls because of their fault of providing a basic feature that is to be expected from every single wireless card in the market. Should I believe that a guide over the phone is more efficient than a step-by-step solution or a link to an alternative driver? I'm getting kind of disappointed. At least they have understood (or copy-pasted) my problem, dutch comfort though.
Any ideas? Anyone experienced the same problem and solved it? Is there an official (or even unofficial) driver for this device for Windows XP that allows me this basic feature (like b43 in Linux)?
Thanks in advance,
str4ngS

Yes, I have posted this thread to different forums after I realized that Lenovo "customer care" is not likely to help me out and even wirelessforums.org members couldn't come up with any ideas for days, that's why. I have already written that helper applications like SMAC (or etherchange or macshift) don't work, because they do the same thing in the system as I change it in the driver panel, so they use the same method which simply does not work.
Locked? Definitely not. If yes, why can I change the MAC of my adapter under Ubuntu Linux using b43 open-source driver if it's really locked? Or you mean it's locked from software, because Lenovo or Broadcom didn't want their users to change their MACs or they just forgot to release a fully-functional driver? Well, then I would like to have a driver in which it's not locked, because this is a basic feature of my adapter of which the hardware is capable.
I have already contacted Broadcom, see their (automatically-generated) answer in my initial post, but I will try to do that again with more foresight.

Snow Leopard and my alltel wireless card do not get along.

I recently purchased an alltel wireless card for my MacBook that connects to the internet fine, but appears to be messing with the operating system . . . or something. Alltel said they write their software according to the information they received from Apple. Apple says they send the operating system to Alltel, and they have no way to fix my problem. Can anyone out there help me?
It seems that if I shut down my MacBook after every time I use the card, I am OK.
If I use it more than once without shutting down, things start to go wrong. For example, sometimes the keyboard stops working. The mouse is fine.
More often, I disconnect from the Quicklink (alltel) software, pull the card, only it seems the software has not truly disconnected, as the Menu Bar ceases to work, the colored wheel spins and spins, and I cannot shut down my MacBook, not even w/the "3 magic keys," unless I press the power button. A complete shutoff always solves any problems.
I did check Disk Utility and found that many disk permissions did not match and repaired them. This did not fix the problem.
My local Mac "fixer" said she had the same problem with another customer and had to re-install the operating system, etc., etc., but would have to charge me a minimum of $70. She has no idea why this worked or if it will work with my MacBook. I do not want to spend $70 with no guarantee, or even probability, that the problem will be solved.
Any ideas?

Hi Voodooflea, I have experienced exactly the same problem as you describe here. The solution I found was to simply NOT use the QuickLink Mobile software to connect. Rather, just go into your System Preferences and then to the Network section. If it isn't already there, create a new connection with the modem, putting in the appropriate numbers for the telephone and account name. Then, connect from within the Network system preferences and you probably won't have the lock-up of your computer. It seems that I only have this problem when I use the QuickLink Mobile software to connect. Let us know if this works for you.

Can't create a wireless network without a wireless card on my Mac

Help!
O.k. I tried searching the forums for an answer but the odd nature of my problem, and the immense database of topics made it very difficult to find a similar post.
The general issue/idea:
Run a wireless network using Airport Extreme - Connect desktop mac via ethernet and Roku player via wi-fi. Can't get the desktop mac to connect via ethernet when I restart the network/Airport Extreme.
My Father in law has my old computer; It's a PowerMac G5 (Dual 1.8GHz CPUs) running OS 10.5.8), connected to internet via cable (TimeWarner) modem. It does NOT have an Airport or Airport Extreme card installed. The computer works fine, and I don't believe that I 'need' an Airport Card in order to use the Airport Extreme (it's a brand new/refurbished model) in the manner described below.
I would like to use the Airport Extreme to generate/run a wireless network (Do I need an Airport Card in order to generate/run a wireless network? Doesn't the AE actually do that?), connect the desktop Mac to the network via Ethernet (I shouldn't need an Airport Card to do that, should I?) and connect a 'Roku Player (802.11g capable) to the network via wi-fi.
As far as I know, this should be possible.
Basic steps/as I understand them:
A. Connect ethernet from cable modem to AE.
B. Connect ethernet from AE to desktop Mac.
C. Create the wireless network using desktop Mac and Airport Utility.
D. Restart AE to start the wireless network running.
E. Connect Roku to wireless network over wi-fi.
I have no problems with A & B. Once the AE is connected to the desktop Mac, I'm able to get internet via ethernet as it passes through the AE. I can then create a wireless network (step C.) using the Airport Utility (and setup assistant). The problem starts after I've configured the wireless network.
Once I've configured the wireless network, the Airport Utility software prompts me to restart the AE in order to start the wireless network.
As soon as I restart the AE, my desktop Mac tries to connect to the 'wireless' network, even though it's already connected via ethernet. I don't have a wireless card in the Mac, and I don't want to connect the desktop using wi-fi/wireless. It's connected via ethernet, works fine during configuration, and I don't ever anticipate a desire to connect the desktop via wi-fi.
No matter what I do, I can't get the desktop to connect via ethernet. The only network connection option I'm offered is 'Rescan'. O.k. the desktop can't find the wireless network (because it doesn't have a wireless card), and I'm unable to continue with the Airport Utility. I can't make any further changes to the network (the options to manually change the network configuration are not available as the desktop Mac cannot currently talk to the AE - It's still trying to connect wirelessly), and the desktop has no internet connection as it's trying to connect wirelessly.
*How can I...*
*Setup/run a wireless network, while keeping the desktop Mac connected via ethernet?*
I'm perfectly willing to factory reset the AE and start over.
Any help appreciated.
Thwarted by the network.
- Robert

My Father in law has my old computer; It's a PowerMac G5 (Dual 1.8GHz CPUs) running OS 10.5.8), connected to internet via cable (TimeWarner) modem. It does NOT have an Airport or Airport Extreme card installed. The computer works fine, and I don't believe that I 'need' an Airport Card in order to use the Airport Extreme (it's a brand new/refurbished model) in the manner described below.
That is correct, you could connect the PowerMac G5, via Ethernet, to the AirPort Extreme Base Station (AEBS) or any other wired router for Internet access. You do NOT need an AirPort Card for wired access ... ONLY if you want the G5 to connect to a wireless network.
I would like to use the Airport Extreme to generate/run a wireless network (Do I need an Airport Card in order to generate/run a wireless network? Doesn't the AE actually do that?)
That is correct, the AEBS is a wireless router that can provide a wireless network. The AirPort Card, on the other hand is a wireless adapter used to allow a Mac to connect to a wireless network, created by any wireless router ... not just those provided by Apple.
As far as I know, this should be possible.
Basic steps/as I understand them:
A. Connect ethernet from cable modem to AE.
B. Connect ethernet from AE to desktop Mac.
C. Create the wireless network using desktop Mac and Airport Utility.
D. Restart AE to start the wireless network running.
E. Connect Roku to wireless network over wi-fi.
Yes, these are all good assumptions.
As soon as I restart the AE, my desktop Mac tries to connect to the 'wireless' network, even though it's already connected via ethernet. I don't have a wireless card in the Mac, and I don't want to connect the desktop using wi-fi/wireless.
Do you actually have an AirPort Card installed in the G5 now? If so, then it might be possible that the "firing order" for network connectivity has AirPort at the top of the list under System Preferences > Network. Just change the order to have Ethernet at the top and disable AirPort to ensure that the G5 connects by Ethernet only.

Wireless card seems to be not working

Hello everyone,
I haven't had any problems with my wireless card for my Macbook Pro since I purchased it, but something seems to be acting up now. Here's the situation...I went away for the weekend, took my laptop with me, didn't use the internet at all. Then I came back to my wireless card not working. It has a self-assigned IP address of 169.254.183.17. I did some reading on it and what people of said is that when you have this particular address your computer can't access the internet. I have power cycled both the router and modem correctly without any success.
I have another laptop that is windows based that can connect wirelessly so I've identified that it isn't a router problem. The thing that baffles me is that I can hard wire my Macbook into the router and achieve a connection...any suggestions on what I should try next?
Thanks in advance.
Message was edited by: Jaden Pretzlaw

Thanks for replying,
I did go into advanced settings to see what was up. And the TCP/IP tab was the area that I was focusing on. Okay...I did try renewing the DHCP lease and it keeps giving me the unusable IP address. One potential problem that may be contributing to this fiasco is that I think the modem in my household is also a router (which we're just using as a modem). The modem isn't mine so I'm not sure how it was setup. I don't believe that modem is activated to give off a wireless connection. I don't know why it would be a problem because I was connecting to the router just fine before. If the windows based laptop can connect just fine, it wouldn't be the router...(just thinking out loud here).
I was given an option by one of our IT personal at the office that I work at...he said that I could completely remove the network from my saved list and re-enter it. He also said that I would have to delete some temporary files that are saved in a hidden folder that are "preference" files for that specific network. I wasn't able to find that folder, and I did try deleting the network but it didn't seem to fix the situation. If I could simply just go back to square one, as I did when I first connected to the network I'm sure it would fix everything.
I hope this wasn't too long to read, hopefully it gives good insight.
Regards
Message was edited by: Jaden Pretzlaw

Intel Wireless Card doesn't work with Linksys?

My wired computer works great with the WRT54GX2, but my wireless cannot hold a signal for very long. Support says they can't help me because I have a Intel wireless card. Intel does not support for that card anymore and I can't see where to buy a Linksys card. Please, help.
Bonnie

check the link for the linksys retailers
Retailers
Message Edited by Maximus on 07-21-2006 05:48 PM
I do know everything, just not all at once. It's a virtual memory problem.

Wireless card

Similar Messages

Maybe you are looking for