Terrible speed when connecting two AEBS

Hello,
I've noticed that I get terrible speeds when connecting two AEBS, one FE and GE.
My setup is as follows:
Broadband connection -> Linux router -> AEBS(GE) --- wireless --- AEBS(FE) -> MacMini
Using my macbook (n-enabled) as reference I've noticed that as soon as the FE conects to the GE I loose roughly 70% of my bandwidth (from ~90mbit to ~25mbit). I got these figures by transfering a large file using FTP and moitoring the bandwidth use on my linux routers internal interface using nettop. I've tried switching places with the basestations with the same result. I've also tried all four different radio modes.
Any advice?

A drastic drop in bandwidth is to be expected when you are using one to wirelessly extend the other. This is because every bit of data has to be transmitted wirelessly twice. Once from the main base station to the remote/relay and then once again from the remote/relay to the client.

Similar Messages

Windows XP not finding NTFS partition when connected to AEBS

Here is my setup:
I have the current AEBS with firmware 7.4.1 connected to a Windows XP w/SP3. I also have my Macbook Pro running wirelessly as well as another XP laptop. I have wireless connections, a bit slower than I had hoped as I get further away from the AE but its OK.
I also have an Acomdata Pure Drive 1tb connected to the AE. I partitioned the drive half HFS+ and half NTFS. I confirmed and re-confirmed that both partitions are OK by connecting them via USB to all of my machines.
When connected to AEBS, the hard drive appears as a shared device rather than as a hard disk on my Macbook pro, which was not what I expected but is ok. Only the HFS+ partition appears, which is as expected.
However, on both windows machines, the HFS+ partition is also the only one that appears, and the file structure under disk properties shows as FAT32! I've searched and have been unsuccessful in getting the XP machines to locate the NTFS partition. Can anyone help?
Mahalo,
Mike

Thanks again for the replies, and I have a follow up question. Apologies in advance since I am a noob with Macs.
I reformatted my USB drive with one HFS+ and one FAT32 partition. Works great on my Macbook (I formatted using Disk Utility), both partitions are visible as shared drives.
On one of my XP laptops, both partitions also appear, and I am able to copy files to both, even the HFS+ formatted partition. When I check formatting in My Computer, both partitions indicate FAT32. When I check formatting on my Mac, it indicates HFS+ and FAT32, respectively.
I expected that the Mac would be able to use both drives, but I expected that only the FAT32 drive would be write-accessible on the XP. So what did I mess up this time?
Mahalo,
Mike

IMac 10.6.8, Snow Leopard with iTunes 11.0.1. loss of wifi speed when connecting a Bose Sound System via bluetooth

Hello, I have an iMac 10.6.8, Snow Leopard with iTunes 11.0.1. When connecting my Bose Sound System via bluetooth the wifi downloadspeed goes from snappy to a crawl, disconnecting the bluetooth connection, the downloadspeed goes up again. Don't have this problems with the Sound System when connecting it to my iPad. I like to mention too, that the downloadspeed of my iPad is always better than of my iMac. Are there any experiences concerning this problem? Thank you in advance.

UPDATE - PROBLEM SOLVED!!!!!!
You can thank me later - after an hour on the phone, I finally got through to a Senior Engineer.
Apperently the issues lies with GRID VIEW.
Open your Itunes, Click on TV SHOWS, then quickly change your view from GRID VIEW (Defaults to this) to List View and Viola!
We tested it out on the phone just minutes ago, my problem is solved and I suspect if you guys try this yours will be too.

Can't get full speed out of Comcast Blast (16/2) when connected to AEBS

I just moved into to a new townhouse that I had prewired with Cat 6 and have subscribed to Comcast Blast service. (No Fios here.) When I connect my Mac directly to the modem, I can get download speeds as high as 16-17 Mbps and upload speeds around 1.5 Mbps at times. However, when I try to connect through my home network (modem > AEBS > Gbit switch > Mac), I'm lucky to get > 4Mbps down and about 1.5 Mbps up. (Download speed is obviously more of a concern.) The AEBS is running v7.2.1 and I confirmed through Network Utility that I'm connected to my network at 1Gb. Any suggestions?
Thanks in advance,
Paul

