Strange network prob setting up WRK54G

Hi,
I have spent an afternoon setting up a WRK54G (not WRT) router and have come across a very strange networking problem. I am using the router to setup a small network in the office off one of the LAN points. I connected the router up and set it up with a static IP address and gateway for the company LAN so setup looked like (Office LAN socket - WRK54G - PC). Once done the internet connectivity using a pc connected to the router via cable was very slow . I replaced the router with a switch (simple 4 port netgear switch) just to get through the day and set my PC back up to the static IP. Later that day I tried to set up the router again and forgot to remove the switch so the setup was (Office LAN socket - switch - WRK54G - PC). To my surprise the whole thing worked. When cleaning up the cables I noticed the switch was still in the chain so I removed it and the same problem of slow speed and packet loss came back.
Any ideas????
Can the WRK54G only take an internet connection from cable or DSL modem? Should there be a problem due to it connecting to a o a LAN?

I have similar settings as yours and it works fine for me.
I guess the dns or gateway is creating porblem for you. I have hardware firewall installed in our company so the lan ip of the firewall becomes geteway for me. so if I set up static ip for the router and give the gateway as the lan ip of the firewall plus the DNS of the ISP it works great.

Similar Messages

2nd Computer Requires a Manual Wireless Network Connection Setting on Powerup

2nd Computer Requires a Manual Wireless Network Connection Setting on Powerup
On power-up, my 2nd computer, a 3 yo IBM R51, requires that I open the Network Connections window, then set the Wireless Network Connection Properties under the Wireless Network Tab, clicking on "Use Windows to configure my wireless network settings", before the automatic connection launches to the WRT150N v1.1 router signal.
I just bought the router and have the latest firmware.
My primary computer does not require the above settings change every time.
Is there a selection I can make so this is automatic on power-up or restart of my 2nd computer?

It was already set to automatic on both extended and standard tabs.
For a good measure, I set it to disable, applied, then reset it to automatic and applied again. Still does same thing.
I notice that if I double click on the small icon for the Intel ProWireless Network Card, I get a Wireless Connection Status Window.
This window has a Wireless Settings section where it seems to have a possibly obsolete "Current Location Profile" called ssnetwork (the name of my old network on my old D-Link router that I just changed out for the Linksys.
Anyway, the Network Name (SSID) field is now blank but when it first came up, it had the new name of the network I'm using.
Do you know how I access this "Current Location Profile" so I can edit it and possibly enter my new network name?
There is a button at the bottom of the screen called "Modify WLAN Settings" that I click but nothing launches when I do so.
Now that I manually did the connection setting, my network name appears in the "Current Location Profile."
Ted

All Network Volumes set as Login Items open in Finder on EVERY startup

...after updating to 10.5.8
I have a Mac running on an otherwise all PC network. Before updating to 10.5.8 I had 5 network volumes set to "connect" on startup automatically (System Prefs / Accounts / Login Items). This worked perfectly and connected to these volumes silently without me having to ever worry about it. I didn't even have to check the "Hide" boxes.
After updating to 10.5.8 however, it became completely annoying. Now it still connects to these volumes, but opens up every single one in Finder upon every startup. That's 5 windows I have to close every time I startup my computer. It may not sound like the worst thing in the world, but mind you I have to log out and back in every day for work. Even checking the "Hide" checkboxes don't do anything.
Anybody experiencing the same problem? Anybody know a workaround or fix? My company has a rather large and complex network so staying connected to certain folders that I use is a must. Thanks.
Screenshots:
Login Items - http://img.photobucket.com/albums/v326/Magick0ne/Other/Login_Items.jpg
Every Startup - http://img.photobucket.com/albums/v326/Magick0ne/Other/Finder_Windows.jpg
Message was edited by: Pifman

Pifman wrote:
Thanks to both of you. I guess the search I ran wasn't good enough as I didn't find the discussion that you posted.
One of the possible workarounds posted there was to use a third-party program that I found difficult to understand and use. Instead I took V.K.'s advice and made an AppleScript and then made that script launch at login. Works like a charm.
Only difference is that my AppleScript isn't located in the Utilities folder (10.5.8), instead I got to it by going to Applications / AppleScript / Script Editor.
sorry, my mistake on the location.
Then I made a script and saved it as an application. I then put that application in my Login Items (System Prefs / Accounts / Login Items).
If you're having trouble finding the mount volume (or server) address, here's how you can find it: If you are currently connected to the volume(s) that you want to use, left-click it and hit Cmd+I (or right-click, Get Info). Use the address next to "Server:" - That's it!
Hopefully Apple will fix this bug soon so people don't have to make AppleScripts just to make the OS work correctly.
I wouldn't bet on it for leopard. leopard development has stopped now after snow leopard has been released. historically, Apple only releases security patches for old OS versions once a new one comes out. Interestingly, this bug is present in snow leopard too! or maybe they don't consider it a bug and this is how it should work. one can make a case for this, I guess.

HT4623 When I joined my wireless network I set authentication required to on and di not eneter a username or password. I then went into safari and as requested entered my username and password. Now,however the iPod is remembering my credentials. How do

When I joined my wireless network I set authentication required to on and di not eneter a username or password. I then went into safari and as requested entered my username and password. Now,however the iPod is remembering my credentials. How do I clear my credentials?

Go to Settings>Safari and Clear History, Cookies and Data
Also go to Settings>Safari>AutoFill and Make sure that Names and Passwords are OFF and Clear All.

Network connecting setting in VM

The below issue could be duplicated in VM. But this issue is about signed name. If there are any suggestion or solution, this is very very appreciated.
There is a windows service exe (vc6 code) which will call some COM interface (.net code, signed name dll file).
Scenario 1:
1) The network connection of the virtual machine settings is Host-only.
2) The COM dll is signed name file.
It costs lots of time (more than 1 minitues) to create com instance.
Scenario 2:
1) The network connection of the virtual machine settings is Host-only.
2) The COM dll is un-signed name file.
It costs less than 1 second to create com instance.
Scenario 3:
1) The network connection of the virtual machine settings is Bridged. And the host computer had never had access to Internet.
2) The COM dll is signed name or un-signed name.
It costs less than 1 second to create com instance.
What's the relationship between network connection setting and signed name?
Thanks Very Much!
Scott

