AntonioRocco

Hi I also see this but only rarely. In all of the cases where i have seen it the problem has been down to the physical structure of the network itself. Network outlets and cables as well as switch and - occasionally - even the gateway. I would not rule out Duplex mismatching either. Ironically I have never seen this delay in environments that use split DNS or base their internal domain around something other than .local and moreover a .local domain that has only one word in its namespace. For example: domainname.local rather than subdomainname.domainname.local. I happen to know that HodgeHi's network is not based around .local but I think when he's seen the problem it's probably down to the NVIDIA chipset that came with the majority of his iMacs? I think he may agree with me on that one? Antonio Rocco (ACSA)

Hi ". . . . have noticed that the cc4 network login times are awful. is this a known issue/can it be resolved?" I would say it was as I've noticed this on RM's CC4 Networks since it was first rolled out. It was particularly bad to begin with and has - in my opinion - marginally improved only a little since. I'm not talking about Macs here. I am talking about purely PCs. If it's bad for them then it will be the same for Win7 installed on a Mac. Essentially the issue you're seeing has very little to do with the fact it's a Mac in my experience. There is a time sync issue when installing Windows OS on bare metal Macs. It's about an hour IIRC? So you might want to check your time sync. You do this on the PC side. In an SSO environment Server and Clients cant be out by more than 5 minutes. "Is it possible for the imac to boot straight into the windows partition from startup?" Yes. Either do this whilst logged into the Mac OS or the Windows OS. It's your choice. If you decide to do this on the Mac side log in as the local administrator and click on the Startup Disk Preference Pane - Apple Menu > System Preferences. Select Windows and click Restart. If you decide to do this on the PC side again log in as the local administrator and click on the BootCamp Icon in the task bar. Click on the BootCamp Control Panel and select Windows. Forgive me but if you genuinely want the Macs to always boot into Windows I have to ask Why? You could have bought twice that amount of PCs for half the price. Moreover you're not really giving students - or anyone else - a chance to use and become familiar with an OS or a different way of computing that is not based around Windows. Users can get their fill of Windows on the PCs you have already have. My 2p. Antonio Rocco (ACSA)

Hello Arthur Lion Server at the moment has gone pretty much the same way that Snow Leopard went the first time it was released. Hopeless and frustrating! Which appears to be the case if you read the horror stories over on the Lion Server Support Forum: https://discussions.apple.com/community/servers_enterprise_software/mac_os_x_lion_server However as is usual with most Support Forums, most (not all) will post if there are problems. Very few post reporting no problems at all. Most of those that post mentioning problems are having them because they've 'rolled their own' versions of Apache or Perl or SQL or Ruby and Samba and so on. Upgrades and/or Migrations from one version to another never go too well once you move away from Apple's stock install. Having said that some of the posts mentioning Open Directory being supremely mangled on Migration or Upgrade are disturbing. I've not had a chance to install/test Lion Server yet so I can't say one way or another. But - as alluded to before - there were many were moaning how 'bad' 10.6 Server was, when it first came out, when compared to 10.5. I remember someone saying 10.5 Server was twice as bad as Vista and that's saying something! Personally I've never had a problem with Vista. Then again my needs are simple and I don't expect too much. In my experience (and possibly yours?) OS X Server does not generally begin to 'settle down' until the .3 and/or .4 Updates are released. I half expect 10.7 Server to follow the same pattern. The 10.7 Client OS is actually OK and I and others have been running it quite happily the day it was released. It also works fine with AD and/or OD. Granted there are a few differences but nothing really major. Hopefully others may find this link helpful which lists some of them: Apple Tips Some Changes in Lion HTH? Antonio Rocco (ACSA)