Hey Paul:
Okay.
This should NOT be happening. Something is obviously awry here. Try checking the cable that is used to connect your Comcast Modem to your Airport Base Station. It may / may not be the problem. Usually however Comcast does not supply high quality patch cords and they're not anywhere near the cat 5 or 5e spec. Forget about Cat 6 being given away by them.
So go buy a handful of patch cords that are spec'd at cat 6. (And get ready to pay thru the nose for them!) Use these to replace all the connections from the Cable Modem to the AEBS and from the AEBS to your Gigabyte Switch. You can get a reading that says you're connecting at gigabyte speeds but if your cables won't run it, then you do not get the throughput that you're looking for. Remember you are going through multiple ethernet ports here (cable modem to AEBS to Switch to Computers.
Also, do you have your Gigabyte capable devices on the GB switch ONLY? No 10/100 printers or computers with slower ethernet ports connected to THAT switch? I know they say 10/100/1000 but generally that's total BS. You'll find that isolating the slower speed devices/computers onto their own switch/hub makes a huge difference. A NON-Gigabyte ethernet device (just like a non-N Wireless device) mixed into the same network can slow down the who network. The solution is to put the slower stuff on a little 8 port powered 10/100 switch of it's own with a Gigabyte UpStream connection to your GB switch. That way the slower devices don't slow your entire network down to a crawl. Don't forget to use a CAT 6 Cable from the GB Switch to the 10/100 switch with a GB Upstream port. Yes. It matter that much. The faster the network goes the less forgiving it becomes.
Also, you said you had the house wired for CAT 6. Did the installers use CAT 6 certified Jacks, Cable, Connectors? Lots of really lousy electricians will charge you for CAT6 and then use the cheaper connectors and jacks. You've got the right cable. But nothing else. And the whole thing is NOT going to work at the maximum speeds until the hardware is all CAT6 and installed correctly.
I paid over $30k to wire the office for CAT 6 and POE for the phones. The contractor used the cheaper cat 5 jacks and connectors. They didn't even terminate the connectors properly. Cost me a fortune in trouble shooting to find the problem and more money/time to correct it. When I took the first guy to court for breach of contract and fraud he said "I didn't know that CAT6 required special jacks and connectors and cable terminations." The judge agreed with me that as an electrical contractor charging that kind of money - he should have known and supplied what he specified. Not what was handy and cheaper. I got my money back. And court costs. And he got fined an additional $50k for the fraud and misrepresentation. So find out what your contractors actually installed. I'd almost bet that somewhere along the way, you're back to cat 5 or cat 3 and don't even know it.
Good luck!
Isn't data communications FUN?
Let me know what you discover!
M in LA

Fans on full speed when connected to TB-display

Whenever I'm using my thunderbolt display, the fans in my MBP (early 2011-model) goes up. Every 10 minute or so they ar on full speed (6200rpm), no matter what. It happens even when I'm not using any software, just watching my desktop
When checking iStat or Activity Monitor everything seems normal except for the fans.
Typical scenario every 10 minutes or so:
CPU:
User 3%
System 2%
Idle 95%
Fans (both left and right):
5800 - 6200 rpm
System:
Processor 2.2 GHz Intel Core i7
Memory 8 GB 1333 MHz DDR3
Graphics AMD Radeon HD 6750M 1024 MB
Software OS X 10.8.3 (12D78)
Solutions I have tried without success:
- reset SMC
- reset NVRAM and PRAM
- clean install of OS
- both open and closed lid
Any tips/help?
H.

The temperature is about 145ºF like yours, so maybe it's normal. I have tried with both the lid closed and open.
What I find strange, is that my colleagues (all with basically the same set-up as me: MBP and TB-displays) dont have this problem. They have both older and newer MBPs than I have. We all work with the same kind of work and software.
Yesterday I also tried to connect my MBP to a normal PC-monitor (minidisplay -> VGA) and still the fans went crazy. I can't remember having any issue with before, and as I said: I am the only one in my office that have this issue.

Computers doubling up when connecting two apple routers together

I seem to be getting multiple iterations of the same computers on my network. I have 2 apple routers. One is a master the other is in bridge network extend mode.
The iterations look like this:
Luke's Macbook Air
Luke's Macbook Air (2)
Luke's Macbook Air (3)
Luke's Macbook Air (4)
Merinda's iMac
Merinda's iMac (2)
Apple TV
Apple TV (2)
etc...
Thoughts?

Thanks for clarifying that for me.
Yosemite has a number of issues, and this is one of them. Unfortunately, there are no adjustments or settings on the Apple AirPorts, or in AirPort Utility to address the issue of "multiple" Macs, so your question is beyond the scope of this support forum.
You might be able to temporarily fix things by opening System Prefences (gear icon on the dock), the opening Sharing and adjusting the name of the Mac, but no guarantees.
I would recommend that you post in the Yosemite support forum regarding this issue. The link for that forum is just below:
OS X Yosemite

Networking Best Practices - Connecting Two Switches

Connecting two switches together is an easy task, which makes it so frustrating when it doesn’t work. Here we will outline a basic scenario of connecting two switches and achieving connectivity. In these scenarios we will be using commands and settings that will work for most modern PowerConnect switches. However this does not cover all possible scenarios and the commands may differ slightly from switch to switch.
For instance, in most cases you can use General or Trunk mode when connecting two switches. However, on the PowerConnect 62xx series switches, you must use General mode if you want to allow management traffic onto the switch over the PVID. If you use Trunk mode, you will not have the default VLAN on those ports. The ports will only allow tagged traffic.
For more details on the difference between Access, General, and Trunk modes, follow this link.
http://en.community.dell.com/support-forums/network-switches/f/866/p/19445142/20089157.aspx#20089157
It is always a good idea to have the user and CLI guide for your switch, to reference any possible changes in command syntax.
http://support.dell.com/support/edocs/network/
Layer 2
Layer 2 switches operate at the data link layer of the OSI model. Layer 2 is responsible for error checking and transmitting data across the physical media. MAC addressing sources and destination protocols are layer 2 protocols. Layer 2 switches use the MAC address of data packets to determine where those packets should go. It learns the MAC addresses of all devices and creates a segment/forwarding table.
When a switch receives a frame with a destination address that isn't in its forwarding table, the switch forwards the frame to all other ports. If the destination machine responds to the server, the switch will listen to the reply and learn which port the destination machine is attached to. It then adds that MAC address to the forwarding table.
The Dell PowerConnect Layer 2 switches have ports that all operate in VLAN 1 by default. If it is acceptable to have all traffic on the same broadcast domain, then you can simply leave the default alone, connect the two switches and traffic will flow.
If you do not want all traffic on the same broadcast domain, then we need to look at adding additional broadcast domains through the use of VLANs.
We will use 3 VLANs for the following scenario.
VLAN 1=Management
VLAN 2=Client
VLAN 3=Server
To create these VLANs we do the following commands (VLAN 1 is already created by default)
console(config)# vlan database
console(config-vlan)# VLAN 2
console(config-vlan)# VLAN 3
console(config-vlan)# exit
We can then name the VLANs to help keep things organized.
console(config)# interface vlan 2
console(config-vlan)# name Client
console(config-vlan)# exit
console(config)# interface vlan 3
console(config-vlan)# name Server
console(config-vlan)# exit
Once we have the VLANs created we can place a device in that VLAN by placing the port it plugs into, in access mode for the specific VLAN.
So we have a workstation on port e2 we want to be placed in VLAN 2, we would issue the following commands.
console(config)# interface ethernet 1/e2
console(config-if)# switchport mode access
console(config-if)# switchport access vlan 2
console(config-if)# exit
The next port plugs into a server on port e3 we want on VLAN 3, we would issue these commands.
console(config)# interface ethernet 1/e3
console(config-if)# switchport mode access
console(config-if)# switchport access vlan 3
console(config-if)# exit
For the ports connecting the two switches together, we place the ports in trunk mode and specify the native VLAN and allowed VLANs.
For the port e1 that connect the two switches to each other would be configured like this.
console(config)# interface ethernet 1/e1
console(config-if)# switchport mode general
console(config-if)# switchport general allowed vlan add 2,3 tagged
console(config-if)# switchport general pvid 1
console(config-if)# exit
Once these VLANs and port settings are made on both switches. A server connected to switch A on VLAN 3 should be able to communicate with another Server connected to switch B that is also in VLAN 3. Without the use of a router the devices in VLAN 3 will not be able to communicate with devices that are outside of their broadcast domain (i.e. VLAN 2 devices could not reach VLAN 3 devices)
Layer 3 + Layer 2
Until recently, routers were the only devices capable of layer 3 protocols. Switches capable of routing are now available and in widespread use. In most cases we will connect our layer 2 switches to a Layer 3 capable switch to perform our routing for us.
On the layer 3 switches we will use the same VLANs and setup that we did with the layer 2 switches. Then we will add to the configuration.
We can assign an IP address to each switch with the following command.
Switch A
console(config)#ip address 172.16.1.1 255.255.255.0
Switch B
console(config)#ip address 172.16.2.1 255.255.255.0
Then we will enable routing only on Switch A
console(config)# ip routing
Switch A we assign an IP address to VLAN 2 and enabling routing on the VLAN.
console(config)# interface vlan 2
console(config-if-vlan2)# Routing
console(config-if-vlan2)# ip address 172.16.20.1 255.255.255.0
console(config-if-vlan2)# exit
Switch A we assign an IP address to VLAN 3 and enabling routing on the VLAN.
console(config)# interface vlan 3
console(config-if-vlan2)# Routing
console(config-if-vlan2)# ip address 172.16.30.1 255.255.255.0
console(config-if-vlan2)# exit
On both switch A and switch B we will keep things simple and use interface 1/e1 for the connection between each switch. Setting both switches 1/e1 to general mode, allowing the additional VLAN 2,3, and keeping the PVID of 1.
console(config)# interface ethernet 1/e1
console(config-if)# switchport mode general
console(config-if)# switchport general allowed vlan add 2,3 tagged
console(config-if)# switchport general pvid 1
console(config-if)# exit
We will have one client computer connect to switch A on port 1/e2 and one client connect to switch B on port 1/e2. These ports will be in access mode for VLAN 2, and the config should look like this on both switches.
console(config)# interface ethernet 1/e2
console(config-if)# switchport mode access
console(config-if)# switchport access vlan 2
console(config-if)# exit
We will have another client computer connect to switch A on port 1/e3 and one client connect to switch B on port 1/e3. These ports will be in access mode for VLAN 3, and the config should look like this on both switches.
console(config)# interface ethernet 1/e3
console(config-if)# switchport mode access
console(config-if)# switchport access vlan 3
console(config-if)# exit
On Clients connected to Switch A we will assign an IP address and gateway based on the VLAN they are in access mode for.
Client connected to access port for VLAN 2.
IP Address:172.16.20.11
Default Gateway:172.16.20.1
Client connected to access port for VLAN 3.
IP Address:172.16.30.11
Default Gateway:172.16.30.1
On Clients connected to Switch B we will assign an IP address and gateway based on the VLAN they are in access mode for.
Client connected to access port for VLAN 2.
IP Address:172.16.20.12
Default Gateway:172.16.20.1
Client connected to access port for VLAN 3.
IP Address:172.16.30.12
Default Gateway:172.16.30.1
External Connection
At some point we may want traffic to have an external connection. To do this we can create a new VLAN for our point to point connection from Switch A to our router. We will use VLAN 7 for this and assign an IP address.
console(config)# vlan database
console(config-vlan)# VLAN 7
console(config-vlan)# exit
console(config)# interface vlan 7
console(config-vlan)# name WAN
console(config-if-vlan2)# Routing
console(config-if-vlan2)# ip address 10.10.10.2 255.255.255.0
console(config-if-vlan2)# exit
On our router we will assign an IP address of 10.10.10.1
Then place the port connecting the switch and router into access mode for VLAN 7. In this case we use port e4.
console(config)# interface ethernet 1/e4
console(config-if)# switchport mode access
console(config-if)# switchport access vlan 7
console(config-if)# exit
We will then need to put in a default route with the next hop as the router IP address. This allows the switch to know where to route traffic not destined for VLANs 2, 3, or 7.
console(config)#ip route 0.0.0.0 0.0.0.0 10.10.10.1
Next on the router we’ll need to add a route back so the router knows about the networks attached to switch A. Generally adding a static route on most routers is done with the following command:
ip route {Network} {Wildcard Mask} {Next Hop-IP}
In our case here are the 2 static routes we could use.
Ip route 172.16.20.0 0.0.0.255 10.10.10.2
Ip route 172.16.30.0 0.0.0.255 10.10.10.2
The routing that we enabled on Switch A will enable traffic from the other VLANs to traverse over port 1/e4 to the router, connecting us to external traffic. The routes we added to the router allow the traffic to flow back to the switch over port 1/e4.
Layer 3 + Layer 3
In some situations we have two switches, each setup to route for its own broadcast domain, which we want to connect together. In this situation we no longer have a need to use Trunk or General mode between the switches. Instead we can create a common VLAN that will be used for the connection between the two switches.
To create this VLAN we will run the following commands on both switch A and B
console(config)# vlan database
console(config-vlan)# vlan 6
console(config-vlan)# exit
console(config)# interface vlan 6
console(config-vlan)# name Connection
console(config-vlan)# exit
On switch A we assign an IP address to VLAN 6 and enable routing on the VLAN.
console(config)# interface vlan 6
console(config-if-vlan2)# Routing
console(config-if-vlan2)# ip address 172.16.60.1 255.255.255.0
console(config-if-vlan2)# exit
On switch B we assign an IP address to VLAN 6 and enable routing on the VLAN.
console(config)# interface vlan 6
console(config-if-vlan2)# Routing
console(config-if-vlan2)# ip address 172.16.60.2 255.255.255.0
console(config-if-vlan2)# exit
On both switch A and B we place the connecting ports into Access mode for VLAN 6.
console(config)# interface ethernet 1/e1
console(config-if)# switchport mode access
console(config-if)# switchport access vlan 6
console(config-if)# exit
We then need to make some changes to switch B now that it is layer 3 and not layer 2 and has its own broadcast domain.
We will enable routing on Switch B
console(config)# ip routing
What used to be VLAN 2 and 3 will now be VLAN 4 and 5 for our separate broadcast domains.
Switch B we assign an IP address to VLAN 4 and enabling routing on the VLAN.
console(config)# interface vlan 4
console(config-if-vlan2)# Routing
console(config-if-vlan2)# ip address 172.16.40.1 255.255.255.0
console(config-if-vlan2)# exit
Switch B we assign an IP address to VLAN 5 and enabling routing on the VLAN.
console(config)# interface vlan 5
console(config-if-vlan2)# Routing
console(config-if-vlan2)# ip address 172.16.50.1 255.255.255.0
console(config-if-vlan2)# exit
On Clients connected to Switch B we will assign an IP address and gateway based on the VLAN they are in access mode for.
Client connected to access port for VLAN 4.
IP Address:172.16.40.11
Default Gateway:172.16.40.1
Client connected to access port for VLAN 5.
IP Address:172.16.50.11
Default Gateway:172.16.50.1
The end result should look like this.
Troubleshooting
If we are having issues with connectivity, we may need to place some static routes in place to help traffic to the next hop in the network.
On switch A we configure a static route to help traffic to the next hop in the network, which is the router.
console(config)# ip route 0.0.0.0 0.0.0.0 10.10.10.1
The external router will also need a path defined back to all networks/VLANs.
To check the status of a port we can use the command. Show interfaces detail, this will help us see the port status. For example to check the status of port 48, we would run this command.
console# show interfaces detail ethernet 1/g48
To check routing paths:
console# show ip route
The IP address of the network for each VLAN should be listed as C – Connected. Then also a path or default route to your upstream router.
We can use basic ping commands from a client to help test where connectivity is dropping off at. By doing this we can narrow down where in the network to start troubleshooting.
-Ping from client to default gateway, being the VLAN the client is in access mode for. If this fails then we may need to double check our client settings making sure the proper IP and gateway are being used.
-Ping from client to the ip address of the switch the client plugs into. If this fails we may not have VLAN routing enabled on the VLAN the client is in.
-Ping from client to another client on same VLAN, same switch. If this fails we need to check on client settings, IP address and gateway.
-ping from client to another client on different VLAN, same switch. If this fails we need to double check the VLAN routing commands are in place.
-ping from client to the ip address of the next switch in the network. If this fails then check Trunk port configuration from switch to switch, ensuring the VLAN is added to the Trunk port.
-ping from client to another client on same VLAN, different switch. If this fails, check Trunk port settings.
-ping from client to another client on different VLAN, different switch. If this fails then check trunk settings and VLAN routing configuration.

Derek,
I tried to draw my prefered setup for this network configuration.
I would create a Team with the two 1 GBit NICs and use it for Domain, DNS, Backup and any SystemCenter Agents.
I would also Team the two 10 GBit NICs and than assign it to a Hyper-V Switch for the VMs. In Windows Server 2012 it is posible to create vNICs for the Management OS that use this Hyper-V Switch (Converged Network Design). I would create two vNICs SMB1
and SMB2 to use them for Cluster and Livemigration traffic with SMB Multichannel. If your storage system supports SMB Multichannel you can also use both as storage NICs (but this depends wich vendor you have).
Hope this helps.
Grüße/Regards Carsten Rachfahl | MVP Virtual Machine | MCT | MCITP | MCSA | CCA | Husband and Papa |
www.hyper-v-server.de | First German Gold Virtualisation Kompetenz Partner ---- If my answer is helpful please mark it as answer or press the green arrow.

Unable to change permissions when connecting over SMB

As of OS 10.9, SMB2 is the default protocol when connecting two Macs running 10.9. Unfortunately, SMB2 seems to be half-baked at this time. Among the issues I've encountered, one of the more vexing ones is that it does not seem to be possible to change permissions on a remote file or directory over SMB. In Finder, the permissions section simply says "you have custom access" regardless of the file/folder's actual permissions. Even if I have full read/write access to the file/folder, I have no way to change its permissions.
chmod and chown also don't work. They don't report an error – they simply don't do anything when I run them on remote files.
If I connect to the same system via AFP, everything works fine and I can change permissions in Finder, and via chmod.
Is anyone else seeing this behavior? Are permissions just broken under SMB2?

So the background to this situation:
1. The user had OS 10.6.8 installed on one volume, while his actual users home folders stored on a second volume, this is fine but can sometimes cause issues during/post upgrade to 10.7
2. The user upgraded to 10.7 and while his home folders were still being accessed, he no longer had permission to change or modify them.
3. The user downgraded to 10.6.4 again which broke the link for his users completely.
4. In an attempt to change the permissions for his information he had the (common) mistake of changing the permissions of his root level of his drive, this did several things, in addition to negatively effecting his OS, it also locked the drive mount points in his (hidden) /Volumes/ folder.
5. the steps taken to help rectify this issue:
A. Open Terminal.
B. TYPE:
chmod -N /
chmod 1775 /
chown root:admin /
C. Reboot computer
D. Open Disk Utility.
E. Repair permissions on the boot volume.
F. Also the following commands were run on her second drive to allow him access to his stuff again:
sudo chflags -R nouchg /path to drive/
chmod -R 775 /path to drive/
chmod -RN /path to drive/
chown -R username:staff /path to drive/
Once the permissions repair is complete the Users can be readded to the System Preferences>Accounts pane and the paths to home directories located in his second drive using the "Advanced Options..." section, but due to the time the permissions repair was going to take this step will be posted tomorrow.
Also each user will require Terminal commands to make the permissions unique for each user: (this must be done PRIOR to the users being added in System Preferences>Accounts.
chmod -N /
chmod 1775 /
chown root:admin /
sudo chflags -R nouchg /path to home folder/
sudo chmod -R 775 /path to home folder/
sudo chmod -RN /path to home folder/
sudo chown -R username:staff /path to home folder/
EE

I have one itunes account with two phones. when i phone one of the numbers both phones have started to ring, only when connected to wifi at home. How do i resolve this please?

I have one itunes account with two phones assigned to it, sons and daughters, (5s). When i phone one of the numbers both phones have started to ring, only when connected to wifi at home. The problem does not occur when not connected to wifi. How do i resolve this please? texting is fine it is only when ringing one of the numbers.

<http://support.apple.com/kb/HT6337>
"To turn off iPhone Cellular Calls on a device, go to Settings > FaceTime and turn off iPhone Cellular Calls."

I have an ipad 2 and when connected to my wifi at home it will not download and play you tube videos quickly. Do I need to upgrade my connenction speed? What is the optimal speed?

I have an ipad2. When connected to my wifi at home it will not download you tube videos for easy viewing. Do I need to upgrade my connection speed? Would 3 Mbps be enought or do I need to go to 6 Mbps. I mainly use my ipad to view emails, browse the internet and watch you tube videos.
thanks - Michelle

Welcome to Apple Support Communities.
There are a number of factors in the 'speed' equation. Any or all of them can affect the 'observed' speed of your connection.
1. Are you in a neighborhood full of WiFi routers (and thus, lots of WiFi interference)? I can 'see' at least 22 other WiFi routers from my living room!
2. What is the maximum connect speed and band and bandwidth available from your wireless router. Is it 802.11n or the older 802.11a/b/g? 300Mbits or 150Mbits? 2.4Ghz or 5Ghz or both? Does your router measure (QoS) Quality of Service and can it change 'channels' automatically?
3. What is the observed strength of your wireless connection? Are you getting at least 80% signal when connected? Are there other people in your family also using significant bandwidth at the same time (Netflix, streaming video, streaming audio, game systems)
4. What is the "advertised" speed of your current ISP connection?
5. What is the measured throughput of your current setup. Go to speedtest.net or use the free speedtest.net app available in the App Store. Try several times, from different locations in your home, and at different times of day and night.
I have AT&T DSL advertised at 3Mbit/sec down and 512Kbit/sec up. My Speedtest.net measured throughput is about 2.4 Mbit/sec downstream and upstream is about 0.4Mbit/sec. I'm using a Motorola Netopia 2210-2 DSL modem. I have no problem viewing YouTube videos and other mobile video content on the iPad 2. I'm connected wirelessly to a D-Link DIR-655 Gigabit router rated at 150Mbps at 2.4Ghz (only) with 802.11 b/g/n enabled. The interior of my home is within a range of 30-50 feet from the router and no more than 1 wall. It is a single level concrete slab foundation of about 1500 sq. ft. with cathedral ceilings. I have successfully streamed ESPN3.com on my MacBook at the same time my son was streaming another ESPN3.com game on his MacBook Pro. I've streamed YouTube videos while my son was watching a NetFlix movie on his Wii game system. He's also successfully used Skype for extended 'teleconferences.' None of my devices are connected to HDMI on a large screen TV. 95% of the time, I can do iChat video without any signal breakup to my son (who is at a college with a Gigabit (1000Mbit) wired connection!). 5% of the time the connection drops. We haven't tried FaceTime (designed for mobile connections to be much less bandwidth-intensive, from what I understand) simply because we both have iChat on our computers.
So for me, a 3Mbit DSL connection is absolutely adequate, given all the other parameters mentioned. As the car manufacturers say, "Your mileage may vary."
Message was edited by: kostby

When we connect two bw systems to one R/3 system?

Hi ,
When we connect two bw systems to one R/3 system,
could you please exlain what is the imact to SAP and BW in terms of query performance, batch performance,Develoment ,Quality system,security,BW Support.
Thanks in advance.
Regards,
kranthi

you can connect multiple BW to single R3 source system.
In the delta queue (RSA7 in source system), you have a field with the target system, so you don´t have problem if you have many target bw system, because the data selection is done by system field.
Challenge arises when you have multiple R3 feeding to single BW system and then you have to consolidate the master data say 0material fed from different source system R3 then you can consolidate data using consolidated infoobject.
The following components concatenate to the key of a consolidated InfoObject:
1)source system ID (two-character source system ID; permitted values are stored NW BI table RSSOURSYSTEM)
2)one blank character
3)backend object type (four-character backend object type; permitted values are stored BI table RSBWBEOTYP)
4)master data key value as stored in the source system
Note that the key of a consolidated InfoObject solely consists of non-integrated informations from the different source systems. Integration across source systems results from a (maybee repeatedly applied) data consolidation and cleasing process which unveils duplicate master data keys.
Hope it Helps
Chetan
@CP..

