Well, then let's start from the beginning... How many IP addresses do you see using ?

Just 1, the correct one.

File does not exist for me either.

Well, probably the software can't determine the server's IP address, because your MSS and client are in different subnetworks, don't know... but let's try to trick it. Connect using RDP to your MSS and write down its MAC address, then on the client launch Terminal.app and run the following command:

This adds MAC address statically to the ARP cache, which might be then become available for the Control Center.
If this does not help, it is better to delete added static ARP using

Since my MediaSmart only stays up for part of a day before not allowing me to connect, I started the morning by power cycling the unit. (Prior to rebooting I can ping it, and telnet to ports like 3389 for RDP, but I can't connect to it via Mac or Windows via any of the tools, shares, or RDP). After rebooting I was able to successfully RDP in and mount shares but per ususal, Hitting apply on the Mac software does nothing but put that error in the console.

I checked my arp table and the correct IP and MAC address where in there for the MSS. I went ahead and did a delete and static add of the same info, no difference.

Thanks for the suggestion but no good.

BTW, I only run one subnet. My network is as follows, a Linksys/Cisco WRT54G-TM (T-Mobile @ Home Linksys Wireless Router with 4 10/100 ports). Off of that Router I have 3 different Linksys 10/100 switches that feed the various components on my network (Slingboxes, Dish Network Receiver, FreeBSD server, etc..) The MSS is plugged into an 8 port switch that is plugged into the WRT54G-TM.

I have tried running the MSS with a DHCP assigned address and a static address, it doesn't seem to make a difference.

Are the Mac client and MSS on the same switch? If no, try to plug them in. If this does not help, well, I'm out of ideas, sorry. But it seems to me that the reason is somewhere in the network configuration, maybe in hardware.

I won't have time to work on trying this until this weekend but I'll give it a shot. Thanks for all your suggestions.

Fuzzyuu, have you heard anything back from HP? Thinking about opening a case myself but I don't want to waste my time if they're not helpful.

I to am having the same trouble.

I have the known MAC error that others have reported. Enter the sever name and password press apply and get the following error logged as viewed with console

9/25/09 6:59:18 AM HP MediaSmart Server Control Center[28562] *** -[NSFCDictionary setObject:ForKey:]: Attempt to insert nil value (key:Sewrver Mac)

If I knew where to put the key I could manually put in the MAC of the server.

OS X 10.6.1 HP CP 2.5.0b.43

Have done all the things I could find others have done.. Plugged computer and server direct to the Router, Originally on same switch. Firewall is off on OSX. Someone suggested ip net mask error on server.

So far not luck

will keep everyone informed and looking for more to try.

I think it would be very helpful if everyone who has this problem would call HP. I spent a while on the phone last week with Froilan, and then this morning I talked with Joe.

Joe said that this was a new issue that has just recently shown up in the past week or so. They are raising the issue up to the developers for a fix.

Could somebody post a copy of this file for us? Maybe we could copy it to our system, and edit it to get this working.

FWIW, I've called HP twice this month about the issue. Both times they said it was a new issue for them. There are enough people having the issue that it should have been raised quite a while ago.

The fact that there still isn't a resolution is very disappointing.

I purchased an EX485 a few weeks ago and have been experiencing the same issue. I've been through all the suggestions here with the same lack of joy. This thread has been going since May which leads me to believe that HP is not going to fix this. I wish I had seen this thread before I gone through all the trouble to no avail. Fortunately I bought this at Costco - so back it goes.

Thanks to everyone that has worked on this and provided suggestions.

Tony

It seems to me that something happened with the lately shipped MSS, because number of complains increased remarkable and found solution, which previously helped, does not work anymore.

So the update from HP is that they know about the bug and are working on a fix. They also confirmed that the MSS 3.0 software will be coming to the 47x and 48x series.

Any estimate on a timeline for either?

I am going to finally call HP and report the issue as well, now that I tried everything I can think of to try and fix. I'm not sure if your comfortable sharing this or not, but if wanted to give me your service request number I can reference that when I call to hopefully save time and link the cases to show that this is affecting a lot of users.

Thanks

Rob