Number of supported users(clients) in Roaming network setup

We are planning to configure Roaming Network with 10 units of Aiport Expresses in our office. I just want know how many number of clients can connect to this network.

In theory 50..
In reality.. about 10 per unit.. but you might stretch it to 20 if you use both bands carefully. Remember you only have 100mbit ethernet connection.. at absolute max you are going to reduce 10 clients down to 10mbit.. and 20 clients to 5mbit.. that is very slow when you start moving files. And wireless just ain't that efficient.. so much less is better.
You might also find running 10 units harder than you might think unless they are 100M apart.. wireless provides 3 non-overlapping channels at 2.4ghz and about 3 times that number at 5ghz depending on location in the world.
If they are too close to each other.. you will have chaos.
Airport Express is a home unit.. for office you should buy pro grade gear.

Similar Messages

  • Roaming Network setup

    Hello all-
    I've read most of the posts on setting up a roaming network and I'm still struggling with my setup. Here's my scenario- any help is appreciated:
    -I have a wireless-N Primary AEBS connected to COX cable modem in the house
    -I have 100 ft cat5e cable coming out to my garage/studio that I plug directly into my MB pro from the Primary AEBS
    -I am attempting to setup a roaming network in my garage/studio by plugging the ethernet cable from the primary AEBS to a wireless-N Airport Express A1264 in order to maintain a wireless network out in the garage
    -I have followed Apple's Airport Networks manual and tried a combination of things in Airport Utility, but no luck
    -Since I don't get a wireless signal from my primary AEBS to my MB pro on my network (when I am in the garage), I assume it is to distant for the Airport Express in my garage to get the signal. So would my configuration actually be a roaming network?
    Anyone have any ideas?

    Bob, I'd like to thank you for some of the most helpful advice on the topic I've seen on the boards. I greatly appreciate this thread and a couple others you've provided guidance on. Much appreciated.
    Sorry to trouble you with more but I would be grateful for the thoughts and response. I'll list out the configuration I've pulled together based on my understanding on a few of your posts. The reason for my post is that in spite of my efforts the throughput on the network seems spotty and off.
    Motorola SB6120 (DOCSIS 3)
    Airport Extreme - Simultaneous Dual Band II (7.5.2)
    Time Capsule - Simultaneous Dual Band (7.5.2)
    Airport Express - 802.11n (7.5.2)
    Mac Mini (x2)
    MacBook Air
    MacBook Pro
    iPhone 4 (x2)
    Sony PS3
    Area - Connection:
    I'm in a 2 story place that's unfortunately concrete but I doubt this is the cause of the issue. Cable enters downstairs and is connected to a brand new SB6120. The 6120 ethernets to the Extreme. There is a Mini hung off the Extreme using ethernet. Also off the Extreme is Cat5 running upstairs to the 2nd story connected into the Wan Port of the Time Capsule. The second Mini is connected to the TC with ethernet. The PS3 hangs off the Extreme using ethernet but this is not used often. The Express is located outside on the patio on the 1st floor level.
    AEBS: Create Wireless Network (2.4 & 5Ghz), No Guest Network. Separate network names created for 2.4 and 5Ghz. WPA2 in place. Manual Channels 149 & 6, Share Public IP, DHCP is on and a range has been set. Enable NAT Port Mapping Protocol is selected. So is Allow this Network to be extended. Create closed Network is on and Use Wide Channels are both on. I've reserved IPs for all machines (including the TC & Express) using MAC IDs and have set all machines to DHCP and confirmed they are using the corresponding IPs. I've also included the 2.4Ghz network for all the Airport clients.
    TC: Bridge Mode selected. Create Wireless Network (2.4 & 5Ghz), the exact same network name & device passwords are used. Same with WPA2. DHCP on. Allow this Network to be extended is NOT checked. Manual Channels at 161 & 13. Create closed Network is on and Use Wide Channels are both on.
    Express: Extend Wireless Network. Allow Wireless Clients is checked. It's using the same network name (the 2.4Ghz), device password, and WPA2 as well. Channel is set to automatic and seems to like Channel 4. Connect using Wireless Network & Bridge Mode selected.
    Wow. What a long list of it. Sorry about it. Ultimately, I was hoping to create a Roaming Network but when configuring the Express the option was only to Create or Extend a network. I can't seem to find a lot of information about the pros & cons but I was hoping to achieve Roaming.
    Issue: I seem to be having quite a bit of socket issues and connection closed issues. When moving about the house I'm almost forced into a restart in order to secure a better connection. Once I do get a device connected it seems to burst up and down a lot. Meaning, I'll have great up/down and then suddenly I'm down to 30B/s down. It is highly possible I've got lousy cable access. I am paying for 100MBs but I do know they suffer from noise on the line quite a bit.
    Is there anything you can think of to help optimize this configuration? Again, sorry for the long note and thanks for your earlier guidance to get me this far. It is working well but I still feel I have missed something to make it better. Let me know please. Happy to respond and clarify as needed.

  • TLN missing for users in Federated Portal Network Setup

    Hello All,
    We are facing a weird problem in our Federated portal Production setup; when the users login to portal they are not able to see the TLN. On further investigating we found that this issue is happening when the user id is locked in any of the producer portals within our FPN environment due to which the users are not able to view roles related to other systems as well in which there id is active.
    This issue is reproducable but only occur once the ID are locked and password is expired in one of the assigned system.
    Our FPN setup is as below:
    Consumer C connects to Producers
    1. A (RDL)
    2. B (RDL)  - BI Dual Stack
    3. D (RRA)  -  BI Dual Stack
    In turn A (producer) connects to 4 ECC systems (F3, M1, R1, R5)
    We are using RRA and RDL both in our environment.We have connected all federated portal with P4 Port, so if required we
    can use RDL.
    Please note our consumer C is EHP1 SP5 and both BI systems B and D are EP 7 sp13. 
    Any help in this regard is highly appreciated as this is critical issue affecting users in our production environment badly.

    This was an SAP bug. We raised an OSS message and it is taken care now. User now gets TLN and then portal runtime error if the id is locked.

  • In a Roaming Network, Does the Primary Base Station have to be the only hub, or can spokes come out of an Extended Base Station?

    I live in the basement of an old, brick building, in one of 5 apartments, for the building's staff. I have an older Airport Extreme and Express setup that's working for me in my unit, connect to a Comcast Ubee cable modem. The rest of the basement shares a DSL connection through a wired network that includes three routers. I've been asked to build a network that the rest of the staff can share, using my cable connection and any new hardware required. Since ethernet cable is already in place for the legacy DSL network, I'd like to re-use it with new base stations and Airport Expresses, just swapping out the old gear. But the Roaming Network setup instructions show all spokes coming out of the Primary Base Station. This does not match my situation, where my cable modem is in a different apartment from the hub of the old network.
    My thought was to get two new Airport Extremes and wire one to my modem, replacing my old AE, and then place the other in my neighbor's apartment, connected by a new ethernet cable. His Extended Base Station would be where all the legacy ethernet cables terminate. I would plug them into the new, Extended Base Station on his end, and put Airport Expresses on the other ends, so each apartment (and the staff room) would have its own wired router.
    Will this configuration work? If not, can anyone suggest a better way? I'm an Apple products user but some of the other guys use Windows. My understanding is that this shouldn't be a problem.

    What I mean is that ethernet can be wired through switches.. (or bridged routers which are switches).
    So you have
    .      .      .   |
    .      .      .Switch--Client
    .      .      .  |
    .      .      . Switch--Client
    The correct way to do this is
    .      |
    .    Client
    .      |
    .     Client
    etc.. all clients are ethernet connected back to the router.. no switches. That means loads of ethernet.. one for every client run all the way back to a central area.
    What you are proposing is to run switches (bridged routers).. so you are using each ethernet link to connect more than one computer. This is wrong from a purists point of view.
    Sorry for the ASCII art work.. but I hope it makes sense.
    You do not need fancy gear to make this all work.. what you do need is a main controlling router.
    You cannot have two routers.. so you cannot put a switch between the cable modem and use two router. You have cable modem---ROUTER.
    That single router must therefore do all the work... part of that work is to provide some way to control usage.. so everyone gets a fair share.. and keep an eye on quotas.. sadly you cannot do both with any cheap routers I know of.. what I propose you do is WNDR3800 flashed to gargoyle firmware.. this is key.. this firmware will be able to track usage and allow each user a fixed amount of your bandwidth.. upload in particular.. as even with high speed on your download you still do not have upload of the same capacity.
    As far as end users are concerned they do not need fancy equipment.. they just need a wireless router. So they can get connection by ethernet or wireless.
    Talk to me directly if you need more is here. s
    my email is also in the profile. But I use the gmail more.

  • Roaming Network with Powerline Adapter

    I have read numerous posts on this, but I am still having a small issue.  My setup is as follows:
    Arris router set on bridge connected to
    latest gen. time capsule (set to DHCP, create network), connected to a powerline adapter that then runs upstairs.  The other powerline adapter is upstairs and connected to latest generation airport express (bridge mode, create network with same ID and pwd as the time capsule).
    Previously, I had the time capsule and the airport express (via the powerline adapter) each connected to the arris router, but this was causing some issues.
    Nevertheless, with the new roaming network setup, the powerline adapter seems to be getting slower speeds or the upstairs airport express is slow.  I can get close to 30 down from the time capsule, but half that on the airport express.
    Any suggestions?

    Powerline is always "iffy". The system can work OK when the powerline adapters are on the same electrical circuit, but things really slow down.....dramatically, in some cases.....when the adapters are on different electrical circuits, since there is a significant signal loss when one tries to "jump"' matter what the advertising or sales guy might say.
    The signal will also slow down quite rapidly over distance.
    Not much that you can do about that, unfortunately, other than experiment a bit with different AC sockets in different locations to see if one might be better than another. Like wireless, powerline is half science and half voodoo, so there are never any clear cut rules about what will and will not work.
    Some users can get by with powerline, but the folks who are looking for the best performance almost always come to realize that there is nothing better than an Ethernet cable with no loss up to 300+ feet or 100 meters.  Yes, I know that the running the cable might not be easy, but a good electrician or wire guy can do some amazing things.

  • Can't Connect to "Roaming" Network

    I have set up a new Airport "roaming"network.  I have an Airport Extreme as the primary wireless router attached to the Internet.  The Extreme is attached via ethernet cable to an Airport Express.  I believe everything is set up according to Apple's instructions.
    When I have both devices on, their status lights are green.  However, if a device (iPhone, PC) is near the Express, it is asked to join the network and I have to re-enter the password.  It will never connect.
    If I take that same device and get near to the Extreme, it will connect, no problem.
    Also, if I unplug, the Express, everything is OK (except my wireless coverage is not good enough in the house).
    Any help would be greatly appreciated.

    Let's double-check your roaming network configuration just to be sure nothing was missed.
    Roaming Network Setup
    Ref: See page 42 of the Apple AirPort Networks guide.
    Setup the AirPort connected to the Internet to "Share a public IP address." Internet > Internet Connection > Connection Sharing: Share a public IP address
    Setup the remaining AirPorts, as bridges. Internet > Internet Connection > Connection Sharing: Off (Bridge Mode) For each AEBSn in the roaming network:
    For each base station:
    Connect to the same subnet of the Ethernet network.
    Provide a unique Base Station Name.
    The Network Name (SSID) should be identical.
    If using security, use the same security type (WEP, WPA, etc.) and password. Note: It is highly recommended that you use WPA2 Personal for best bandwidth performance.
    Make sure that the channel is set at least three channels apart from the next base station to prevent Wi-Fi interference.

  • How can I set up an AirPort wirelessly in client mode on a roaming network?

    I recently set up a roaming network within my office using a RADIUS server for access control. I have multiple airports connected to our broadband via ethernetcable providing a seamless network over a large space. It works great.
    However, now that I've done this, I can't get one of my airort expresses to work as a wireless music box with speakers plugged in. This airport is in a location that has no ethernet nearby, which is fine because I just want to use it to play music, not extend the network. It's MAC address is configured in the RADIUS server as an authorized device.
    I've tried this "client mode" setup, and a variety of other combinations of settings like making it part of the roaming network as an extender, with no avail:
    Everything I've tried gives me the "AirPort Utility was unable to find your AirPort wireless device after restarting" message, and my AirPort has only a yellow light.
    It seems the AirPort Express is totally incompatible with a roaming network. Is there any way to make this work?

    Before we get into details here, do you understand that the Express will not be be able to "extend" the Xfinity wireless network wirelessly?
    The Express can only extend a network wirelessly from another Apple AirPort router. Another way of saying the same thing is that if you want to "extend" wirelessly, you will need two Apple AirPort routers.
    The Express will need to be permanently connected to the modem/router using an Ethernet cable if you want it to extend the Xfinity network.

  • How to set up roaming networks in both 2.4 an 5 Ghz.

    I have two Airport Extreme base stations, both separately ethernet-connected to our wired LAN. They are configured as a roaming network (both have the same SSID and security credentials). The roaming works pretty well.
    However, when I flip the 5 Ghz option on on both stations, I get two different network names for the 5 Ghz WLAN.
    Our regular (2.4 Ghz) network name is "Apple Network" -- and we only see one instance of this in the airport menu of any computer in range of both.
    However, we see two different 5 Ghz network names show up: "Apple Network (5 Ghz)" and "Apple Network(5Ghz)" (note the missing space between the "k" and the opening parenthesis in the 2nd one).
    When I look in Airport Utility, the 5 Ghz network names are identical (both network names have the space between the "k" and the opening parenthesis). So, the base station seems to be changing one of the names on purpose, I am guessing because they need to be unique?
    However, this isn't the case for the 2.4 Ghz WLAN name (the 2 stations have identical SSID's, and the SSID only shows up once).
    This is annoying and confusing for our users, since there are three networks, as follows:
    "Apple Network"
    "Apple Network (5Ghz)"
    "Apple Network(5Ghz)"
    My question is: is there a way to make the two 5Ghz network names the same (which they already appear to be in the Airport Util config), and also only appear once in the airport menu of the WLAN clients?
    Thank very much.

    Open Macintosh HD > Applications > Utilities > AirPort Utility
    Click Manual Setup
    Click the Wireless tab located just below the row of icons
    Click the Wireless Network Options button
    Enter a check mark in the box next to 5 GHz Network Name
    When you do this, "5 GHz" will be added to the SSID
    Click Update and allow 25-30 seconds for the AirPort Extreme to restart

  • How do I know "Roaming Network" is working with Airport Express and Airport Extreme and should I use extended wireless network for third Express?

    Attempting to eliminate a dead spot in Wifi coverage [and implement AirPlay] have one Airport Extreme 802.11n and two Airport Express 802.11n's.
    The Airport Extreme is of course connected to cable modem and Ethernet switch, and one Airport Express is connected to the Ethernet network. As per instructions for creating a "Roaming Network", Airport Express is set to same SSID, security type, and Password.
    1. How does the client device know which Airport to connect to? In other words, will it switch to the closer WiFi transmitter automatically? The WiFi reception problem is intermittent in the fringe areas so what I do not want it for it to stick with the more distant Airport Extreme in the basement when the Airport Express which is closer will work better.
    2. How can I tell which of the Airports the attached client device is using?
    The third Airport Express will be in a third location - I was planning on using it also for expanding coverage but after reading the warnings about performance suffering when purely using WiFi for the expansion in this location ("Wireless Extended Network" without an ethernet connection) I have figured that the single wired Airport Express will be adequate and will use the third Express to do Airplay only.
    Question: Can I use this second Airport Express to extend the wireless network via "Extended Wireless Network" while the other two are in "Roaming Netowrk" configuration? Without bogging down??

    1. How does the client device know which Airport to connect to?
    The Mac computer will automatically connect to the wireless access point with the strongest signal...which is probably the closest AirPort. An iPhone or iPad may not do this and will tend to stay connected to one AirPort.
    2. How can I tell which of the Airports the attached client device is using?
    On a Mac, open Macintosh HD > Applications > Utilities > AirPort Utility. Click on one of AirPorts. In the area to the right, locate the AirPort ID and jot that down. Then do the same for your other AirPort.
    Move your Mac near one of the AirPorts and log on to the wireless. Hold down the option key on the Mac while you click the fan shaped AirPort icon at the top of the screen. Look for the BSSID. That is the AirPort ID of the device to which you are connected.
    If you are close to the "remote" AirPort, and you see the AIrPort ID of the "main" router when you are testing, then you know that the network is not configured correctly.
    Can I use this second Airport Express to extend the wireless network via "Extended Wireless Network" while the other two are in "Roaming Netowrk" configuration? Without bogging down??
    There will be a modest 10-15% bandwidth loss with the "extend" setup, assuming that the Express is located where it can receive a strong wireless signal from the AirPort to which it is associated. You can avoid the bandwidth loss if the Express is also connected via Ethernet as part of the roaming configuration.

  • Is there a known conflict between an extreme g base station and express n in a roaming network?

    I have an extreme g base station connected to a cable modem, an express g connected to a linksys switch via ethernet, and an express n connected to the same switch via Ethernet. The switch is connected to the extreme g base station by Ethernet as well. They are all set up to be a roaming network with 128 bit WEP security. I made two changes to the network recently. I went from a WDS setup with the extreme g and express g, which was generally stable but slow, to the roaming setup above, and I added the express n. Now something is causing the network to loose connectivity at least once a day, requiring a restart of the extreme g. My hunch is the express n is causing problems for the older g units.
    Does anyone know if this is a known problem and if there is a solution?

    For what its worth.....
    I have mixed older "b/g" and newer "n" devices in "extended" and "roaming" networks for years, and have never experienced any issues with this type of setup.
    As a Community Support "regular", I can say that I cannot recall having seen the type of issue that you have described, but other users may comment with different opinions.

  • Assigning user accounts on small network

    We are setting up a business where people with "subscriptions" can come in and work, in a setup that has wireless.  When the subscription runs out we want to disable their ability to access the network.  Doing that through the router's key would be a nightmare!  We would like a system whereby we can give the individual user a user account w/password, and disable the individual account.
    However, Im not sure what the best to do that would be.  Ive used a corporate vpn, but that required an account on the corporation's domain (100,000+ users) and we are talking maybe 20 users, so we arent looking for major functionality (not to mention the support issues).  Just the ability to control user access to the network.
    Does anyone have any thoughts on how we can best do this?
    Thanks very much, Mark

    The most important step, once you've got Open Directory and DNS set up, with Local Network Users set up in, is to make sure that all client Macs are using the server's IP address as the primary DNS server in System Preferences > Network, and that they have joined the Network server in System Preferences > Users and Groups > Login Options.
    Having said all that, I have just spent hours setting this all up only to find out that Mail doesn't currently work with Network Homes in 10.10.3 / 4.1.
    I will be hoping that Apple recognise the bug, and put out a fix soon.

  • Socket options to support hand off across wireless networks

    I'm developing an application client which connects to a server and is meant to run on PCs. I want to make sure that my client application doesn't disconnect when the user moves from one network to another network (one cafe to another cafe).
    Is there any socket option to support this kind of client application requirements?

    EJP wrote:
    You had better take this up with Tim ( ) and the co-inventors if the Internet protocols.
    This nonsense is frequently encountered in newspapers and magazines, but I'm surprised to see it repeated here. Tim Berners-Lee is not an inventor or co-inventor of any Internet protocols except HTTP, which follows exactly the same principles as FTP, SMTP, etc: very tolerant line-oriented headers, and MIME-encoded data. These principles, not to mention the Internet protocols proper like IP, ICMP, UDP, TCP, etc., were invented by people like Vincent Cerf, decades before Berners-Lee had anything to do with it. Have a look at the authors and the dates on the RFCs. Berners-Lee is also credited with 'inventing' HTML which is a mild reworking of IBM SGML.:-) I stand corrected.

  • Time Capsule on a Roaming Network

    Hello everyone,
    Quick and hopefully simple questions.
    I just bought a 2TB time capsule.  Is there any good reason to setup partition(s)?  My household has 1 iMac and 3 Macbooks.  Would it be good to have a separate partition for each machine?  I am also open to having some network attached storage on the time capsule but don't find it absolutely nessasary.
    Lastly I plan on setting up a roaming network using my airport extreme(connected to the cable modem) and then run cat 6 to the time capsule and 2 other airport express units to get great wifi coverage throughout my house.  Anyone have any tips or advice on this setup?  I have checked the apple support site and understand the confing involved in setting up the roaming network, just wanted to poll the forums for any helpful advice.
    Thanks for your time!!

    Quick and hopefully simple questions.
    I just bought a 2TB time capsule.  Is there any good reason to setup partition(s)?  My household has 1 iMac and 3 Macbooks.  Would it be good to have a separate partition for each machine?  I am also open to having some network attached storage on the time capsule but don't find it absolutely nessasary.
    Answers are simple.. There is no way to partition a TC. Not without voiding warranty and removing the drive and doing it on a computer .. then returning the drive to the TC. So don't do it.
    You do not need to have separate partitions for each machine.. if you are going to use Time Machine as most people do, each computer will create its own sparsebundle which is kind of virtual disk partition. Each computer will use only its own sparsebundle and everything will be kept isolated from each other.
    I am not sure what you mean by using NAS .. do you mean a separate NAS plugged in or a USB drive or using some of the TC internal disk space for file sharing?? The later is not a great idea. TM and data do not generally get on too well.. And the TC is a backup target for TM.. it has no way to back itself up, nor can TM backup a network drive. So any files on the TC are not backed up.
    See pondini .. our TM guru master for all things TM.
    Basic info.
    See particularly Q3 here for sharing TM and data.
    Lastly I plan on setting up a roaming network using my airport extreme(connected to the cable modem) and then run cat 6 to the time capsule and 2 other airport express units to get great wifi coverage throughout my house.  Anyone have any tips or advice on this setup?  I have checked the apple support site and understand the confing involved in setting up the roaming network, just wanted to poll the forums for any helpful advice.
    Roaming is a good setup. Not a lot that goes wrong.
    BUT.. IMHO.. and it is that..
    Setup the whole wireless network using simple names.. no spaces pure alphanumeric.
    Since every unit gets the same SSID.. I do recommend a lot more manual control.. I simply don't trust the automagical system to work.
    You have only 3 non-overlapping channels at 2.4ghz.. 11, 6, 1 and you need to setup each unit on one of those channels.
    There are more channels at 5ghz and the range is poor so they tend to interfere less.. but AC wireless uses 80mhz and even N uses 40mhz. So take care to spread things.. and you decide. Hence I use separate names for 2.4ghz and 5ghz so I can force clients to use band I choose.. not the one they choose.
    Be experimental.. no one setup is ideal for everyone.. and since wireless is about 80% straight voodoo then try a few arrangements and see what works well for you. Be prepared to wipe the whole thing out and start over.. keep track of all the options you try in a log. (that is the science part.. log the voodoo!!)

  • Roaming Network Options?

    Can you explain this in more detail. I have been trying to understand what is the best way to "expand" the network in my house. Should I place my new AEBS in the ideal location, connected through ethernet as a bride and use the same SSID/Password as my router's network? Should I use WDS and Extend the network? Should I Extend the network but still connect to the router through ethernet? What are the differences between these?
    I want to have it where I can roam throughout the house and not have to worry about managing anything. I just want my devices to connect to the network and have a strong signal. Thank you.

    A "roaming" network is a configuration where all of the wireless access points or routers are connected back to a main router using an ethernet connection. This type of setup provides the best bandwidth performance for the network. Within reason, you can add as many wireless access points as you wish and place devices exactly where they are needed to provide as much wireless coverage as you wish. Commercial networks are designed using this type of configuration.
    An "extended" network is one in which the main router and remote devices communicate together over wireless only. The remotes supply additional wireless coverage in the area where they are located. Placement of the remote devices is critical because they must receive a good wireless signal to be able to "extend" it effectively.
    The basic "extend" configuration works like the hub and spokes of a wheel. The "main" router is the hub, so it needs to be in a central location within the home. The "remotes" are located as needed at the ends of the spokes. The remotes communicate directly to the hub, not to other devices at the ends of the other spokes.
    The two main drawbacks to this type of system are that the remotes must be located where they will receive a good signal and there is some bandwidth loss, about 10-15% per remote device on average. So, the more remotes you add, the more bandwidth you lose, but you get more's all a trade off. There's really no stated maximum number of remotes, but 3-4 would be about the practical limit for most homes. Many users use only 1-2 with good results.
    Finally, there is an older technology called WDS which allows a setup consisting of a "main", "relay" and "remotes". While it might seem that this would be a good choice, the performance hit is substantial...50% bandwidth loss for each "relay" or "remote" and the system will only work at "g" wireless levels, so you lose any advantage of faster "n" speeds on newer routers. This would not be a good choice for most users most of the time, but in situations where older "g" routers are used with newer "n" routers, it is the only choice available to extend a wireless network.

  • Resolving names of Mac OS clients over a network

    I support a number of OS X clients (both laptops and iMacs) in a Windows-centric environment. All of the Apple systems are running 10.6.x, and are not set up to use Active Directory (although the Windows clients do). We use Retrospect for backup, which supports both our Windows and OS X systems quite well, except that we've found that the hostnames of the OS X clients will randomly stop resolving- so we've been left with entering IP addresses for many of our OS X clients in the backup system. Since we use DHCP, this can be problematic if someone leaves their computer off for a couple of days, or for laptops which are only occasionally plugged into the wired network (but we need to catch them for backup whenever they may be connected). So far there doesn't seem to be any particular pattern to this, although things seem to work more often if the fully qualified name is used (systemname.domain, even though they're not joined to domain accounts) it isn't surefire.
    Does anyone else have any experience with this, and perhaps some suggestions?
    As a note, this is for a medium-size division within a large organization, and we don't have any control over the network environment. We could request static IPs for every Mac system but I don't think that would go over very well. This is a critical issue, because occasionally a system will stop resolving, stop backing up, and then we'll need to access recent backup data, only to find that it's not there- not good.
    I can provide any additional information needed for troubleshooting.

    Unless the workstations are in the same domain then you will have to open wide your Win dows domain or setup your own DNS internal server. Either that or join the Macs to the Domain.

Maybe you are looking for

  • Rejected Items

    All, Please see the scenario  : I dont have QM Module here . Batch Management is active here . So while doing goods receipt the Raw materials will go to Quality Ispection SLoc(unrestricted status)  and after quality Inspection ( physically ) , if it

  • How to Create a Group for Permissions?

    When I create a new folder, the default owner is my home directory name ("short name") and the default group is also my home directory name ("short name"). Why is this? What is a group? How do I create a group name if I want to pick one myself? Are t

  • How can I open TIF attachments on IPad?

    I have IOS 4.2.1 on my IPad. I cannot open TIF attachments on mail, even though I am able to do so on my IPhone 4. The setting to upload remote images is on. Any ideas?

  • TIFF generated with JAI won't fax

    I have tried to generate some simple black/white TIFF files with JAI, which I have then sent to a fax via a tool on an IBM AS/400. The TIFF files look fine on my computer, and the faxing tool also sends them without problems, but the result when the

  • Has anyone experienced this...

    ...when the PB wakes up from sleep, the airport did not pick up the IP address until I turn it off and turn it back on again....(self-assigned one with 169...) It has just happened about 3 days ago, before it was working normally. Do I have to check