Any words?
Thanks
Scott

HT5569 When I attempt to choose the wi fi network I set up my iPhone message says "unable to join the network." It's my network!

Recently, my iphone 4s lost connection with the wifi network I set up on my imac desktop. The message I receive is "unable to join the network..."
Can anyone offer a solution to this problem? Thanks!

Oh, so the problem has nothing at all to do with the iPhone ... it is that you cannot remember the network password! No wonder the iPhone cannot join the network.
Why not simply destroy the network and set up a new one with a password you remember?

Really strange network issue that is specific to OS X 10.6.8

Really strange network issue that is specific to OS X 10.6.8 on both 2 iMacs and an older intel Mac Pro.
Any system running 10.6.8 is achieving on average 15 –20 mb a sec transfer rates regardless of drive speeds, cables, network activity etc.. I've spent some time removing any cable , drive speed, router issues to the point where one machine dual boots into both 10.6.8 and 10.6.5
The 10.6.5 system has network speeds of 60mb – 80mb p/sec transfer rates.
Our older 10.5.8 PPC mac gets 80mb and my 2011 Macbook Pro 10.7.2 hits 60mb – 80mb consistently as well.
Any idea what the cause is?
Cheers

Since your other Mac running 10.5.8 is not affected, you know that your AirPort router is functioning correctly.
What changed on your Mac? This seems like a post for either the Mac OS X v10.6 Snow Leopard support area, or the support area for your model of Mac.
We normally handle questions about the AirPort Express, AirPort Extreme or Time Capsule in this area, but you can certainly wait to see if you receive a response here.

HT4199 I have a new iPhone 4s. I have a home wi-fi network using Cisco Linksys2000 router with all settings per this article - phone will not see network if set to 5 GHz channel width - solution?? 2.4 works but is not optimal with other devices in home

I have a new iPhone 4s. I have a home wi-fi network using Cisco Linksys2000 router with all settings per this article - phone will not see network if set to 5 GHz channel width - solution?? 2.4 works but is not optimal with other devices in home (computers; tivo). Have others seen this? Any advice is much appreciated.

Stephen Spark is right - your best alternative is to use a simultaneous dual band wireless router like the AirPort Extreme. Your Cisco Linksys2000 is not a dual band router, meaning that it will be constrained to operate at the slowest speed of all the devices on your network.
The AirPort Extreme's dual networks will support all your 802.11n devices as well as all your 802.11b/g devices on both the 2.4 and 5 GHz frequencies simultaneously.

Strange network freezes when wrong time is set (with transmission-gtk)

