|
Affiliate programs save you money! Shop online or order at Wired? ALL SITES AFFILIATED WITH WIRED?.
|
WE NOW HAVE 3 DIFFERENT ACCESS POINTS TO CONNECT YOUR NEW INTEL MAC.
wired for mac or pc (recommended)
wired (main modem) doesnt work with new intel mac with n cards
WIRED3 (conference room not recommended)
be close (outside table closest to CR.) OR in the room.
To Print from Mac OSX:
if you have OSX.4 just add a network printer
If you don't have OSX.4 (GOOD LUCK) FOLLOW THE INSTRUCTIONS BELOW.
THE SIMPLY WAY
-
EMAIL WHAT YOU WANT TO PRINT TO A YAHOO ACCOUNT
-
GET ON ONE OF OUR WINDOWS MACHINE AND PRINT.
1. Download (to your desktop) and install Gimp-Print 4.2.6 (be sure you
install it)
and for Jaguar (not needed for Panther) ESP Ghostscript version 7.05.6 (ESPGS)
Find these at: http://gimp-print.sourceforge.net/MacOSX.php3
2. Do the Unix Magic:
In a terminal window (Applications/Utilities/Terminal), enter the following commands one at a time:
1. copy the following
sudo ln -s /usr/bin/smbspool /usr/libexec/cups/backend/smb
paste in terminal window
terminal will ask you for your computers password ( if it has one)
hit enter.
2.copy the following
sudo killall -HUP cupsd
paste in terminal window
terminal will ask you for your computers password ( if it has one)
hit enter.
Don't type this! Use cut and paste. Ignore the cute remarks Terminal makes when you start it.
3. Double Click on Print Center (Applications/Utilities/PrintCenter)Printer List appears
Hold down Option key while you click on ADD
Choose ADVANCED
in DEVICE choose Windos Printer via Samba
Anything will work for Device Name
in Device URI enter smb://wired@computer2/hppsc750
in Printer Model choose HP
Then choose HP DesignJet 750
To network with a PC in the wireless system to transfer files
- go to finder
- go to go
- go to connect to server
- choose approved network
- choose approved computer
- type any user name and password
- or get user name and password from pc owner.
and your now able to share files with the pc. unfortunately the pc cannot share with the mac.
enjoy
To network with a Mac and a PC in the wireless system to transfer files
On the MAC:
in System Preferences, Sharing enable "Windows File Sharing" "Personal File
Sharing"
and "Remote Login"
in ACOUNTS configure a user with the rights to login
for the windows computer:
click
START
MY NETWORK PLACES
Add a Network Place
Add Network Place Wizzard appears
click
Next
click on Choose another network location
then click NEXT
In "Internet or Network address" type
\\192.168.0.131\sandra or what is says in your mac
under System Preferences, Sharing, Services (look for your address at the
bottom)
click NEXT
the wizzard responds: sandra on Samba 2.2.3a (build 26) (192.168.0.131)
click NEXT
click FINISH
if it asks for a username and password
enter a username and password from ACCOUNTS where you have given a user
the rights to login
EXTRA EXTRA
READ ALL ABOUT IT
NEW INTEL MAC PROBLEM CONNECTING WITH HOTSPOTS
If you have a new Intel Macbook, you may have noticed some problems connecting to Wifi hotspots like Internet Cafes and libraries. I never had such problems with my old iBook. The symptoms are as follows:
- Joined to an open network with no problem
- Unable to surf the Internet
- Your IP address is 169.something
- No amount of renewing DHCP leases or reboots will fix it
On a recent trip, I had this problem repeatedly at many different places. By
accident, I found a partial solution: Run the Network Diagnostics program
located in /System » Library » CoreServices. Somehow, Network Diagnostics is
able to get a valid IP address about eight out of ten times when nothing else
will.
Note that you can also get to Network Diagnostics through the Network System Preferences panel: click Assist Me, then Diagnostics.]
Thanks! All
that fiddling around in Network Preferences in my OS X years, and I never
noticed the "Assist me…" button.
What I've done at such times, is kindly to ask the PC user next to me if he
could show me his ipconfig, then gamble and set a manual IP address for myself
which is one or two numbers higher. An extremely embarrasing thing to ask (when
"everything is easier on a mac"), and also it might ruin the connection of other
network devices nearby. So the solution mentioned in the article is much better!
I like this
solution. In the past, I have seldom been able to get DHCP to work in remote
locations. Instead, I have manually assigned my own IP address and, if it is not
already assigned, the router will take it. One can usually tell what range to
use, but typically I just use 198.168.1.10, but sometimes the 1 is a 2 and
sometimes you have to dig deeper to see the real network address.
Then I also keep a record of the DNS servers I typically use from home and those
work remotely too (most of the time).
After an OS
X system and/or airport client (framework/driver) update on my systems, I have
found
that sometimes on the first startup after the update, it tries to join an
airport wireless network,
tries to get my join password from the Keychain, asks to update the keychain,
etc.
But I find that that executable called "airport" gets stuck. Therefore I am
never able to join my home
network. So when this happens, I forcibly kill that "airport" process, using
either Activity Monitor or using
a command-line kill. After that first run and kill, everything is fine.
This has happened from several OS X updates over the past couple of years. Hope
that helps someone; Larry
My Mac Book Pro had a lot of problems accessing the internet using the wireless connection. This morning I decided to figure it out and here is what I found for (more or less) useful information:
- Install the latest firmware 1.0.1
- For heat reasons, recalibrate your battery afterwards (not sure how this should help, but maybe Mac Voodoo helps). Not that I had any heat problems...
- Connect to your router using wireless
- Remove the key from the keychain application for your wireless router
- Enter the WEP Key (13 letters) not the 26letter hexcode (for whatever the reason this does not work).
- Thank the lord.
Firmware 1.0.1 with the latest airport driver indeed allows me to finally connect to public hotspots again.
Acquisition
and Mac OS X 10.3.9
I’m receiving an inordinate number of emails stating that Acquisition will not connect after running the Mac OS X 10.3.9. This has nothing to do with Acquisition. Rather, it appears that the 10.3.9 installer is, for many people, horribly broken. This is quite clearly an OS issue that affects all applications using Java, including Safari.
This issue is well documented on many Mac support sites and it is strongly recommended that you follow their guidance. Failing that, contact Apple support directly.
Note that this is not universal - I for one have not had any issues following the 10.3.9 upgrade. That said, my advice is this:
Do not, under any circumstances, install Mac OS X 10.3.9 until Apple corrects their botched installer.
Update: Apple has acknowledged that the 10.3.9 upgrade is botched. Nonethless, they are reportedly steadfastly refusing to either warn users or amend the botched installation package. This behavior is quite simply unacceptable for a company that claims to strive for software stability and usability. Culpability without corrective measures is empty and meaningless. For shame, Apple.
Update: Apple has released a software update.
Read this
http://discussions.apple.com/thread.jspa?threadID=797008&tstart=0
Mac OS X 10.4.8: AirPort does not auto-connect to existing networks after restart or wake from sleep Issue or symptom
After upgrading to Mac OS X 10.4.8, some Intel-based computers may not auto-connect to remembered networks that use WPA2 or WEP security. This article explains how to correct this behavior.
Products affected
-
Macs with Intel Core Duo-based processors:
- MacBook
- MacBook Pro (all models)
- Mac mini (Early 2006)
- iMac (Early 2006)
- Mac OS X 10.4.8
Solution
To restore the auto-connect feature:
1. From the Apple menu, choose System Preferences.
2. Select the Network pane.
3. From the "Show:" drop-down menu, choose "AirPort".
4. Make sure the "By default, join:" pop-up menu is set to "Preferred networks." (If it was set to "Automatic networks", you can set it back to Automatic after the next step.)
5. Select any network that shows WPA2 security and use the minus (-) button to remove those networks from the list.
6. Once all WPA2 networks have been removed from the list, use the plus (+) button to add them back. (You will need the appropriate passwords for the wireless network.) If it's more convenient, you can wait to re-add the networks until you use them—when you use a network, it will be added to the list automatically.
If in step 3, your default was Automatic rather than Preferred, go ahead and change your default back to Automatic.
Best answers yet
http://www.index-site.com/WIFI1048.html#COMPATIABLEROUTER
None of A Brody's
solutions helped me. I called Apple and the support person said it's a problem
with the gateway not the Mac and there were no known issues relating to the
latest updates. I mentioned that there was a buzz in the
Apple discussion area as well as on the Internet to which he responded that
people will write anything they want and their discussion boards are
user-to-user. Thanks, Apple.
Potential solution 1: I have been running my system without any
encryption and some people have found that adding WPA encryption solves the
problem (WPA is recommended over WEP). I'm going to try that next.
Potential solution 2: Wipe the drive and reinstall the system. Don't use
the migration tool if you are migrating from an non-intell Mac because you could
bring over incompatible settings. And don't update to 10.4.10. I really don't
want to do this.
Today I called Qwest and talked to a DSL support guy named Steve. He said that
he had a few calls last week on this issue and he was very appreciative of the
testing and research I had done.
He put me on hold and called Actiontec. (Actiontec charges $29.95 per incident if I call.) They said that yes, there is a problem with 802.11n Apple wireless cards. I don't know if they have linked anything specifically to the 10.4.10 update or not. They are working on it. They are hoping that Apple is working on it or will tell them more of what they are doing so they can make their Gateways compatible.
Try this, you can't connect to http://apple.com, but you can connect to http://17.254.3.183
- MacBook, MacBook Pro owners suffer keyboard...
- Freezing iMacs may be victims of hardware, not...
- Apple releases iMac freezing fix, MacBook Pro...
- Apple's iMac MXM Updater to cure iMac's Boot...
- Apple updates MacBook Pro battery firmware, QT...
System users in Apple's discussion forums (one, two), as well as those speaking directly with AppleInsider, say the problem first surfaced after the appearance of the Mac OS X 10.4.10 update this summer and so far is known to affect most models, though reports are currently scarce from buyers of Apple's fall 2007 units.
The exact behavior of affected systems can vary slightly, but appears to largely be connected to the computer's power supply. While the connection remains largely stable when plugged into an AC adapter, switching to battery power renders the wireless link intermittent and in many cases drops network access entirely when idle.
"Whenever I unplug my AC adapter, my wireless Internet goes a little crazy and starts continually disconnecting and reconnecting moments later," says one owner.
Users often can't detect nearby networks after restarting the card through software, but can almost always regain a dependable connection after reattaching the power plug. A handful of owners report having to restart the computer to restore the Wi-Fi connection, however.
To date, the intermittent connection issue has not been publicly acknowledged by Apple and affects systems regardless of subsequent Mac OS X updates. Both the recent 10.4.11 update and all current versions of Leopard continue to exhibit the symptoms of the problem, although some note the situation improving for their systems after the most recent upgrades to both Leopard and Tiger.
For those still affected, successful workarounds have included reverting to Mac OS X 10.4.9 when possible, and setting up commands in Terminal that send out data to keep the connection active. But since the issue does not occur when running Windows XP or Vista in Boot Camp, several users say Apple has no reason to leave the apparent flaw unresolved.
"Wi-Fi works OK under other OS X releases and also with Windows Vista running on the MacBook hardware," says one report. "Apple's engineers need to quit playing with their iPhones, roll up their sleeves and look for bugs."
/www.philosophersguild.com