HT1222 Hi Does anyone know how can I stop my iPhone 4s downloading automatic system update so reducing my network speed when plugged in to charge or connected to the pc ??? I'm really ok with my iOS 5.0.1 and I don't need 5.1

Hi Does anyone know how can I stop my iPhone 4s downloading automatic system update so reducing my network speed when plugged in to charge or connected to the pc ??? I'm really ok with my iOS 5.0.1 and I don't need 5.1

Setting up and troubleshooting Mail
http://www.apple.com/support/ipad/assistant/mail/
iPad Mail
http://www.apple.com/support/ipad/mail/
Try this first - Reset the iPad by holding down on the Sleep and Home buttons at the same time for about 10-15 seconds until the Apple Logo appears - ignore the red slider - let go of the buttons. (This is equivalent to rebooting your computer.)
Or this - Delete the account in Mail and then set it up again. Settings->Mail, Contacts, Calendars -> Accounts Tap on the Account, then on the red button that says Remove Account.
 Cheers, Tom

What happen when we connect Two PC with IP from Same subnets

Scenario 2nd : What happen when we connect Two PC with IP from Same subnets. PC1 -192.168.10.1/24 PC2 - 192.168.10.2 on a two different L2 Switch on different vlans which are connected via a LAN cable.
All ports are access ports
Interview Question : No More Info.
Pc1<SwA>------<SwB>PC2
Q.1 Will they communicate If yes what will be packet/frame flow.
Q.2 If not where will be the packet/frame drop. ? Why.
I need step by step if possible plz how the packet moves , vlan taggings n all internal works that happens behind .. plz
thnx in advnce ....