Hi!
After transmission-gtk running for a while, the network doesn't work any more, not even the connection to the router. Even after closing transmission-gtk, the problem persists until I disconnect from the network (using wicd / wpa atm) - or wicd freezes and refuses to start again. Trying to use ifconfig / iwconfig makes the terminal freeze (not recovering with ctrl+c), other tty/vty's still work. System won't shutdown / reboot after this happens, the tty that gave the command just freezes.
Not sure where to start here... can't use iwconfig/ifconfig... can't look up stuff online while I'm on the machine trying to work this out... any hints?
Thanks!
edit: some random information that I don't think contains anything useful:
wlan0 IEEE 802.11bgn ESSID:"wlanx"
Mode:Managed Frequency:2.412 GHz Access Point: 48:5B:39:E8:54:98
Bit Rate=54 Mb/s Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=47/70 Signal level=-63 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:67 Missed beacon:0
wlan0 Link encap:Ethernet HWaddr 54:E6:FC:88:C9:72
inet addr:192.168.144.56 Bcast:192.168.255.255 Mask:255.255.0.0
inet6 addr: fe80::56e6:fcff:fe88:c972/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:16365 errors:0 dropped:0 overruns:0 frame:0
TX packets:12310 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:8815506 (8.4 Mb) TX bytes:2072550 (1.9 Mb)
(thats when everything works fine of course...tools don't work when this error occurs )
edit:
After looking for the fifth time, found a semi-interesting part in messages.log (thats a few minutes around the problem occuring, with failed reboot etc...):
Dec 9 16:52:22 localhost kernel: [ 1501.828150] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Dec 9 16:52:23 localhost kernel: [ 1502.096812] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Dec 9 16:52:23 localhost kernel: [ 1502.350614] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Dec 9 16:52:26 localhost kernel: [ 1504.914410] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Dec 9 16:52:26 localhost dhcpcd[4723]: version 5.2.12 starting
Dec 9 16:52:26 localhost dhcpcd[4723]: wlan0: broadcasting for a lease
Dec 9 16:52:29 localhost dhcpcd[4723]: wlan0: offered 192.168.144.56 from 192.168.11.11
Dec 9 16:52:29 localhost dhcpcd[4723]: wlan0: acknowledged 192.168.144.56 from 192.168.11.11
Dec 9 16:52:29 localhost dhcpcd[4723]: wlan0: checking for 192.168.144.56
Dec 9 16:52:34 localhost dhcpcd[4723]: wlan0: leased 192.168.144.56 for 600000 seconds
Dec 9 16:52:34 localhost dhcpcd[4723]: forked to background, child pid 4746
Dec 9 16:54:45 localhost kernel: [ 1644.059228] transmission-gt[4941]: segfault at fffffffffffffff7 ip 000000000044d347 sp 00007f79b69feac0 error 4 in transmission-gtk[400000+b7000]
Dec 9 17:03:20 localhost dhcpcd[6704]: sending signal 1 to pid 4746
Dec 9 17:03:20 localhost dhcpcd[6704]: waiting for pid 4746 to exit
Dec 9 17:03:20 localhost dhcpcd[4746]: received SIGHUP, releasing
Dec 9 17:03:20 localhost dhcpcd[4746]: wlan0: releasing lease of 192.168.144.56
Dec 9 17:03:20 localhost dhcpcd[4746]: wlan0: removing interface
Dec 9 17:03:21 localhost kernel: [ 2160.076551] cfg80211: Calling CRDA to update world regulatory domain
Dec 9 17:03:21 localhost kernel: [ 2160.423451] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Dec 9 17:03:24 localhost kernel: [ 2163.236352] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Dec 9 17:03:26 localhost kernel: [ 2165.659989] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Dec 9 17:03:27 localhost kernel: [ 2165.947971] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Dec 9 17:03:29 localhost kernel: [ 2168.505313] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Dec 9 17:03:30 localhost dhcpcd[6860]: version 5.2.12 starting
Dec 9 17:03:30 localhost dhcpcd[6860]: wlan0: broadcasting for a lease
Dec 9 17:03:32 localhost dhcpcd[6860]: wlan0: offered 192.168.144.56 from 192.168.11.11
Dec 9 17:03:32 localhost dhcpcd[6860]: wlan0: acknowledged 192.168.144.56 from 192.168.11.11
Dec 9 17:03:32 localhost dhcpcd[6860]: wlan0: checking for 192.168.144.56
Dec 9 17:03:38 localhost dhcpcd[6860]: wlan0: leased 192.168.144.56 for 600000 seconds
Dec 9 17:03:38 localhost dhcpcd[6860]: forked to background, child pid 6883
Dec 9 17:07:35 localhost -- MARK --
Dec 9 17:21:01 localhost dhcpcd[8752]: sending signal 1 to pid 6883
Dec 9 17:21:01 localhost dhcpcd[8752]: waiting for pid 6883 to exit
Dec 9 17:21:01 localhost dhcpcd[6883]: received SIGHUP, releasing
Dec 9 17:21:01 localhost dhcpcd[6883]: wlan0: releasing lease of 192.168.144.56
Dec 9 17:22:22 localhost shutdown[8824]: shutting down for system reboot
Dec 9 17:22:22 localhost init: Switching to runlevel: 6
Dec 9 17:22:23 localhost acpid: exiting
Dec 9 17:23:54 localhost kernel: [ 0.000000] Initializing cgroup subsys cpuset
Dec 9 17:23:54 localhost kernel: [ 0.000000] Initializing cgroup subsys cpu
Last edited by whoops (2011-08-14 07:51:53)

I have had problems where my connection would drop "coincidently" while downloading torrents. I use ipblock to block unwanted ip addresses, force encryption both ways, and use tcpkill (pretty sure it is in the "dsniff" package) to block foreign ports that seem suspicious to me. Also, I have noticed that if there is a lot of connections my network will almost halt and if I limit the connected number of connections per torrent after the swarm gets going then it will first drop peers instead of seeds so it does not really seem to effect speed either. I do not use transmission so I do not know all the particulars there ( using deluge) but there should be similar settings for encryption as well. If doing a lot of downloads I also reset my router (unplug it) for about 5 minutes when I am done and reboot just to be sure. If you think that your troubles may be caused by your isp or an anti-p2p group I would definitely give the above a shot.
Last edited by dodo3773 (2011-08-14 04:00:49)

Server 2008 R2 Strange Network/Client Issues

Hi All
I'm facing some strange things with a fairly recently deployed 2008 R2 DC machine.
It's a Dell R720 (16GB Ram dual socket). The NIC is an Intel X540 10Gb adapter. The network switch is a Netgear XS708E 10Gb 8-port, with 3 Win7 clients connected at 1Gb into the same switch. The server runs AD, DNS, DHCP and file services.
Pretty simple, as it's a processing suite deployed at a remote location.
Network connectivity at the client end can be very patchy with disconnects and slowdowns in the file copy speed between client and server (<1mbs). Sometimes the clients refuse to even connect, and
show no network connection.
I am trying to track down the problem. It's either something in the server eg DNS or a faulty switch. If I plug my laptop into the Netgear switch it connects etc, so I'm not sure that's the problem.
The only other thing I can think of is that I had attempted to multi-home the server, which I subsequently found was not best practice. I have since removed the second adapter, but maybe some detritus
remains in DNS?
I will re-run the DNS config wizard to freshen that up and report back.
Does anyone else have some pointers for me?
TIA

Hi,
“Network connectivity at the client end can be very patchy with disconnects and slowdowns in the file copy speed between client and server (<1mbs).”
Could try test the copy speed between Win7? Personal experience maybe your switch connection rate set up correct, or replace your cable as the crosswire then monitor the status.
More third party information:
Choose the Right Switches for Your Local Area Network Upgrade in 2011
https://www.adcapnet.com/blog/choose-the-right-switches-for-your-local-area-network-upgrade-in-2011/
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Strange networking question

I have two computers (they are called IOMS-design and Beast). I'm trying to connect the two using shared variables and front panel binding.
When I set up the Beast as the server, it works fine. Everything binds to the variables on Beast.
However, this is the opposite of what we want, so we tried to reverse it. This is where the strangeness comes in. IOMS-design can see everything on itself and the Beast, but the Beast can only see it's own contents, not IOMS-design's. I've attached two images to illustrate my problem.
I don't think it's strictly a Windows networking issue because the computers can see each other in the Networking window on Windows. Also, like I said, it works with the data going one way, but not the other.
I think it's a LabVIEW configuration issue because of this.
FYI both computers are running Vista and LV8.6.0
Message Edited by elset191 on 02-20-2009 09:03 AM
Tim Elsey
LabVIEW 2010, 2012
Certified LabVIEW Architect
Attachments:
Beast-view.jpg ‏36 KB
IOMSDesign-view.jpg ‏41 KB

Nevermind.
Somehow I overlooked the fact that Beast had Norton
Tim Elsey
LabVIEW 2010, 2012
Certified LabVIEW Architect

Strange network problem - it hangs.

Hello,
I have experienced strange problem with network. I'm searching for solution (in Internet) for about a month.
What is happening:
When I start browser and start to browsing, network sometimes hang - when I click on link nothing is happening - I have to refresh page two or three times to get it back. Sometimes it hangs on sending a request, and sometimes on downloading page content.
I'm using Kadu as my IM and it gives me communication errors every one or two minutes, very often it drops messages.
When I installing sometimes, or upgrading system pacman reporting download error - when I download 10 packages always about three have those errors, then I must download them again.
Ping work's well.
ping -c 5 google.com
PING google.com (74.125.43.99) 56(84) bytes of data.
64 bytes from bw-in-f99.1e100.net (74.125.43.99): icmp_seq=1 ttl=52 time=46.2 ms
64 bytes from bw-in-f99.1e100.net (74.125.43.99): icmp_seq=2 ttl=52 time=47.0 ms
64 bytes from bw-in-f99.1e100.net (74.125.43.99): icmp_seq=3 ttl=52 time=46.5 ms
64 bytes from bw-in-f99.1e100.net (74.125.43.99): icmp_seq=4 ttl=52 time=46.4 ms
64 bytes from bw-in-f99.1e100.net (74.125.43.99): icmp_seq=5 ttl=52 time=46.1 ms
I have try this solution:
http://wiki.archlinux.org/index.php/Con … ling_issue
but this also won't work.
Problem appears on lan and on wlan (tested on two usb cards) connections - I have also tried connection by wicd and networkmanager - same problem.
Then I have borrow laptop from my friend, installed and configured Arch - and same problem.
I have buy some celeron (S478 2,66ghz) PC (for test) - and I have experienced same problem here.
I have tried opendns, google dns, and I have setted dns same as my router IP, same problem remains on dhcp.
On every system I have tried it on firefox, chrome and opera.
So, you can ask what is strange in this issue? Strange thing is that I have tried install Ubuntu, Fedora, Opensuse on those three machines and they don't have this error. Pages download normally, Kadu don't drops messages. Please don't tell me to use one of those distro I want to stay with Arch.
Please help me to solve this. Maybe I'm doing something wrong with configuring network.
Best regards.
P.S sorry for my english, it is not my native language.
Last edited by szamot83 (2010-09-01 17:34:27)

I think it's not the same, try doing 'lsmod | grep -i ipv6' and see if the module is still loaded, you can also check the output of ifconfig for inet6 addr to check if it is trying to use ipv6.
If the problem is not caused by trying to use ipv6 with a router that doesn't like that then I have no other ideas.

[SOLVED]MSI P31 Neo -mobo and strange network problems

I can't get network to work properly with this MSI-mobo's integrated lan chip.
When I boot from Arch install cd r8169-module is loaded and I can get ip via dhcp. Strange thing is that I can access http but not ftp. When I change transfermode to passive from links ftp works. But during Arch install setup I can't access the repos.
When I boot to Arch after install network doesn't work at all. Only thing I get is resolv-errors when I try to use wget or pacman. R8169 module is loaded at boot and Ifconfig shows that I have ip assigned to eth0.
I also tried with 3com's 3c509 network card that I had laying around and I have exactly same network problems with it as I have with r8169.
I am really going out of my mind with this. I have a laptop with via's network chip and I've never had any network problems with it and Arch. I haven't changed anything in my routers setup and I just tried and the networking on my laptop works just fine.
I also tried Ubuntu Hardy on this desktop machine and networking works ok. Ubuntu also loads the r8169 module as Arch does.
Last edited by Aakko (2008-05-18 21:18:29)

Quote from: techie5487 on 24-January-08, 07:34:41
UPDATE:
I tried booting with 2 RAM Chips and it works great! This seemed to be the problem.
The ram IS double sided which would explain it.
If you are wanting some more system specs, just ask and I will try and get the most I can.
Del UK:
If I could run 4gb it would be great but I cannot seem to find the SPD in bios. My BIOS is American Megatrends Inc. v02.61 so it would be great if you could help me with that!
If all else fails I might either just settle with 2GB or buy some new RAM chips. Can anyone please tell me some Ram chips which would be able to give this mobo 4GB?
Thanks
techie5487
Done
2 Gb in
Into bios
SPD off
Set to 5-5-5-15
Save settings
Power off
Install extra 2 x 1Gb modules into slots 2 & 4
Power system up
4Gb detected................. slow post not fast
3.25Gb checked
1 second delay
4096Mb
3.25Gb extend
768Mb in +4Gb
System sees 3.25Gb

K7N2 Delta ILSR Strange network problems

K7N2 Delta ILSR
2500+ AMD Barton
Radeon 9600 PRO
Windows XP
Hi there,
My network was working fine yesterday but now whenever I plug a cable into the onboard network card, my computer starts having these strange flucuations...Every few seconds the CPU usage jumps from 0% to about 50% which causes the system to freeze for a second, making it a real pain to do anything.
Does anyone have any idea whats causing this?
Thanks,
Shim

Quote
Originally posted by deftonie
The kingston memory I have is on the memory compatibility list.
kingston removed k7n2 from their supported list.
kingston is not on the Good Memory Choices for ALL K7N2 nF2 released boards
for some reason msi have not removed kingston from their supported list.
Quote
Originally posted by pseudemys
So (and I'm addressing the question in particular to Raven): shoud i wait for a some kinda accident, crash, whatever sooner or later? I'm really scared about such things. You know... everything seems ok and then, suddenly, a nasty surprise. Which is the problem with kingston and k7n2 series? Further, I'd like to buy another 512 M stick and honestly it seems more sensible to me to mount two equal sticks. And I feel somewhat stuck...
a memory can be incompatible but still work.
alot of people buy any memory they can and throw in and it may work.
but it can start crashing after installing some program or updating bios or drivers.
thats the reason i posted the memtest program.
worry about a crash....no reason for that as you self said memtest reported no errors prime95 no errors and doom3 worked good.
kingston uses many different chips on their memory and its those chips that is the problem.
one guy found out that on the specific memory he bought kingston used 3 different chips on.
only 1 of them worked good on k7n2.
so a 33% chans of success in getting a good module is considered bad.
so write down the numbers on the chips and take it with you to the store and compare it to the memories they got.

Solution to Airport Extreme Base Station + Airport Express networking probs

I've been investigating this for 3 straight days after inadvertently destabilizing my network. There are tons of posts discussing a variety of issues, all of which seem related. My goal here is to provide links to other relevant posts and explain what I ended up doing to get things to work.
First, the background. You can skip below to SOLUTION if you don't really care... However, I highly recommend you take the time to read everything, as you'll get other useful information in the BACKGROUND section. I'm guessing many of you have similar, related problems so BACKGROUND might help provide context (and solutions) to some things you are seeing...
MY SETUP:
AirPort Extreme Base Station (AEBS) of type b/g (round one, not square one), connects to the cable modem, and creates a WDS network that is then shared across two standard AirPort Express (AEX) units (100megabit, not the gigabit ones). One AEX serves as a relay unit that accepts clients, the other serves as a remote unit that also accepts clients. The intent is to show a single network throughout the house and let users log on to one network and move between networking units without having to switch from network to network.
I have a variety of networked devices throughout the house all running on the same network (2 Mac Pros, a Powerbook G4, a Mac Mini, an Apple TV, a Windows XP laptop, two iPhones, two wifi printers, and a 5-unit Sonos system, plus the AEBS and two AEXs). Yeah, I'm a geek.
The Mac Pros are both running 10.4.11, and the Powerbook is running 10.5.2.
AEBS is running firmware 5.7
AEXs are running firmware 6.3
All Macs were initially accessing configs via the recently released AirPort Utility 5.3.1. More on that later.
BACKGROUND:
I've had this network setup working for about a year now. Recently, I've been having poor network performance problems and came to the conclusion it was a LAN problem (ie. problem with my home network, as opposed to with my ISP). Upon initial investigation, I began by looking at my networking logs (via AirPort Utility 5.3.1). You get to those by selecting the unit in question, choosing "Manual Configuration", the selecting the "Advanced" tab up top with the "Logging and SNMP" sub-tab. Click the "Logs and Statistics" button therein for log details from that unit.
The first thing I noticed was "Administrative access denied to ff80::xxxxxxxxx" messages - a lot of them. I didn't recognize the ff80:: address in question, and so became concerned it was someone outside the network trying to hack one (or all) of the AEBS/AEX units. You can see threads discussing that investigation here:
"Hack or panic?" - http://discussions.apple.com/thread.jspa?threadID=1438486
"Administrative access denied" - http://discussions.apple.com/thread.jspa?threadID=1438865
Long and short of it is that the recent AirPort Utility 5.3.1 release (current as of March 13) seems to have problems (keychain) when attempting to access the AEBS and AEX units. The "Administrative access denied" logs actually refer to the client machine you are using when you try to read the logs. The ff80::xxxxxx address is simply the IPv6 address for the machine you are using; if you turn off IPv6 on your client machine, that address should switch over to begin showing a regular IP address instead (something like 10.0.1.xxx), which makes it easier to associate the IP to the machine. I explain how to deactivate IPv6 on both Tiger (10.4.x) and Leopard (1.5.x) here:
http://discussions.apple.com/thread.jspa?messageID=6814978#6814978
Anyway, in the process of investigating the "Administrative access denied" problem, I began tinkering with my AEX settings. Specifically, I ended up performing a hard factory reset (unplug unit, plug back in while holding down the little button with paper click/pen for ~10-15 seconds until light flashes green 4x then reverts to amber/yellow/orange). I began reconfiguring my entire WDS network using the newly updated AirPort Utility 5.3.1, and that's when the trouble started.
(If you are having problems seeing either your AirPort Extreme Base Station or AirPort Express, read this:)
In short, each time I thought I had properly configured things and then confirmed settings (kicking off a reboot on the AEX unit) the unit would restart with new settings but not properly join the WDS and not show up in the AirPort Utility list of units. More specifically, I would start with a "wiped" AEX and see both the AEBS and the AEX in my AirPort Utility list, but upon confirm/reboot the AEX would disappear and the AEBS would remain. However, that's not 100% correct. It seems that sometimes I would end up with the AEX and NOT the AEBS. Because both the AEX and AEBS were theoretically "hosting" the same network name (remember, WDS shares the network name across units) my auto-login feature for my client computer's wifi seemed to "jump on" whichever unit it first saw hosting the default network name for my house. In other words, it seems what was really happening was that I was ending up with two separate networks in my house, both with the same name but not talking to each other (as opposed to two units sharing the same network name and internet connection). The AEX would continue to blink orange/amber/yellow (whichever color it is to your eyes ) because it could not grab an internet connection -- and if I was on the network through that AEX unit I would not get internet. But if i was connected through the AEBS I would continue to have internet access. As far as my client computer (my Mac Pro) was concerned, I was on the home wifi network even if I was on the AEX rather than the AEBS -- it would show the home wifi network name as the name of the network it had connected to. But when I opened the AirPort Utility 5.3.1 I would see only the AEX (if I was connected through it) or the AEBS (if connected through it) -- a clear indication that the units were not truly sharing the same network.
I tried rebooting and reconfiguring the AEBS and AEX about 50 times (literally). I even tracked down an older version of the AirPort Utility 5.2.1 via this thread (see Tesserax post):
http://discussions.apple.com/thread.jspa?threadID=1067565
One interesting thing re: 5.2.1 is that the "Administrative access denied" errors summarized above disappeared. As explained in a post reference above, the going theory is that this a permissions/keychain problem new and unique to AirPort Utility 5.3.1. However, even though 5.2.1 does have a slightly different interface with different settings, I still couldn't get the WDS to work.
EVENTUALLY, I came across this post:
http://discussions.apple.com/thread.jspa?threadID=1422527
MuaddibOfArrakis walks through setting up a WDS from scratch, and the workflow is different than what is possible with either AirPort Utility 5.3.1 or 5.2.1. He's doing it with the old version of AirPort Admin Utility, which I fortunately saved a copy of many moons ago when I had somewhat-related problems with my WDS (since forgotten). In fact, it's a lot easier. What's nice about this older app is that it literally does the heavy lifting of "connecting" the AEBS and AEX units during the configuration -- it reboots both at the same time as the config is happening, and lets you choose from a list of available units to "add" to your WDS network. In short, it's a FAR SUPERIOR workflow even though some of the GUI isn't as intuitive as the newer AirPort Utilities that were designed to replace it.
SOLUTION:
If still have a copy of the AirPort Admin Utility follow the instructions from MuaddibOfArrakis here:
http://discussions.apple.com/thread.jspa?threadID=1422527
If not, try setting up your WDS network using AirPort Utility (hereafter AU), with these configs (take from my now-working network), as viewed through AirPort Utility 5.3.1.
I. Configure your AEBS.
Select the AEBS from AU, and choose "Manual Setup"
1. Under the AirPort tab up top:
a. Under "Base Station" sub-tab:
i.) assign a name for that specific unit, so you can later identify the specific unit from the list of units -- this is the name that will show up beside the unit in the AU list of configurable units. You can name it something like "kitchen", or "office". I have mine numbered, so XXXXXv1, XXXXXv2 etc where the XXXXX is the name of the shared network and the numbers help me tell the units apart. Just be sure you name each uniquely, and if you have several you might write the name on the unit itself.
ii.) pick a password for logging into that unit. This is different from the network password, its a security check to get in and change the configs on this unit later. Be sure to remember it in your keychain for the sake of simplicity, and write it down somewhere secure.
iii.) if you choose to set time automatically, pick a location that you will use consistently across all your units. I use time.apple.com.
iv.) uncheck "Allow configuration over Ethernet WAN port" unless you want to be able to remotely mess with settings -- which you almost certainly do not need to do.
v.) I left the "Options" button alone - no settings there.
b. Under the "Wireless" sub-tab:
i.) Wireless Mode: "Participate in a WDS network"
ii.) Network Name: this will be the name of your wifi network shared by all units, so be sure to remember what you pick. If you are already connected to this AEBS via wifi while you are making these changes, then you can use the same wifi name you already have set up -- you don't have to change it. Note that if you DO change it, after reboot your will LOSE connection to the network and have to reset your wifi settings on your client machine to match the new network/password in order to be able to access the network.
iii.) pick a Radio Mode. I'm using b/g compatible. You'll want to do the same, unless you are on the new gigabit AEX. I'm pretty sure about this, but not 100% -- others post if I'm wrong.
iv.) choose a Channel. This can be a more complicated procedure, but for now just pick something consistent across all your units. If you get everything working and find that you're having intermittent network problems, you could later try changing your Channel -- it can pick up interference from phones, microwaves, etc and changing it can help.
v.) I have wireless security set to WPA/WPA2 Personal.
vi.) Wireless Password is the password for access to your wifi network (not your unit itself). If you are connecting to your AEBS via wifi while doing this config, then you can use the same password you have already set up. Pick a good one unless you want other folks jumping on your wifi and stealing your bandwidth and/or credit card numbers . Remember it in your keychain and write it down someplace secure, because you'll need it for the other units too. As noted above, note that if you DO change it, after reboot your will LOSE connection to the network and have to reset your wifi settings on your client machine to match the new network/password in order to be able to access the network.
vii.) Click the "Wireless Options" button. I have my multicast rate set to 2mbps, transmit at 100%, timeout at 1 hour, and i have checked the "Create a closed network". This last step keeps your network from advertising itself to the outside world. Users can only find it by explicitly typing the network name into their wifi settings (e.g. AirPort -> Other... then enter Network Name, Security and Password). I leave interference robustness unchecked.
c. Under the "WDS" sub-tab:
i.) the AEBS should have it's WDS Mode set to "WDS main".
ii.) Check the "allow wireless clients" box on the AEBS; this lets you connect client machines to it directly too.
iii.) hit the plus button to add the Remote system (AEX). There are two types of configs for the AEX's - "remote" and "relay". Assuming you have 3 units like me (2 AEX and 1 AEBS) the key question is whether you will place each AEX within direct reach of the AEBS (remotes), or if you will have one AEX in the middle connecting to an AEBS on one side and an AEX on the other -- where the furthest AEX is out of reach from the AEBS (remote) and connects only to the AEX in the middle (relay). I'm using a relay setup. If you are using relay, you can still set up the AEX relay to serve client computers too -- it doesnt have to JUST relay. More on that later. For now, you want to add only AEX units that will talk DIRECTLY to the AEBS. So if you have a setup like mine, just add one (the one in the middle - the relay). If you have two remotes connecting directly to the AEBS, you will add them both here. When you hit the '+' button it will ask for both an ID and description. For description I use the name I'm assigning to each unique unit (as above, "kitchen" or XXXXXv1 or whatever you use). For AirPort ID, use the number listed on the AEX unit itself (not the number for "Ethernet", also on the AEX unit).
d. Under the "Access" sub-tab:
i.) I have it set to "Not Enabled". I'd suggest you start that way too, and you can go change it later if you get everything working correctly.
2. Under the "Internet" tab up top:
a. Under the "Internet Connection" sub-tab:
i.) Connect Using: Ethernet
ii.) Configure IPv4: Using DHCP
iii.) Ethernet WAN Port: Automatic (Default)
iv.) Connection Sharing: Share a public IP address
b. Under the "DHCP" sub-tab:
i.) DHCP Beginning Address: 10.0 . 1 . 2
ii.) DHCP Ending Address: 10.0.1.200
DHCP Lease: 4 hours
c. Under the "NAT" sub-tab:
i.) nothing should be checked;
ii.) nothing under Port Mappings either
3. Under the "Printers and Advanced" tabs up top:
Nothing special needs to be configured there.
THAT'S IT.
=============
I. Configure your AEX(s)
Select the AEX from AU, and choose "Manual Setup"
1. Under the "AirPort" tab up top:
a. Under "Base Station" sub-tab:
i.) pick a unique name for this unit, same logic as for AEBS
ii.) pick a password specific for accessing this unit, same logic as for AEBS
iii.) Set time automatically: be sure to use the same settings used on your AEBS
iv.) Options: no need to set any
b. Under "Wireless" sub-tab:
i.) Wireless Mode: Participate in a WDS network
ii.) Network Name: same name used for AEBS, this is the name of your wifi network
iii.) Channel: same as AEBS
iv.) All settings here (those above, plus Security and Password & in Options button) should be the same as for AEBS settings on this tab
c. Under the "WDS" sub-tab:
...if AEX is "in the middle" (as described above):
i.) WDS Mode: WDS relay
ii.) Allow wireless clients: check (unless you only want to bridge between the edges without letting folks connect on this AEX in the middle)
iii.) WDS Main: set to the AirPort ID (aka MAC address) for the AEBS. You can find it on the bottom of the AEBS, either labeled as such or at the bottom beside the logo of a wireless signal (square logo, with semi-circles mimicing a radio signal).
iv.) WDS Remotes: click the '+' to add any AEX's that will connect to this relay rather than directly to the AEBS. Same deal as above, use the name in the description and use the AirPort ID from the side of the AEX (not the Ethernet ID).
.....if AEX is connecting to a relay ("on the end", as above) or if there is no relay and AEX connects directly to the AEBS:
i.) WDS Model: WDS remote
ii.) Allow wireless clients: checked
iii.) WDS Main: if connected to a relay, use the AirPort ID of the relay AEX. If connected to the AEBS directly, use the AirPort ID of the AEBS
d. Under the "Access" sub-tab:
i.) MAC Address Access Control: Not Enabled (for now, you can change later)
2. Under the "Internet" tab up top:
a. Under the "Internet Connection" sub-tab:
i.) Connect Using: AirPort (WDS) -- should be selected and gray'ed out.
ii.) Configure IPv4: Using DHCP
iii.) Ethernet WAN Port: Automatic (Default)
iv.) Connection Sharing: Off (Bridge Mode)
3. Under the Music, Printers and Advanced tabs up top:
Nothing special needs to be configured there. You can worry about AirTunes settings later...
That should be it. I'd recommend setting up the AEBS first, then the relay (if applicable), then the remotes. Initially, you can bring each unit in the same room with you for configuring. After configured and restarted the AEX should blink then turn solid green. If it turns green you should be good to go.
HOPE THIS HELPS. As noted above, I did not config through AirPort Utility 5.3.1 so I haven't tested this procedure through that app. However, after getting my network to work I went back and transposed all settings into this post to help others. Please provide feedback on whether or not this is working, so we can collectively try to move towards a setup procedure that works for everyone....
Good luck!
Message was edited by: b.byrd

I'm not convinced that the problem lies in Airport Utility. This same thing was happening to me, nearly exactly as you describe it. The thing is that with me, the problems clearly started when I updated the firmware in my Airport Express (n). That's when all the wacky stuff started happening. Sometimes it would show up in AU, sometimes it didn't and even if it didn't, I could still access the internet through it.
But as you said, the problems got really bad when another Express (b/g) was put on the network with it. Even when it did work, the (b/g) would make it impossibly slow.
You know more about this than me, and clearly have more patience if you've restarted the network fifty times. I gave up at about ten.
In any case, your solution is more of a work around and if you're still having that slow connection problem, I'm not sure you've got it. But thanks for your reporting of this. At least I know I'm not crazy.

Strange network prob setting up WRK54G

Similar Messages

Maybe you are looking for