Hi ". . . If I try logging in with an AD user account that doesn't exist within any of my OD groups, that login should be rejected . . ." Not true. A Mac Server (this is implied because you've mentioned an OD Group) is not directly involved in any authentication at all. Identification, Authentication and Authorisation is solely between your DC and the Mac Workstation - the hardware itself. If you require Technologies and/or Services that are only available on OS X Server then most - not all - can be Principles of the AD's Kerberos Realm and participate in Single Sign On. This still won't mean you can't log in. The only time the above statement could be true is if you applied a local (or LDAP) MCX that determines which Users or Groups are allowed to login on that/those workstation(s). If it's a local MCX this would be done using the Accounts Preferences Pane > Login Options. If applied using LDAP this would be done using a Computer MCX. This kind of lockdown can only applied at hardware level. To apply Managed Preferences (MCX - or if you like, mac-style GPOs) you'd either nest AD Users or Groups within an OD Group or create a Computer Group (Apple call this a List) and add Mac Workstations which have been joined to Open Directory. Regardless of whether those workstations have been bound to Active Directory or not, all users (including local ones) who attempt a login on those workstations will have those MCX applied. HTH? Antonio Rocco (ACSA)

Hi "Is this possible at all?" Yes and it's easier than you might think. Although it depends on how you have your AD Users Profile Settings configured? There's actually no real need for Augmented Records (which is just another way of doing AD-OD Integration or, if you like, Magic Triangle) either. If you've specified their Home Area location in the Profile Path then you simply add another Home Area location in the UNC Path and assign a suitable Drive Letter. This can be anywhere you like. Even a Mac Server. Assuming your Mac Server has the capacity and you've defined a suitable share point appropriately? All you need do thereafter is assign appropriate redirects using the Global Policies Management Console for the home area defined in the Profile Path and you've achieved dual homes. One for Users when they log into a PC and one for when they log into a Mac. Again depending on how you've structured and configured your AD this could be hard or easy work? From there your only possible problems are - albeit minor ones - finding some way to synchronize the data. Or at the least give access to Users Data depending on which platform they log into. Assuming this is something you want to provide? Your other potential issue will be backup. Clearly all this data - and once Macs are involved there will be lots of it, more than you think - will need backing up somewhere? Presumably? Although even this can be failry easily accommodated with a little bit of thought and with potentially no need for extra expense. Your only other problem after that is acquiring enough knowledge (a training course would be ideal/useful) in supporting a platform which is unfamiliar to you. HTH? Antonio Rocco (ACSA)

@bodminman Yes. @glennda You're more than welcome! Actually I'm not an Apple fan. Apart from being an ACSA (Apple Certified Systems Administrator) I'm also an MCSA (Microsoft Certified Systems Administrator). I can see the merits and de-merits of both platforms. Both have their strengths and weaknesses. I think the phrase 'Horses for Courses' could be applied although I have to question why you 'need' macs in a mature AD environment? Surely the units you already have are more than capable of being used to produce musical content as well as anything else deemed to be a mac's sole preserve? If it was me I would have asked what compelling reason does the school need to purchase macs? Looking nice would not be a compelling reason in my view. Having said that my own view is the platform stacks up pretty well when compared like for like. No doubt others will have their own opinions (rightly so) - usually based around costs and/or lack of understanding. Point 5 was always going to be a moot point for those that look at things with a firm - but jaundiced - 'Windows' eye. However the point is well made. There are currently no viruses, malware or any other kind of nastyware for the platform. How you tackle this fact is entirely up to you. If you're installing Anti-Virus software on a Mac it's not to protect the Mac. If your PCs already have up-to-date A/V installed what would be the point? At best all it gives you is another layer of defence for your PCs. Which is as good a reason as any I suppose? In 30 years of using computers of one kind or another, PC, Mac, Honeywell, Sun etc I've never installed any A/V software and I've never had a Virus. There are no mac applications AFAIK that are expressly designed to work with networked accounts. The fact that some of them do or sort of do, is a bonus. As ever YMMV. HTH? Antonio Rocco (ACSA)

Hi Apple Menu > System Preferences > Accounts Login Options. Click the Join button. Key in the domain name. You should be prompted for an account name and password that has authority for the AD Domain - eg: yourdomain.com. For that amount of Macs you can use any AD Users' account details. Some Do's 1) Make sure all Macs have unique names - Apple Menu > System Preferences > Sharing > Computer Name. 2) Make sure all Macs are referencing the same NTP Server - Apple Menu > System Preferences > Date & Time > Date & Time. Key in the DC's IP Address assuming the DC is your NTP Server? 3) Disable Automatic login and keep the default local administrator's name and password secret. Even from the Teachers. Apple Menu > System Preferences > Accounts > Login Options. The relevant setting should be fairly obvious. 4) Change the default Ageing level for Reverse DNS entries to 1 or 2 days. 5) Try and follow Microsoft's Best Practices. For example try and keep OUs to no more than 3 deep. Try and keep the container/folder structure fairly flat. Some Dont's 1) If you don't want User's home containers to be created locally access the Directory Utility. /System/Library/CoreServices. Click on the Active Directory plug-in and select the Show Advanced Options disclosure triangle. De-select the option. 2) If you're using .local as the .TLD for your internal domain you will have login issues. If your DNS and DHCP Services are configured correctly you hopefully won't see that many problems? Having said that expect some random and intermittent problems anyway. The .local suffix is reserved for Bonjour/Rendezvous Services which can't be switched off. 3) Once bound to your Domain Users will have full access to browsing the Network - you can't stop this. If your AD environment is not locked down with appropriate permissions or the macs are not in their own VLAN or subnet, you may find any user having complete and unrestricted access to just about every share/pc you've configured. Other Useful Pointers 1) There are no GPOs (apart from the password policy) that can be applied to Users logging onto a Mac - not without a Mac Server, altering the AD Schema or specialist and potentially expensive 3rd-Party help. 2) Once Macs are introduced into any AD environment they will inevitably find every flaw and weakness like nothing else. 3) Don't attempt to make Macs behave like a PC because they won't. 4) You can't deploy Mac applications from a PC 5) No matter what anyone tells you there are currently no viruses/exploits for the platform 6) Macs are fundamentally UNIX boxes so you can't log in without the existence of or the ability to create a home folder. The container/folder must have the shortname of the desired user - eg: Any Body (long name) anybody (short name) - set. That container must also allow that user read/write permission. 7) Avoid overly strict Quotas. 1GB should be enough for what you appear to require? The above is not an exhaustive list but should help? Antonio Rocco (ACSA)