Hi Abhishesk,
The PCs should communicate each othet.
Since there is no trunk port involved, there is not tagging involved.
Since both the PCs are into the same subnet. PC1 will not need default gateway for the communication with PC2. So PC1 will start with sending ARP request for PC2 MAC address.
Since all the ports in SW1 are in same VLAN, the ARP should reach all ports including the switchport where SW2 is connected to.
Sw2 has got a complete different access port on ALL the switchports. Sw2 will receive the ARP from Sw1. Remember that there is no tagging for the frame. Hence Sw2 will again send the ARP packet to all the ports which belong to same VLAN wherein the packet is received. ie, Sw2 will send the ARP packet to all the ports in Sw2. PC2 will also get the the ARP.
The ARP reply will make it way back using the same logic.
Now both the PCs can start the actual packet exchange.

Internet speed slows down when connected via airport express

Internet speed slows down when connecting via airport express. When connecting directly via the timecapsulethe internet speed is ok, when connecting via the airport express the speed slows down.What can I do to change that? Any suggestions?

Turn off the AirPort Express completely as a test, and move your computer very close to the location of the Express.
As I said before, the Express can only extend the bandwidth (speed) that it receives from the Time Capsule, so the speed that you see there with the Express powered off will be the fastest speed of which the Express is capable.
The Express will make the signal go further when it extends....but it will not make the signal go faster.
A good location for a device that extends wirelessly is a point that is about half the distance from the Time Capsule and the general area that needs more wireless coverage.
If you locate the AirPort Express too far from the Time Capsule or there are more than a couple of walls in the signal path, the signal will be very slow by the time that it reaches the Express....and the Express simply extends a signal that has already slowed down significantly.
If you already have the Express located about half the distance between the Time Capsule and general area that needs more wireless coverage, how many walls, ceilings or other obstructions are there in the signal path between the Time Capsule, the AirPort Express and the area that needs more coverage?
Often, due to obstructions, it is just not possible to achieve good performance when you try to extend a network wirelessly. The solution is connect the AirPort Express to the Time Capsule using a wired Ethernet connection.
There is virtually no signal loss with this type of connection, so the Express can be located exactly where it is needed and it will produce a much faster wireless signal in this type of setup.

