Still no success with Self-Assigned IP

I don't see any answers to my previous question that work. My PowerBook G4 connects to my Airport Extreme Base Station but will not "take" and IP address and self-assigns instead. Last week with much fiddling (unfortunately not knowing what was working—trying all the suggestions here) it reconnected, but this morning it was no go again. Other computers (both Airport connected and Ethernet connected) are doing fine on the network.
Any more ideas?

I tried WEP, WPA Personal and none.  Nothing works.  In fact, with WPA Personal I see the Airport gets a self-assigned IP for about 1 second,then drops.  The others get a self-assigned IP but of course it is bogus and there is no connection. 
Like I said, the MacBook connects to a very old (circa '01) Netgear wireless-B router with WEP, so it is something about this Linksys wireless router.
Message Edited by hb.240z on 02-26-2009 10:32 AM

Similar Messages

  • MacBook Pro can't actually connect to Wi-Fi with Self-Assigned IP

    Hi there
    I have a 15 inch MacBook Pro and it can connect to Wi-Fi but have no actual data coming in. And it says self-assigned IP.
    This only happens to my home Wi-Fi, however, I can connect and use Wi-fi at school or anywhere else perfectly. In the mean time, my Android phone and my flatmates' Windows have no problem using the Wi-Fi. The problem has been going on and off for a month, sometimes it works again and sometimes it goes wrong like this again.
    During this time I mostly use my other MacBook Pro 13 inch Retina. Until today, this problem happens on my 13 Retina mac for the first time, and the 15 Pro again as well. A few days ago, my 15 Pro started working again, and today they just gone wrong together at the same time.
    I just found out that my 15 pro can still work if connected to ethernet, but I can't just work in the living room, where the router is. And as you know Retina doesn't support Ethernet.
    I've check on the Internet and found many people have the same problem as I do. I also tried lots of ways to fix it with the information I found online. And nothing works. I even suspect that it's actually my flatmate blocks me out with some setting on the router (Is it possible?)
    Anyways, can someone please help me fix it thoroughly... Please and thanks.

    Each country regulates wireless networking differently. Wi-Fi devices are restricted to certain frequencies and power levels. The client devices try to find out where they are and configure themselves accordingly. Since a wireless access point (WAP) usually does not move across national boundaries, the Wi-Fi regulatory domain (country code) is set by querying the first one to respond when the client initializes itself. You don't have any direct control over it on the client. If your device is picking up the wrong country code, and is therefore locked out of using some Wi-Fi channels or operating at full power, the only lasting solution is to fix or remove the misconfigured WAP.
    To find out which WAP's are broadcasting a wrong country code, do as follows.
    Triple-click anywhere in the line below on this page to select it:
    /S*/*/P*/*/*/*/*/airport -s | open -ef
    Copy the selected text to the Clipboard by pressing the key combination command-C.
    Launch the built-in Terminal application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
    Paste into the Terminal window by pressing command-V.
    The command may take a noticeable amount of time to run. Wait for a new line ending in a dollar sign ($) to appear.
    A TextEdit window will open with the output of the command. The first line should look like this:
    SSID BSSID RSSI CHANNEL HT CC SECURITY (auth/unicast/group)
    Each line below that one represents a WAP within range. Compare the two-letter code in the column headed "CC" with the ISO code for your country. The code "X0" means that the country couldn't be determined. If a WAP with a wrong code is not under your control, try restarting the computer as close as possible to your own router.

  • TiBook with self-assigned IP Address Only

    I have a titanium powerbook that has stopped connecting to the internet via the ethernet port. (It does find the internet via its Airport Card, however.) The network utility states that my powerbook as no ISP and a self-assigned one is used instead. I've tried powering down the modem for five minutes. (There is no router.) I've also confirmed that the ethernet source is not the problem, because my G4 Tower connects to the internet via the same cable.
    Any suggestions are welcome.
    Thanks,
    Trevor Monroe

    Hi Tim,
    Generally speaking, if a computer is set up for DHCP but it can't find a DHCP server, it will assign itself an IP address for that interface.
    It sounds to me like the iBook is having trouble talking to the AX (DHCP server). This could be caused by a variety of things, from failing hardware to software bugs to configuration issues.
    Has this only happened the one time? If this has only happened once, I'd call it a fluke. If it is or gets to be a frequent thing, we'll need to dig a little bit deeper.

  • Self Assigned IP address – can't figure this out. Frustrated.

    This is a long post but bear with me. It proposes a challenge for the mac connoisseur. Who knows? Might be fun?
    OK, here goes:
    Please help. I have been trying to fix this for about 7 months. I first noticed this issue when I started traveling around the country, from hotel to hotel. While others (PC's and Mac's) had no trouble connecting to the free wifi at these hotels, I did. I kept getting "self-assigned i.p."
    This was extremely frustrating. I often had to call up the i.t. guys and ask them to help me manually put in ip address, subnet mask, router (gateway), and dns. This worked much of the time but not always.
    Let me also say that, sometimes it worked perfectly! I'd say about 25% of the time (at these hotels) my internet worked perfectly – just connected immediately. The other 75... "self-assigned i.p."
    I just spoke to the mac "geniuses" and they told me it's not an issue with my computer at all (either hardware or software). Are you kidding me?!?! How can they explain everyone else's internet working except mine. And I'm talking like 100 or more different hotels in a 4 month period. They were trying to tell me that it was just a coincidence every time! "You'd be surprised" one guy said. Hahaha. They said that the routers aren't accepting my computer's whatever. OK, well WHY?! The router works for everyone but me. It's something wrong with my computer right?! Well no one acknowledged this.
    More background info:Just had my airport card and logic board replaced. Computer came back and the sheet said "passed all hardware tests." BUT, none of my issues (I had other ones too involving battery life and not being able to access certain websites) were fixed.
    I went to an apple store. They told me to do an erase and reinstall or whatever. So I did that (by dragging and dropping everything I'd saved on an external hard drive using disk utility). By the way, I also upgraded from leopard to snow leopard. So now, if I have the same issues after this I'll know both leopard and snow leopard are screwed up.... right?
    OK, so I followed their instructions on deleting and reinstalling to a tee and guess what?! Everything worked! Or so it seemed. Battery fine. Websites now accessible. I figured the airport issue was fixed too. But now that I'm not touring anymore and the airport works in my house, I never encountered any issues. Until now. At my work.
    I got a new job and it's one in which I HAVE to have a computer that connects to the internet. So of course, the same issue with self assigned i.p. presents itself. Everyone else in the office has no problem. Including a Mac person that used to work there.
    I've been reading some other threads that are just completely confusing me. One of them might be the solution but I thought I'd detail my troubles so that some smart computer person out there can diagnose my specific problem and give me a specific fix.
    I noticed that many people believe there was a bug in one of the 10.5 updates. I am pretty quick to install updates (maybe I shouldn't be because I hear that the first updates are often buggy and maybe you should wait for a while). But this problem has continued now with Snow Leopard too so... I don't know. I don't know anything anymore. I have tried everything. And Apple is telling me it's not a problem with my computer. Give me a break.
    One more interesting quirk: before doing the erase and reinstall my computer could not find the Apple Store's network. After the erase and reinstall it works. That's why I assumed everything was fine! But no. And now the Mac people are saying there's no problem because they can't see it.
    BTW, I have tried all the obvious things. It's not an obvious thing. But I mean, if you think it is... then tell me I guess. But I've been in the advanced tab thousands of times. I feel like I've exhausted everything in there.
    Thank you thank you thank you in advance if someone is actually able to solve my issue.

    continuation of console log:
    Feb 1 13:08:45 localhost kernel[0]: npvhash=4095
    Feb 1 13:08:45 localhost kernel[0]: PAE enabled
    Feb 1 13:08:45 localhost kernel[0]: 64 bit mode enabled
    Feb 1 13:08:45 localhost kernel[0]: Darwin Kernel Version 10.2.0: Tue Nov 3 10:37:10 PST 2009; root:xnu-1486.2.11~1/RELEASE_I386
    Feb 1 13:08:45 localhost kernel[0]: vmpagebootstrap: 507215 free pages and 17073 wired pages
    Feb 1 13:08:45 localhost kernel[0]: standard timeslicing quantum is 10000 us
    Feb 1 13:08:45 localhost kernel[0]: migtable_maxdispl = 73
    Feb 1 13:08:45 localhost kernel[0]: AppleACPICPU: ProcessorId=0 LocalApicId=0 Enabled
    Feb 1 13:08:45 localhost kernel[0]: AppleACPICPU: ProcessorId=1 LocalApicId=1 Enabled
    Feb 1 13:08:45 localhost kernel[0]: calling mpopolicyinit for TMSafetyNet
    Feb 1 13:08:45 localhost kernel[0]: Security policy loaded: Safety net for Time Machine (TMSafetyNet)
    Feb 1 13:08:45 localhost kernel[0]: calling mpopolicyinit for Quarantine
    Feb 1 13:08:45 localhost kernel[0]: Security policy loaded: Quarantine policy (Quarantine)
    Feb 1 13:08:45 localhost kernel[0]: calling mpopolicyinit for Sandbox
    Feb 1 13:08:45 localhost kernel[0]: Security policy loaded: Seatbelt sandbox policy (Sandbox)
    Feb 1 13:08:45 localhost kernel[0]: Copyright (c) 1982, 1986, 1989, 1991, 1993
    Feb 1 13:08:45 localhost kernel[0]: The Regents of the University of California. All rights reserved.
    Feb 1 13:08:45 localhost kernel[0]: MAC Framework successfully initialized
    Feb 1 13:08:45 localhost kernel[0]: using 10485 buffer headers and 4096 cluster IO buffer headers
    Feb 1 13:08:45 localhost kernel[0]: IOAPIC: Version 0x20 Vectors 64:87
    Feb 1 13:08:45 localhost kernel[0]: ACPI: System State [S0 S3 S4 S5] (S3)
    Feb 1 13:08:45 localhost kernel[0]: mbinit: done (64 MB memory set for mbuf pool)
    Feb 1 13:08:45 localhost kernel[0]: rooting via boot-uuid from /chosen: 5924DB5A-4C9F-323F-BC39-2469AEAB4D18
    Feb 1 13:08:45 localhost kernel[0]: Waiting on <dict ID="0"><key>IOProviderClass</key><string ID="1">IOResources</string> <key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict>
    Feb 1 13:08:45 localhost kernel[0]: com.apple.AppleFSCompressionTypeZlib load succeeded
    Feb 1 13:08:45 localhost kernel[0]: AppleIntelCPUPowerManagementClient: ready
    Feb 1 13:08:45 localhost kernel[0]: FireWire (OHCI) TI ID 8025 built-in now active, GUID 001b63fffe8a7584; max speed s800.
    Feb 1 13:08:45 localhost kernel[0]: Got boot device = IOService:/AppleACPIPlatformExpert/PCI0 /AppleACPIPCI/SATA@1F,2/AppleICH8AHCI/PRT0@0/IOAHCIDevice@0/AppleAHCIDiskDriver /IOAHCIBlockStorageDevice/IOBlockStorageDriver/FUJITSU MHW2120BH Media/IOGUIDPartitionScheme/Untitled@2
    Feb 1 13:08:45 localhost kernel[0]: BSD root: disk0s2, major 14, minor 2
    Feb 1 13:08:45 localhost kernel[0]: [Bluetooth::CSRHIDTransition] switchToHCIMode (legacy)
    Feb 1 13:08:45 localhost kernel[0]: [Bluetooth::CSRHIDTransition] transition complete.
    Feb 1 13:08:45 localhost kernel[0]: CSRUSBBluetoothHCIController::setupHardware super returned 0
    Feb 1 13:08:45 localhost kernel[0]: AppleIntelCPUPowerManagement: initialization complete
    Feb 1 13:08:45 localhost kernel[0]: AppleYukon2: Marvell Yukon Gigabit Adapter 88E8055 Singleport Copper SA
    Feb 1 13:08:45 localhost kernel[0]: AppleYukon2: RxRingSize <= 1024, TxRingSize 256, RXMAXLE 1024, TXMAXLE 768, STMAXLE 3328
    Feb 1 13:08:46 localhost kernel[0]: yukon: Ethernet address 00:1b:63:94:9c:ad
    Feb 1 13:08:46 localhost kernel[0]: systemShutdown false
    Feb 1 13:08:47 localhost kernel[0]: NVDANV50HAL loaded and registered.
    Feb 1 13:08:47 localhost kernel[0]: Previous Shutdown Cause: 5
    Feb 1 13:08:47 localhost kernel[0]: Atheros: mac 12.2 phy 8.1 radio 12.0
    Feb 1 13:08:47 localhost kernel[0]: DSMOS has arrived
    Feb 1 13:08:47 localhost kernel[0]: AirPort_AthrFusion: Ethernet address 00:1e:52:77:13:82
    Feb 1 13:08:47 localhost kernel[0]: IO80211Controller::dataLinkLayerAttachComplete(): adding AppleEFINVRAM notification
    Feb 1 13:08:56 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Down on en1. Reason 1 (Unspecified).
    Feb 1 13:09:05 Michael-Pines-MacBook-Pro kernel[0]: Warning - com.apple.driver.InternalModemSupport declares no kernel dependencies; using com.apple.kernel.6.0.
    Feb 1 13:09:13 Michael-Pines-MacBook-Pro kernel[0]: en1: 802.11d country code set to 'US'.
    Feb 1 13:09:13 Michael-Pines-MacBook-Pro kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 149 153 157 161 165
    Feb 1 13:12:08 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Up on en1
    Feb 1 13:15:38 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
    Feb 1 13:15:39 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Up on en1
    Feb 1 13:18:08 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
    Feb 1 13:18:08 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Up on en1
    Feb 1 13:31:48 Michael-Pines-MacBook-Pro kernel[0]: hibernate image path: /var/vm/sleepimage
    Feb 1 13:31:48 Michael-Pines-MacBook-Pro kernel[0]: sizeof(IOHibernateImageHeader) == 512
    Feb 1 13:31:48 Michael-Pines-MacBook-Pro kernel[0]: Opened file /var/vm/sleepimage, size 2147483648, partition base 0xc805000, maxio 400000
    Feb 1 13:31:48 Michael-Pines-MacBook-Pro kernel[0]: hibernate image major 14, minor 2, blocksize 512, pollers 5
    Feb 1 13:31:48 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Down on en1. Reason 7 (Frame received from nonassociated STA).
    Feb 1 13:31:48 Michael-Pines-MacBook-Pro kernel[0]: hibernateallocpages flags 00000000, gobbling 0 pages
    Feb 1 13:31:48 Michael-Pines-MacBook-Pro kernel[0]: en1: 802.11d country code set to 'US'.
    Feb 1 13:31:48 Michael-Pines-MacBook-Pro kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 149 153 157 161 165
    Feb 1 13:31:50 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Up on en1
    Feb 1 13:31:50 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Down on en1. Reason 7 (Frame received from nonassociated STA).
    Feb 1 13:31:50 Michael-Pines-MacBook-Pro kernel[0]: System SafeSleep
    Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: hibernatepage_listsetall start
    Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: hibernatepage_listsetall time: 114 ms
    Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: pages 274489, wire 35250, act 50684, inact 887, spec 62, zf 137, throt 0, could discard act 24613 inact 28670 purgeable 6142 spec 128044
    Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: hibernatepage_listsetall found pageCount 87020
    Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: IOHibernatePollerOpen, mlget_interruptsenabled 0
    Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: IOHibernatePollerOpen(0)
    Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: writing 86158 pages
    Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: image1Size 73471488
    Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: PMStats: Hibernate write took 4108 ms
    Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: all time: 4108 ms, comp time: 592 ms, deco time: 0 ms,
    Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: image 166148608, uncompressed 353234944 (86239), compressed 162715248 (46%), sum1 dc78ee00, sum2 4fe372a2
    Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: hibernatewriteimage done(0)
    Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: sleep
    Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: Wake reason = UHC3
    Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: System Wake
    Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: Previous Sleep Cause: 0
    Feb 1 13:41:07 Michael-Pines-MacBook-Pro kernel[0]: USB (UHCI)ort 2 on bus 0x5d has remote wakeup from some device
    Feb 1 13:41:08 Michael-Pines-MacBook-Pro kernel[0]: en1: 802.11d country code set to 'US'.
    Feb 1 13:41:08 Michael-Pines-MacBook-Pro kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 149 153 157 161 165
    Feb 1 13:41:09 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Up on en1
    Feb 1 13:50:04 Michael-Pines-MacBook-Pro kernel[0]: IOHIDSystem::relativePointerEventGated: VBL too high (33307137), capping to 20000000
    Feb 1 13:55:23 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
    Feb 1 13:55:23 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Up on en1
    Feb 1 13:59:32 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
    Feb 1 13:59:32 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Up on en1
    Feb 1 15:24:13 Michael-Pines-MacBook-Pro kernel[0]: systemShutdown true
    Feb 1 15:24:13: --- last message repeated 1 time ---
    Feb 1 15:24:13 Michael-Pines-MacBook-Pro kernel[0]: Kext loading now disabled.
    Feb 1 15:24:13 Michael-Pines-MacBook-Pro kernel[0]: Kext unloading now disabled.
    Feb 1 15:24:13 Michael-Pines-MacBook-Pro kernel[0]: Kext autounloading now disabled.
    Feb 1 15:24:13 Michael-Pines-MacBook-Pro kernel[0]: Kernel requests now disabled.
    Feb 1 15:24:32 localhost kernel[0]: npvhash=4095
    Feb 1 15:24:32 localhost kernel[0]: PAE enabled
    Feb 1 15:24:32 localhost kernel[0]: 64 bit mode enabled
    Feb 1 15:24:32 localhost kernel[0]: Darwin Kernel Version 10.2.0: Tue Nov 3 10:37:10 PST 2009; root:xnu-1486.2.11~1/RELEASE_I386
    Feb 1 15:24:32 localhost kernel[0]: vmpagebootstrap: 507215 free pages and 17073 wired pages
    Feb 1 15:24:32 localhost kernel[0]: standard timeslicing quantum is 10000 us
    Feb 1 15:24:32 localhost kernel[0]: migtable_maxdispl = 73
    Feb 1 15:24:32 localhost kernel[0]: AppleACPICPU: ProcessorId=0 LocalApicId=0 Enabled
    Feb 1 15:24:32 localhost kernel[0]: AppleACPICPU: ProcessorId=1 LocalApicId=1 Enabled
    Feb 1 15:24:32 localhost kernel[0]: calling mpopolicyinit for TMSafetyNet
    Feb 1 15:24:32 localhost kernel[0]: Security policy loaded: Safety net for Time Machine (TMSafetyNet)
    Feb 1 15:24:32 localhost kernel[0]: calling mpopolicyinit for Quarantine
    Feb 1 15:24:32 localhost kernel[0]: Security policy loaded: Quarantine policy (Quarantine)
    Feb 1 15:24:32 localhost kernel[0]: calling mpopolicyinit for Sandbox
    Feb 1 15:24:32 localhost kernel[0]: Security policy loaded: Seatbelt sandbox policy (Sandbox)
    Feb 1 15:24:32 localhost kernel[0]: Copyright (c) 1982, 1986, 1989, 1991, 1993
    Feb 1 15:24:32 localhost kernel[0]: The Regents of the University of California. All rights reserved.
    Feb 1 15:24:32 localhost kernel[0]: MAC Framework successfully initialized
    Feb 1 15:24:32 localhost kernel[0]: using 10485 buffer headers and 4096 cluster IO buffer headers
    Feb 1 15:24:32 localhost kernel[0]: IOAPIC: Version 0x20 Vectors 64:87
    Feb 1 15:24:32 localhost kernel[0]: ACPI: System State [S0 S3 S4 S5] (S3)
    Feb 1 15:24:32 localhost kernel[0]: mbinit: done (64 MB memory set for mbuf pool)
    Feb 1 15:24:32 localhost kernel[0]: rooting via boot-uuid from /chosen: 5924DB5A-4C9F-323F-BC39-2469AEAB4D18
    Feb 1 15:24:32 localhost kernel[0]: Waiting on <dict ID="0"><key>IOProviderClass</key> <string ID="1">IOResources</string><key>IOResourceMatch</key> <string ID="2">boot-uuid-media</string></dict>
    Feb 1 15:24:32 localhost kernel[0]: com.apple.AppleFSCompressionTypeZlib load succeeded
    Feb 1 15:24:32 localhost kernel[0]: AppleIntelCPUPowerManagementClient: ready
    Feb 1 15:24:32 localhost kernel[0]: FireWire (OHCI) TI ID 8025 built-in now active, GUID 001b63fffe8a7584; max speed s800.
    Feb 1 15:24:32 localhost kernel[0]: Got boot device = IOService:/AppleACPIPlatformExpert/PCI0/AppleACPIPCI/SATA@1F,2/AppleICH8AHCI/PR T0@0 /IOAHCIDevice@0/AppleAHCIDiskDriver/IOAHCIBlockStorageDevice/IOBlockStorageDriv er /FUJITSU MHW2120BH Media/IOGUIDPartitionScheme/Untitled@2
    Feb 1 15:24:32 localhost kernel[0]: BSD root: disk0s2, major 14, minor 2
    Feb 1 15:24:32 localhost kernel[0]: [Bluetooth::CSRHIDTransition] switchToHCIMode (legacy)
    Feb 1 15:24:32 localhost kernel[0]: [Bluetooth::CSRHIDTransition] transition complete.
    Feb 1 15:24:32 localhost kernel[0]: CSRUSBBluetoothHCIController::setupHardware super returned 0
    Feb 1 15:24:32 localhost kernel[0]: AppleIntelCPUPowerManagement: initialization complete
    Feb 1 15:24:32 localhost kernel[0]: AppleYukon2: Marvell Yukon Gigabit Adapter 88E8055 Singleport Copper SA
    Feb 1 15:24:32 localhost kernel[0]: AppleYukon2: RxRingSize <= 1024, TxRingSize 256, RXMAXLE 1024, TXMAXLE 768, STMAXLE 3328
    Feb 1 15:24:33 localhost kernel[0]: yukon: Ethernet address 00:1b:63:94:9c:ad
    Feb 1 15:24:33 localhost kernel[0]: systemShutdown false
    Feb 1 15:24:44 localhost kernel[0]: Previous Shutdown Cause: 5
    Feb 1 15:24:44 localhost kernel[0]: Atheros: mac 12.2 phy 8.1 radio 12.0
    Feb 1 15:24:44 localhost kernel[0]: NVDANV50HAL loaded and registered.
    Feb 1 15:24:44 localhost kernel[0]: DSMOS has arrived
    Feb 1 15:24:44 Michael-Pines-MacBook-Pro kernel[0]: AirPort_AthrFusion: Ethernet address 00:1e:52:77:13:82
    Feb 1 15:24:44 Michael-Pines-MacBook-Pro kernel[0]: IO80211Controller::dataLinkLayerAttachComplete(): adding AppleEFINVRAM notification
    Feb 1 15:24:45 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Down on en1. Reason 1 (Unspecified).
    Feb 1 15:24:45 Michael-Pines-MacBook-Pro kernel[0]: en1: 802.11d country code set to 'US'.
    Feb 1 15:24:45 Michael-Pines-MacBook-Pro kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 149 153 157 161 165
    Feb 1 15:24:51 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Up on en1
    Feb 1 15:24:52 Michael-Pines-MacBook-Pro kernel[0]: Warning - com.apple.driver.InternalModemSupport declares no kernel dependencies; using com.apple.kernel.6.0.
    Feb 1 15:25:35 Michael-Pines-MacBook-Pro kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).

  • Airport has self-assigned IP address, authentication step fails

    I am a computing consultant at a Pennsylvania university and am trying to configure the airport service on a 15" MacBook Pro (pre-unibody style ~2007) running 10.6.5.
    We are trying to connect to a WPA2 Enterprise wireless network that requires username and password authentication before assigning an IP address. We configure Macs all the time here and they all work very well, in fact my own personal Macs haven't ever given me trouble. But the machine I'm working on at the moment just cannot obtain a correct IP address. We know for sure this is not a network or user account credential problem. It must be on the client computer side.
    I have tried removing all old user profiles and certificates from the Keychain (our network grants a certificate automatically for new connections), I deleted preference files from the /Library/Preferences/SystemConfiguration folder, I have removed the Airport service from Network Connections, rebooted the machine and performed 3 PRAM resets just for good measure, re-added the Airport service and tried a fresh configuration. I also created and entirely different user account and tried configuring. The only thing I have not tried is reinstalling the OS which I'm really trying to avoid because I'd like to learn what is actually causing this problem. None of the above attempts have been successful.
    Has anyone encountered this before in an enterprise environment? Does anyone have any ideas that I should try?
    Thanks in advance!

    Something like one year ago or so, i had to reinstall the OS cuz i wasn't able to make the iPhone recognized over usb for the tethering conenction...
    only AFTER i found out it was related to the OS booting in 64 bits, not just 32 and using the 64 capability for those programs who required it.
    I had to deal with self assigned ip too, while sharing internet conenction from airport through ethernet to another mac, but i dunno if that should help you.

  • Self assigned IP Address, wireless doesn't work

    After upgrading to Leopard I keep getting "AirPort has a self-assigned IP address and may not be able to connect to the Internet." when I try to connect to the wireless network. Thus, wifi does not work at all. I've researched it best I can and it seems to be a problem with the router assigning an IP address to the mac, but why didn't this happen in Tiger? However if I play around with it for awhile it will randomly start working, but the same method doesn't fix it everytime. It also works fine in bootcamp. If I physically plug into the router, it works fine. This problem didn't exist in Tiger at all.
    Message was edited by: SuperDupe453

    Follow-up:
    On the two laptops, I finally managed to get on line by switching to a different wireless access point, on a different modem. I surmise that the communication between the Macbook DHCP client and the modem/router's DHCP server is less than 100% effective. Looking at the modem/router, I could see that all of the Macs had active connections. But, instead of showing the names of the Macs, the page showed a star (*) for each Mac. I had to compare Mac addresses to verify the connections. The MAC address, of course, is hard-wired into the computer's network interface. It appears that either the DHCP client didn't know what question to ask when it broadcast for an IP address, or it couldn't interpret the answer. Except in the case of the iMac, which worked perfectly.
    I upgraded the MacPro last, since it is my primary machine. Same story--connection with self-assigned address, which is useless. However, this time, having nothing left to lose, I restarted the modem/router, which presumably dumped any inactive connections and issued new DHCP leases.
    However, I do have a few words for the Apple GENIUSES! The Leopard network preferences page puts me in mind of a maintenance free battery. A few of the older folks will remember when you bought a car battery that had to be filled with distilled water to reconstitute the electrolyte. Then, periodically, you check the level of the liquid in the battery, and added distilled water when required. Adding water was required on occasion because some of the water would boil off under certain conditions. Then, we got the maintenance free battery, which is virtually identical to the older battery design, except that you don't have to perform the maintenance of replenishing the water. It turns out, however, that maintenance free batteries do vent on occasion, and should have water added. But, you can't add water because the battery is sealed. So, the difference between conventional and maintenance free is not that the maintenance free battery doesn't need maintenance, it is that you can't perform the maintenance without voiding the warranty.
    The Leopard network preference page won't let you set the parameters that could restore a connection. If the DHCP client doesn't work automatically, you're stuck.

  • Airport Self-Assigned IP, the wireless doesn't connect to the internet

    Hello Everyone,
    I have a problem with my airport shows that has a self-assigned IP address and the DCHP doesn't renew, I tried a manually IP but doesn't work neither, I saw this problem about 4 days ago, and I search here in this same sub-forum, I saw that people with Macbook Alu 13'' having exact same problem as for the iMac 27'' Ethernet or Wireless with self-assigned IP have tried everything but nothing seems to work.
    I'll leave this link here, maybe someone can be helped with it, I tried but doesn't work...
    http://stevejamesson.com/2008/10/01/reset-mac-os-x-network-configuration-factory -default-airport-interface-disappeared/
    Please if someone has same problem and can solve it please help me...

    please help me...

  • Self assigned IP : still no bug fix ?

    I have a problem for a long time with my Time Capsule. I use an ADSL modem and router (from Free French ADSL Provider) and my TC is plugged on it and set to "Bridge" mode.
    I have many devices wired and wireless on the TC. But I have a big problem, sometimes (not all the time), my MacBook is getting a "169.254.x.x" IP address, a self assigned IP.
    That's weird because sometimes it works well from 6 AM to 7 PM for example, then at 7 PM it doesn't work anymore. There is no reason why, because I haven't touch anything in my network.
    It's pretty annoying. Is Apple aware of this problem  ? Can we hope a fix soon ? I had many problems with the WIFI on my Mac (before, it was the "wake up" WIFI problem but it seems to be fixed in the last Lion update).
    I've tried everything, reset all (TC, Macbook etc.), sometimes it works a day, the other day it's not
    Thanks

    7pm sounds too specific to me.. get a wifi analysing software, kismet on the mac but inssider on a pc is a better utility. Locate all the wireless around you and what channels are used. I would say you are being swamped by higher intensity wireless than the TC can produce.
    Go into the wireless setup and change over to manual settings.. set to N wireless.. and set to manual channels.
    In 2.4ghz try 1, 6, 11.. but pick whatever is the lowest usage from your survey of wireless usage.
    Also try and use 5ghz as it has less interference. When you are bridged, the IP address is derived from the modem and not the TC so the issue can be there.. try setting dhcp to fixed for the MAC address of each wireless. and set the lease to very short.. 30min or even try 10min.
    There certainly are issues with Lion networking.. exactly what is hard to figure out.. but you can also try the TC with earlier firmware.. go back to 7.5.2 which was much more reliable than later ones.
    You can also try it in router mode putting the modem in bridge if the ISP supports PPPoE.. or use DMZ with the modem still doing routing. The TC will kick up a double NAT error but just select to ignore it. Sometimes it will work better in router mode.

  • Rebuilding aMacBook 1.83 GHz Intel Core Duo, hard drive failure so rebuilding system.  Aircard will not stop self-assigning IP address.  Any ideas how to resolve successfully?

    Had hard drive failure on MacBook 1.83 GHz Intel Core Duo, so had to rebuild the OS on new drive. Was on Lion 10.7.5 prior to failure, but had to reinstall Snow Leopard 10.6.3 since that was most recent OS on media I had.  After finally getting ethernet connection to router working, was able to get to internet and download / upgrade to 10.6.8.  I assume I can probably buy the upgrade to Mountain Lion 10.8 from there.
    Problem is this, Airport will not stop self-assigning IP address for my wireless connection, and unless I can get wireless back on this laptop, doesn't make a lot of sense to continue the rebuild and reinstall of all the software that was on it prior to HD failure.  Only way to my home network and router is ethernet now.  Everything else on my network (Apple MacBook Pro laptops, iPhones, desktops, and non-Apple printers and laptops) is hooking up to router wirelessly fine.
    Any ideas how to resolve successfully so that the airport will stop self-assigning and allow the router to assign the IP address?

    When see the beachball cursor, note the exact time: hour, minute, second.  
    These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.
    Launch the Console application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad and start typing the name.
    The title of the Console window should be All Messages. If it isn't, select
              SYSTEM LOG QUERIES ▹ All Messages
    from the log list on the left. If you don't see that list, select
              View ▹ Show Log List
    from the menu bar at the top of the screen.
    Each message in the log begins with the date and time when it was entered. Scroll back to the time you noted above.
    Select the messages entered from then until the end of the episode, or until they start to repeat, whichever comes first.
    Copy the messages to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
    The log contains a vast amount of information, almost all of it useless for solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.
    Please don't indiscriminately dump thousands of lines from the log into this discussion.
    Please don't post screenshots of log messages—post the text.
    Some private information, such as your name, may appear in the log. Anonymize before posting.

  • Self-assigned ip address starting with 169

    Trying to connect to free wifi in paris but my gf's computer won't connect, instead it gives me a self-assigned IP address starting with 169, any thoughts on how I fix this?
    Free wifi is a very big network in Paris, you only need a username and a password to sign in and can get connection almost everywhere in the city.
    It works on my computer, but not on my gf's. It also works on my iphone, it's only her computer that doesn't connect. It worked on her computer aswell until yesterday evening.

    Self-assigned IP Addresses 169.254.xxx.yyy are the ones your computer gives itself so that it has a name while it broadcasts a request for a better IP address. A self-assigned IP address usually persists for only a second until your Router responds with a good address. Finding yourself still stuck with a self-assigned address means you cannot reach the Router.
    You should look for really fundamental problems. Is the connection method you prefer the top one in the System Preferences > Networks box? Are you too far away for a good connection? If all seems OK, use the  ( Assist Me ) button in that panel and follow the Setup Assistent [not the Network diagnostics] branch to establish a good connection.

  • Self Assigned IP - Fixed, but help still needed, please

    I'll add a bit of a back story first which I hope will help people understand my issue, but also hopefully lead people with a self-assigned IP issue to a fix (link is within the post)
    I’m on on an iMac 20″ Mid 2007. I recently updated to OSX Lion after having wifi connection issues in Leopard. I used to randomly get kicked off my wifi and given a self assigned IP. With Leopard, the issue was fixed by applying a manual IP, router address etc and restarting. The issue would return months later, but I got over it after a few tantrums.
    Then as soon as I updated to Snow Leopard, I instantly had no internet access and I could only upgrade to Lion if I downloaded system updates. So after a few hours of searching, I toggled my internet sharing ‘on & off’ and that was enough for that fix.
    But then I upgraded to Lion and again, no internet. And nothing worked for me at all, every fix on the internet I tried failed. If my airport ever managed to connect to my router I would get a self assigned IP. Or it would say it was connected but there was no internet. So I hunted for hours and eventually found this:
    Now, here is a fix for anyone who is having the same issue. I hope it works for you!
    http://www.davidpierron.com/index.php/archives/2009/04/13/289/
    This did work for me. The fix is to flush your ipfw through terminal, and it worked for me instantly.
    However, I now have another issue that I really hope people can help me with. It's not as annoying as the above, but my god it's still very annoying!
    Here are some bullets to show the tedious routine I have to go through in order to connect to the internet via my airport.
    • I turn on my mac and my it tries to connect to my router automatically. But after a minute of trying, it says it can’t connect.
    • I select my router manually from the list and have to enter my password manually, even though it is already saved in my Keychain.
    • It then connects and says, ‘Connected but no internet’, so I leave it for two minutes and throw things around the room.
    • After those 2 minutes it connects to the internet. But no, I can’t browse the web as the browser says 'DNS look up failure'.
    • So I open terminal, enter 'sudo ipfw flush' to flush my ipfw and BINGO, I’m online 5 minutes after logging on to my machine.
    The router I am using was only issued to me 8 months ago by my new ISP here in the UK, it connects via WEP and has always been stable for every other device I have connected to it. But I am going to ring up my ISP and see if there is a new router I can get.
    If anyone - ESPECIALLY APPLE who seem to be shying away from admitting there has ever been an airport wifi issue - has any information to advise me, then please let me know.
    Also if you are having a Self Assigned IP address issue and that fix above works, give the man some credit on his blog, and if you know him, give him a kiss from me!
    Thanks

    Update:
    I spoke to my ISP to see if they had any newer routers and if they did WPA now.
    I have a new router on its way and they have updated my router to do WPA!
    The result?
    I now connect to my router automatically after a restart. No issue there.
    However,
    It still can't find the internet when it first connects.
    I still have to wait 2 minutes for it to find the net.
    I still have DNS issues once connected
    I still have to flush ipfw before it works correctly.

  • Self-assigned IP problem - still no resolution!?

    I have a Macbook which is about two and a half years old. I have never experienced any real problems with it, especially regarding connections. I have been connected to my home wireless network (BT homehub) ever since I got the laptop with no issues. It has always picked it up the second I turn it on and never drops.
    One day, I was traveling back home on the train and I tried my luck at connecting to the trains free wireless, but it didn't work. When I arrived hom, my computer would not connect to our wireless. Somehow when trying to connect to the trains wireless, my preferences must have changed or something meaning that my airport now has a "Self-assigned IP address and may not be able to connect to the internet".
    I went through all of the diagnostics and assistant things, but just kept going round incircles. I re-booted, I tried everything I found online on tis community and others but nothing works.
    I have renewed the DHCP Lease - No luck. It says "Configure IPv4: Using DHCP", so it's not that.I tried connecting via Ethernet, but I have the same issue with the Ethernet connection via Airport.
    It is not my Router or internet connection because others are using it in the household with no issue. I went a week or so not knowing what to do. Then I had to go back to Uni for a while - there I was able to connect to the internet using the Ethernet cable they provide (we don't have wireless so I couldn't test that) and that was fine, working as smoothly as it has done for the two years I have had the laptop.
    I am now home, and still cannot connect to the internet. Can somebody please give me any other options/advice? I am at a loss, and desperately need to access the Internet for work!

    I was having the same problem with the wifi not connecting to our home network on only one of our Macbooks.  It kept giving itself a self assigned ip address.  Everything else would connect fine to the home network and the computer with the problem connected fine to every other network aside from our home wifi.  After reading this thread and trying everything on it, this is what finally fixed it:  I didn't have anything under the 802.1x tab either.  So I:
    Turned the Airport off and completely deleted the Airport in network preferences.
    Then I went to keychain access and deleted EVERY wifi network password saved under both Login and System. 
    I turned the computer off and removed the battery and did the SMC reset by holding down the power button for 5 seconds. 
    When I restarted the computer, I reset the PRAM by holding down OPTION, COMMAND, P, and R at the same time RIGHT AFTER I pushed the power button to turn it on and before the grey screen appeared. 
    It reset and when the computer was back on, I added the airport again and joined my home WEP wfi network.  It worked perfectly!  Now I don't know if all of these steps are required to fix the problem but this is what worked for me.  The Macbook with the problem was a black Macbook running 10.6.8.  Good luck!

  • After reading hours on this forum still having self-assigned IP address

    I just posted this below on another thread but it kinda is in the wrong subforum. This really is a networking problem:
    I have spent about 3-4 hours today already (a Sunday after all) reading just about every thread I could find that mentions this problem (airport choosing a self-assigned IP address and thus not sharing the internet from ethernet connection with the iPhone) on this forum and elsewhere.
    Power circuit interruption didn't work
    rebooting, resetting, etc all not working
    password deletion not working
    moving it up or down not working
    It worked fine now for months. My set up is a dsl router that connects the internet via ethernet to my iMac and then Airport is supposed to share it via Wifi so my iPhone can use it. As I said, that worked just fine for months now.
    Yesterday I upgraded to snow leopard and am now on 10.6.4. It worked still fine yesterday!
    Then I shut the system down.
    This morning reboot and it just won't work anymore.
    Any suggestion mentioned anywhere in this forum which a non-specialist like me understands does not work on my setup. I don't know where to go next or who to even ask for help!
    It's so frustrating I obviously need this to work.
    Because my iPhone has Daylite touch and needs the server setting to work to connect properly and sync. Daylite only syncs via wifi. That's my work!
    Anymore ideas out there?
    Message was edited by: BettinaH

    Hi,
    thanks for offering help! Really appreciated.
    I'm not quite sure how that should help? I'm always a bit with resetting things. What can it potentially mess up that is working now? What settings will be affected? There is a list but I'm not sure if there are any current changes.
    And in the list it doesn't seem to be directly linked to any networking info.
    I've tried a save reboot now but while this is apparently a good idea in any event, it didn't help solve my problem. Still getting a self-assigned IP.
    I wonder if getting a new router might solve the problem? Mine is somewhat old. The weird thing is though that it did work for a short while before it stopped doing so. So this can't really be then, can it?
    Oh this is so frustrating. I must get my network running again.

  • Self-Assigned IP with my Ethernet

    I have been having problems while on the internet at school. I will be logged in and on the internet perfectly fine(the Ethernet says connected). Then around 15 minutes later I disconnect from the internet and it says "Self-Assigned IP", where it used to say connected. I can't get back onto the internet until i restart my computer. This gets annoying having to restart my computer about every 15 minutes just to get on the internet. Any answers? Also here is a copy of my ifconfig under the terminal settings while the Ethernet says "Self-Assigned IP".
    Last login: Wed Sep 10 23:47:08 on ttys000
    michael-dishers-macbook:~ Dish$ ifconfig
    lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
    inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
    inet 127.0.0.1 netmask 0xff000000
    inet6 ::1 prefixlen 128
    gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
    stf0: flags=0 mtu 1280
    en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
    inet6 fe80::217:f2ff:fedf:8c88%en0 prefixlen 64 scopeid 0x4
    inet 169.254.160.9 netmask 0xffff0000 broadcast 169.254.255.255
    ether 00:17:f2:df:8c:88
    media: autoselect (10baseT/UTP <half-duplex>) status: active
    supported media: autoselect 10baseT/UTP <half-duplex> 10baseT/UTP <full-duplex> 10baseT/UTP <full-duplex,hw-loopback> 10baseT/UTP <full-duplex,flow-control> 100baseTX <half-duplex> 100baseTX <full-duplex> 100baseTX <full-duplex,hw-loopback> 100baseTX <full-duplex,flow-control> 1000baseT <full-duplex> 1000baseT <full-duplex,hw-loopback> 1000baseT <full-duplex,flow-control> none
    fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 2030
    lladdr 00:1b:63:ff:fe:65:23:16
    media: autoselect <full-duplex> status: inactive
    supported media: autoselect <full-duplex>
    en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
    ether 00:1b:63:09:13:bd
    media: autoselect (<unknown type>) status: inactive
    supported media: autoselect
    michael-dishers-macbook:~ Dish$

    Hmmm...
    Ok, here's a couple of questions for you.
    1) Is this in a dorm room or in a classroom?
    2) Does this happen no matter where you plug in, or is it in a specific room?
    Troubleshooting problems like this can be a pain, but you have to eliminate possible causes no matter how unlikely they seem to be.
    A couple simple things to try:
    Try another ethernet cable. If the cable you are using has a intermittent short or break, it could cause problems.
    Try connecting to another ethernet connection. (That's why I asked if it was in a specific location.) You could just be plugging into a problematic jack.
    Try those first, then if it still has the problem we'll go from there. You may want to check with your school's IT department and see if anyone else is reporting similar problems. Maybe they can lend a hand.

  • No Internet with Lion. Stay away until self-assigned IP addresses are fixed!

    I have a TimeCapsule (802.11n 3rd gen) and four Macs. Until two months ago all was well and everyone could connect.
    Two months ago the Apple apps on the MacBook Pro stopped connecting to the Internet on the TimeCapsule network (Mail and Safari would not connect, Firefox was fine). The MacBook Pro connects on all other networks. I travel a fair amount and the computer has connected fine at all networks tried. I have sinced updated to Lion (10.7.2) and the problem is the same. The error in System Preferences indicates that the computer has a self-assigned IP address and will not be able to access the Internet - but Firefox works, so we know that is not  entirely the case.
    Last week our desktop stopped being able to access the Internet using the TimeCapsule network. Problems the same as the MacBook but the desktop Mac is using Snow Leopard.
    Our older laptop is using an earlier version of OSX and all is well. Out antique Mac laptop is also working well.
    We also have a Verizon MiFi and all machines can access the Internet on that.
    I have tried every "fix" I can find on the boards and through Google. Nothing works. From the looks of the boards, there are thousands of users with this problem and no answer from Apple.
    I was much better off before I switched to Lion. In those days, I just used Firefox and looked at my iPad when I needed mail (and waited to sync at the office). But with Lion comes iCloud and an increased reliance on the App store, making  internet connectivity through Apple apps is a must. Can someone from Apple help us fix this? Does anyone have any suggestions?

    That is what I told Comcast, but they said since my
    computer works "fine" in Safe-Boot,
    Classic, and the other PC—then they
    conclude there's no problem with their hardware and
    that its not their problem; that its Apple's issue.
    And nope I'm not connected wirelessly, it's through a
    basic ethernet cable.
    I don't know who to blame for this. Five years ago, this never happened, but it is common now. It affects both Macs and PCs, but as usual, people like Comcast will make an effort to fix a PC but throw up their hands with a Mac. Go figure.
    So, what speed, duplex and adapter type numbers
    should I put in?
    I don't know for sure. Start with duplex. If it current says "auto", change it to "full". If that doesn't work, or if it already was "full", change it to "half". If still nothing, switch it back to "auto" and fiddle with all the 10/100 speed combinations. You may have to go back and try different duplex and speed combinations! It sounds harder than it is. Try changing the duplex and adapter settings from "auto" before changing the speed. I'm am on my work Dell right now (which needed the same fix BTW), so I can't give you very good step-by-step instructions.
    The thing that troubles me is why is it that the
    internet works fine in Safe-Boot and Classic, but not
    Normal OS X mode?
    No clue about that.

Maybe you are looking for

  • Problem viewing video-content folders in Adobe Bridge

    Hi there. I have problem browsing folders inside Adobe Bridge CS6. When I get into a folder that contains files that are not just images, Adobe Bridge would not responding and would have to be closed. With the folders contains only images I have no f

  • G_G_IDOC_REC_ZZINCOT function module not found in ECC 5.0

    i am getting the dump. the fuction module is not presend in ECC 5.0 Runtime Errors         CALL_FUNCTION_NOT_FOUND                                                      Exceptn                CX_SY_DYN_CALL_ILLEGAL_FUNC                                

  • Acrobat 7.0.9 Standard

    Greetings, After a reinstall ( 5.0.5 and then 7.0 standard upgrade ) on a new hard drive, since updating to 7.0.9, I keep getting the message ' You most reboot before you can get another update ' I have done several cold and warm reboots since and st

  • Can I do a firmware update over ssh

    I am trying to flash the ROM on my video card in order to get it to work. I have the binary file, and of course the instructions say click on it (of course I have no screen yet). Is there a way to run a binary file at the command line? (it's not an e

  • Mixed PC/Mac environment with Mac 10.6 server sharing issue

    In this mixed environment, I can't figure out how to get new documents created on the Macs (saved onto a shared folder on the server) to be set as read/write for the PC user. I'm not a Mac system admin, just to start with, but I do use Macs all the t