Hi OSX Server can perform a Domain Controller Role if (a) it is an OD Master with Kerberos Running and (b) It is 'promoted' to a Primary Domain Controller in the SMB/Windows Service. As ever DNS has to be configured correctly and working on both pointers. You don't necessarily have to create SRV Records but it does help. OSX Server as a PDC is equivalent to a Windows NT 4 SP4 Domain Controller with some 'limited' Win2K Server-like functionality. What this means is XP and older Operating Systems can be joined to its domain and use roaming profiles specified for Users in the Windows tab in WorkGroup Manager. Assuming that's something you want? Vista is supported but not without hacking the registry first. Windows7 is not supported without 3rd-Party help. This is because Microsoft removed all support for NT Domain Controllers. Even then your mileage will vary. There are no 'policies' that can be applied to PCs using WorkGroup Manager or anything else available on OSX Server. What you can do is create scripts, batch files etc that can perform something similar which can be applied post successful login. Again this is done using the Windows tab in WorkGroup Manager. Ironically I have been to AD environments where everything is 'managed' using 3rd-Party scripts downloaded from the Internet. What Microsoft provides in the Group Policy Interface is not used at all. You can promote an OD Replica to a BDC but only if the PDC is an OD Master. What you can't easily do (if at all) is make OSX Server a BDC for a Windows PDC. Similarly you can't easily make a Windows Server a BDC for OSX Server in a PDC Role. I remember someone trying to do this about 4 years ago which did not turn out too well. OSX Server can be made a Domain Member in an AD environment. AFAIK and unless someone knows different you can't easily make a Windows Server a Domain Member in an OD Environment. HTH? Antonio Rocco (ACSA)

Hi "Has anyone successfully managed to set up software raid 1 on an xserve without reinstalling the operating system?" Yes. I do it all the time. However I always make sure I have a fully bootable cloned backup - just in case. In which case why bother? You may as well restore from the clone. The commands in the link you provided don't look right to me? Rather than trying to to this using the Installer DVD try Target Disk Mode (TDM) instead. Start up the Server in TDM (hold down the 'T' key on reboot) and connect it to any mac that accepts a firewire 800 cable connector. If you have a firewire cable that has 800 at one end or 400 at the other you can use that with hardware that only has firewire 400 outlets. Launch Terminal and issue this command: sudo diskutil list You should see something like this: /dev/disk0 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *499.1 GB disk0 1: GUID_partition_scheme *499.1 GB disk1 2: EFI 209.7 MB disk0s1 3: EFI 209.7 MB disk1s1 4: Apple_HFS ServerHD 485.1 GB disk0s2 5: Apple_HFS DataHD 485.1 GB disk1s2 All local drives will be part of the device tree located at /dev. Individual drives will follow that initial path with each additional drives being appended an ascending number. The above shows you the formatted partition followed by the initialised volumes To convert the above System Drive - ServerHD - to a RAID Mirror issue this command: sudo diskutil AppleRAID enable mirror /dev/disk0s2 This will place the system Drive into a degraded RAID Mirror state. You'll get feedback on the screen once this has been done. When finished disconnect the Server's drives and remove the firewire cable. Restart the Server. On successful login launch Disk Utility and add the other drive you're planning to use as the Secondary Mirror to the RAID Mirror you now see in Disk Utility. Depending on how much Data you have it can take a while. Your mileage as ever will vary. HTH? Antonio Rocco (ACSA)