ASA 5505 speed reduction when connected to a Planet fiber converter

Hi!
We have many customers running ASA 5505, and a number of them are running 100 Mbit connections. This normally works fine. But recently, our ISP has started setting up all new fiber connections using a Planet fiber to RJ converter (Before they used Cisco switches), and with those, the locations only get around 50-60 Mbit. We have done all the testing - force port speed and duplex settings, test with a PC directly connected to the converter etc. And the connection allways runs 100 Mbit. And the ASA's themselves also run 100 Mbit when connected to anything else than the Planet converter. We have for now circumvented the problem by placing a simple L2 switch between the converter and the ASA's, but this is not an ideal solution as it adds another single point of failure element etc.
Any ideas?

The Express units can extend wireless on the TC or each other.. but they cannot extend wireless on the Asus anyway..
So the setup is Asus--TC (that has to be ethernet) The TC in bridge mode.
Then TC -- express can be done by ethernet in roaming mode as bob listed above or extend wireless.
I am guessing.. what model are the express units.. they are older Gen1 N model ??
IMHO the TC is simply no longer viable.. replace it with one express as the AP and extend it with the other Express.. see if that works better.
But I would be trying to use the wireless just from the AC66U.
I would also force the Asus back to 20mhz on the 2.4ghz band.. so you can provide adequate channel separation.. 40mhz wireless on 2.4ghz works poorly anyway because you have too much wifi .. there is very limited number of non-overlapping channels.. ie 3. 11, 6 and 1.

Terrible speed when connecting two AEBS

Similar Messages

Maybe you are looking for