Mac Pro App Store login problem

Question

Level 1

10 points

Mac Pro App Store login problem

Hi,

I have early 2008 Mac Pro, and it has problem when login to App Store - it gives error message 'Your device or computer could not be verified. Contact support for assistance.'

Otherwise internet connection is working, iTunes store is working - I can log into that, but not into App store.

Internet is working through third party - Sonnet - ethernet card, native ethernet ports are dead presumably, they will not show up under Network. Internet is working fine.

I have deleted the 'Networkinterfaces.plist' a numerous times, no success.

Any ideas, please!

I've thought myself that perhaps Apple uses native ethernet ports to identify the App store clients, when client has a computer that has ethernet ports. So when they are "dead", how can i go around that? Changeing Mac address?

BR

Indrek

Mac Pro, OS X Mavericks (10.9.5)

Posted on May 28, 2015 1:41 AM

Reply

Answer 1

lllaass

Level 10

210,411 points

May 28, 2015 2:12 AM in response to minaindrek

Contact iTunes support as the message says

Apple - Support - iTunes - Contact Us

Reply

Answer 2

minaindrek Author

Level 1

10 points

May 28, 2015 2:18 AM in response to lllaass

Hi,

contacting iTunes support wouldn't help me. I've been there, and as I said my iTunes account is fine and working. It is App store I cant get in to.

BR

Reply

Answer 3

Linc Davis

Level 10

209,547 points

May 28, 2015 8:31 AM in response to minaindrek

Back up all data before proceeding.

Step 1

Triple-click anywhere in the line below on this page to select it:

/Library/Preferences/SystemConfiguration/NetworkInterfaces.plist

Right-click or control-click the line and select

Services ▹ Reveal in Finder (or just Reveal)

from the contextual menu.* A folder should open with an item selected. Move the selected item to the Trash. You may be prompted for your administrator login password. Restart the computer and test.

If there's no change, repeat with this file:

/Library/Preferences/SystemConfiguration/com.apple.network.eapolclient.configuration.plist

*If you don't see the contextual menu item, copy the selected text to the Clipboard by pressing the key combination command-C. In the Finder, select

Go ▹ Go to Folder...

from the menu bar and paste into the box that opens by pressing command-V. You won't see what you pasted because a line break is included. Press return.

Log out, log back in, and test. If there's no improvement, continue.

Step 2

Reset your computer’s PRAM.

Reply

Answer 4

minaindrek Author

Level 1

10 points

May 29, 2015 12:15 AM in response to Linc Davis

Hi,

I tried all that but no luck - "Your device could not be verified...".

One thing that I tried yesterday - I installed OSX 10.6 Snow Leopard, and applied updates one by one. After 10.6.6 update, when App store was introduced, it was working! I was able to log into App store. It was working also after update 10.6.7.

But update 10.6.8 changed something and I was not able to login - "Your device could not be verified..."

If we could know what was changed, then we might find a key how to bypass this error...

BR

Indrek

Reply

Answer 5

lllaass

Level 10

210,411 points

May 29, 2015 1:29 AM in response to minaindrek

Try installing the 10.6.8 combo update and the suppllemental update

(Note: there's a separate Snow Leopard 10.6.8 Supplemental Update:http://support.apple.com/kb/HT1429 that is not included in the 10.6.8 "combo".)

Snow Leopard 10.6.8: http://support.apple.com/kb/DL1399
from
http://pondini.org/OSX/Combo.html

Reply

Answer 6

Linc Davis

Level 10

209,547 points

May 29, 2015 5:58 AM in response to minaindrek

Have you ever been able to use the App Store in Mavericks with the Sonnet card installed?

Reply

Answer 7

minaindrek Author

Level 1

10 points

May 29, 2015 6:32 AM in response to Linc Davis

No, I have not. I bought this Mac Pro with ethernet cards dead already, and it never worked in Maverics (or Mountain Lion or Yosemite). Yesterday with OSX 10.6.6 it was first time to log in to App store with this mac. And there was no difference in using Sonnet PCIe ethernet card or Airport wifi.

Unfortunately 10.6 is basically obsolete.

I can try this supplemental update but my point was elsewhere - it is working in OSX 10.6.6 and not working in 10.9.5. Maverics is still my main os.

BR

Reply

Answer 8

Linc Davis

Level 10

209,547 points

May 29, 2015 6:38 AM in response to minaindrek

What I think is happening is that, starting with 10.6.8, Apple has been using the MAC address of the client to block attempts to run OS X on non-Apple hardware. Since you don't have an Apple MAC address, you're blocked. The only hope is to change the MAC of the card to spoof an Apple MAC. Some cards would allow that, but I don't know whether yours does. You would use the MAC of one of the built-in interfaces.

Reply

Answer 9

minaindrek Author

Level 1

10 points

May 29, 2015 6:38 AM in response to Linc Davis

I'm sorry to say that I have already tried that and it didn't work. Booted into safe mode, logged into test account that was newly made, and the problem was still there.

Anyway, thanks for helping me.

BR

Indrek

Reply

Answer 10

Linc Davis

Level 10

209,547 points

May 29, 2015 6:38 AM in response to minaindrek

I revised my comment.

Reply

Answer 11

minaindrek Author

Level 1

10 points

May 29, 2015 6:50 AM in response to Linc Davis

Ok, I thought something like that but for me it is unclear why it is not working with Airport wifi then. It is 100% Apple and onboard wifi. Or at least should be 100%, maybe it is changed.

I have tried to change the MAC address but I'm not sure if it changes. It doesn't show under "Network", even if I see new MAC address in terminal.

BR

Reply

Answer 12

Linc Davis

Level 10

209,547 points

May 29, 2015 6:59 AM in response to minaindrek

Remove the Sonnet card and try Wi-Fi. You might have to delete the plist again.

Reply

Answer 13

minaindrek Author

Level 1

10 points

Jun 3, 2015 1:49 AM in response to Linc Davis

Removed the Sonnet ethernet card, deleted .plist-file but problem is still there. Seems that, those who said that replacing motherboard is only solution, are right... Kinda weird - computer is otherwise totally usable and working, could probably work years for me...

But will give up now, thanks for helping.

Reply