Hi As already mentioned there is very little difference 'under the hood' between OSX Client and OSX Server. AFAIK ident is the client implementation on both. There is no specific ident server provided as a binary by default in either OSX Client or OSX Server builds. The manual pages seem indicate other requirements which you should explore if you're determined to pursue this. Perhaps you need to install fink or macports? You really may be better off by posting in the UNIX Forum for a better response. The link you've posted refers to a really old OS (analogous to Windows 98) and a completely different Processor Architecture. I would not base any further investigations into this based on that article. HTH? Antonio Rocco (ACSA)

If you mean the process daemon then it's not something specific or exclusive to OSX Server. Launch Terminal (Client or Server OS) and key in "man ident" without the quotes. Whether Apple's variant of UNIX is what you're used to or looking for is another question. Apple maintains a dedicated UNIX User-to-User Forum where your question may be better placed? https://discussions.apple.com/community/mac_os/mac_os_x_technologies?view=discussions&tagSet=1048 HTH? Antonio Rocco (ACSA)

Hi "Does the same thing work with Apple OSX?" Not in the way I think you mean. If you have a mac available that you're using as an administrating workstation you can install Apple Remote Desktop on that mac and install the 'driver' on all the other macs. This would be the way I would do it. You could still use the share approach but there's no way your Windows Server will 'know' how to install a non-Windows 'driver' on a 3rd-Party platform without some major assistance somewhere assuming such assistance was easily possible. To use the share approach you'd still have to go round each mac in turn and install it locally once you'd connected to the relevant share. I suppose it's a moot point but there are no printer 'drivers' as such for networked printers. For networked printers the 'driver' is really a PPD or Postscript Printer Description File. Basically a set of instructions in plain text form that describes what features and capabilities the printer has. There is no 'engine' as such "Does the driver have to be installed on every Mac?" Yes. HTH? Antonio Rocco (ACSA)

Hello Carter The only reason why I posted the link is because it's slightly amusing. Besides a little Apple bashing every now and then is not a bad thing IMO. As to what it's trying to get at? I've not figured that out yet. Antonio Rocco (ACSA)

Hi YouTube - College Humor- Charlie and the Apple Factory Antonio Rocco (ACSA) http://www.youtube.com/watch?v=dyowZgDcZFU

Hi Create another admin account, log in with it and try again. Does the problem go away now? Antonio Rocco (ACSA)

Hi Tom The reason why you're getting 404 errors is because those urls are not actually real websites. The kb article clearly states: "The latter (http://swcdn.apple.com) currently redirects to the Akamai content distribution network that hosts the updates. Note that the redirected IP address of http://swcdn.apple.com may vary over time or by geographic region." Those urls all redirect to the Akamai network. This network - or at least the Apple content distribution part of it - are not easily accessible using a web browser. The Software Update Preferences Pane in OSX Client and Server as well as the Software Update Service in OSX Server are designed to access this network in a way that's not transparent to the end user. It's looking more and more likely that either your local or upstream proxies are blocking access? You could look at running a traceroute to those urls and seeing at what point the trace stops? This is what I see when running traceroute from my network: traceroute swcdn.apple.com traceroute: Warning: swcdn.apple.com has multiple addresses; using 84.53.178.16 traceroute to a950.gi3.akamai.net (84.53.178.16), 64 hops max, 52 byte packets 1 cpc5-basf9-2-0-gw.12-3.cable.virginmedia.com (82.13.18.1) 11.185 ms 17.400 ms 12.472 ms 2 nott-core-1a-ge-310-2117.network.virginmedia.net (62.255.214.141) 9.763 ms 9.801 ms 7.952 ms 3 leed-bb-1a-as0-0.network.virginmedia.net (213.105.174.169) 59.333 ms 11.300 ms 14.284 ms 4 nrth-bb-1b-as2-0.network.virginmedia.net (62.253.185.101) 12.244 ms 15.058 ms 18.540 ms 5 nrth-tmr-2-ae6-0.network.virginmedia.net (213.105.159.34) 16.547 ms 17.583 ms 17.579 ms 6 tele-ic-1-as0-0.network.virginmedia.net (62.253.184.2) 16.097 ms 14.239 ms 15.834 ms 7 84.53.177.193 (84.53.177.193) 17.391 ms 17.921 ms 17.609 ms 8 84.53.178.16 (84.53.178.16) 15.146 ms 22.225 ms 17.224 ms If you're not seeing the same it's probably your firewall, filter or proxy or a combination of all three? You could also use the tcpdump utility to log traffic as it goes to and fro. Amongst the reams and reams of data you'll definitely see at what point packets are being dropped and which IP address/host is dropping those packets. Antonio Rocco (ACSA)

Hi There are other ways of doing this but for what you want you can create a run-once script on login that will either send a HUP signal to kill the Finder or to reboot the workstation - which achieves the same thing. There are numerous ways of creating this script. Either as a bash executable or as shell script that an Automator Script initiates for you. For general guidance or even specific instructions have a browse of Apple's Technologies Forums: This one is for AppleScript: Apple - Support - Discussions - AppleScript And this one is for Unix: Apple - Support - Discussions - Unix HTH? Antonio Rocco (ACSA)

Hi Tom DU's repair permissions is worthwhile to run although TBH I hardly ever do it. Still you never know? From the information you've provided most of it seems OK although you've not confirmed you've configured your workstations as the kb article advises? Antonio Rocco (ACSA)

Hi Tom SUS uses port 8088 for internal use only. Judging by the information you've provide your problem is there are no updates coming from Apple at all that makes it to your server. That has to be either a block or ACL on your network somewhere or something similar further upstream. If it's neither of those then either you've misconfigured the Server (fiddling with the Firewall Service perhaps?) or there's something fundamentally wrong with the Server itself? Either the OS is borked in some way or the underlying drive/directory structure is not as healthy as it could/should be? What is certain is traffic is clearly making its way out. It's the coming back in again that seems to be the problem? You could try using the tcpdump utility to see what pops up? You may have to run it for a while before you get anything useful back. Can you run Software Update on a client OK? Do updates come down then? Antonio Rocco (ACSA)

Hi mattx "in regards to encryption then this is something that will be changed when we move over to N" This may well be where the problems lies? There were issues with the latest N capable offering from Apple with older G-rated WAPs. It seems WPA-PSK TKIP/AES on a G-rated WAP is not quite the same as WPA-PSK TKIP/AES on an N-rated one. Even this can vary from Manufacturer to Manufacturer notwithstanding they should all be using the same RFC. The iPad Forum over on Apple's Support site may help? Apple - Support - Discussions - Wifi doesn't stay connected ... Apple - Support - Discussions - Cannot join network ... Apple - Support - Discussions - wifi problem with version 4 on iPad and ... Apple - Support - Discussions - iPad connects to WPA2 but not to WPA ??? ... Apple - Support - Discussions - Cannot connect to WLAN ... Apple - Support - Discussions - I think the wi fi is fixed ... Most if not all of the above list issues not really specific to your environment. I list them only to offer you a possible insight into tracking down your specific problem. "People expect their kit just to work. But when I explain it's a bit more complex than that and pass on the article written the other day, about why the network is not the same as your's at home, then sometimes they understand. But the majority of the time they don't." Absolutely! HTH? Antonio Rocco (ACSA)

Hi mattx LOL! Fair comment and I agree with a lot of what you say. I was not trying to start a flamed thread or throw abuse either. I was trying to help. When consulting with Educational sites looking at Apple hardware for the first time, the first thing I always ask is: "What do you think these things are going to give you that you can't already achieve with what you already have at half the cost?" Most of the time the answer is "I haven't a clue but they look nice". Once you go beyond the looks, there is actually something worthwhile there. If you can be bothered to look? You may not agree with it but Apple do seem to provide what most people seem to want? Form with Function. It can't more than coincidence that many other manufacturers copy what Apple start. It can't all be rubbish - can it? I hope you find a solution but it does seem odd you're having a problem as all of the sites I support that use iPads have little or no problems connecting wirelessly to a wide variety of devices. Sorry I could not help. Antonio Rocco (ACSA)

Hi The iPad does support WPA-PSK TKIP/AES and works with most WAPs/Routers/Firewalls. There must be something else going on? Possibly an ACL that queries the Computer Objects Container in AD? You may have to add the iPad's MAC address? Try changing to AES and see if that makes a difference? I've never heard of Aruba so it's possible there's another setting buried somewhere specific to the unit/manufacturer? Perhaps a call to the developer/manufacturer might get you somewhere? It's your choice if you don't want to know anything about Apple but to say on a Public Forum like this you 'hate' them is irrational and childish. You're an adult, grow up and deal with it. Antonio Rocco (ACSA)

Hi Apple's SUS won't work behind a Proxy that requires authentication: Mac OS X Server v10.4 or later: Requirements for Software Update Service Even if the Proxy is transparent you may find the LEA's upstream Filter blocking access? In my experience it happens a lot. Judging by what you've posted you should use the server's fqdn to access the service as per the kb's instructions. You may be able use the IP address, provided whatever you're using to resolve DNS can resolve the reverse pointer. Lookups from the platform may fail if you're using .local as the TLD for your domain. Depends on the namespace convention you've decided to use. Antonio Rocco (ACSA)

@salan "Well thats how ours came in. From an irrisponsible Mac user" Are you saying it's the mac that's made the user irresponsible? Or is it more likely it's the user who is irresponsible? If the Virus, Worm - whatever you want to call it - was introduced to your network on a pen drive then whatever you've installed to defend against this did not work or was not good enough. If it was a brand new virus it would not have mattered where it came from - mac or PC. You'd have been infected either way. The real point here is whatever the Virus was it did not affect the mac. Why bother spending time, money or effort on protecting something that needs no defence just yet. The comment about IT Companies not readily admitting to exploits is a valid one. Apple are no different from anyone else in that respect. Microsoft have to be more transparent because almost all the exploits out there target their platform. Why? Is it because they're popular? Perhaps it's because they're not popular? Maybe they're just easier to exploit? An easy target even? I would argue those reasons apply to Apple equally as well. Perhaps more so? So where are the OSX Specific Viruses, Trojan Horses and Worms? If you know of any - name them. Let's look them up and see what they do exactly. @DaveP It's inevitable this thread will generate debate of this sort regardless of whether the software is free or not. Antonio Rocco (ACSA)

@ZeroHour "Sigh . . . exploits are used by viruses . . ." If a virus does not exist for the platform how can it use an exploit? Granted it only takes the desire and will to create a virus to use an exploit - if it exists. One day someone - with the required talent - will be cheesed off with Apple for long enough to bother to write one. Until that day comes you won't be protected until after the event. The point is there's been plenty of time for someone to do just that. Yet no-one has. Why? Is it too difficult? They can't be arsed? The platform is not popular enough to warrant an attack? Can't see it somehow. Apple have been high profile for at least the last 5-6 years. Everyone knows what an iPod, iPhone and iPad are. Interestingly in that same period of time you've seen arguably some of the most effective and far reaching Virus attacks for the Windows platform - Conflicker (still doing the rounds at some Corporate and Educational sites I support), BlasterWorm, LoveSan, WelcherWorm etc. For OSX? Nothing. "Just because there have been no major uses yet the belief that osx is immune is silly considering exploits that can be used exist" Agreed. However I've not said the platform is immune. Eventually someone will have a go and when that day comes it will be news. If anything I doubt if Apple would try to deny it. In many ways it could be looked at as positive publicity. Apple being Apple will probably use it to their advantage. "Are these not reasonable sensible things to realise as IT professionals?" Agreed. But it's also sensible to look at the pros and cons of the platform and come to an informed decision. My informed decision based on what I know is - save some money because I don't need it. It's true that no modern OS is completely secure although I happen to think a lot depends on who's using it. If you're going to browse silly sites and consistently use P2P Software then you're going to get all the trouble you're asking for. My 2p. Antonio Rocco (ACSA)