Jump to content
Sign in to follow this  
mehron

-1028 error with no ping on a client

Recommended Posts

One of my clients uses all of the same preferences and setting as the rest of us, however is a -1028 error for Retrospect.

 

I have tried to ping the client from the server and realized that it got nothing as well.

 

The client is a OS X 10.3 iBook over ethernet with the 5.0540 version.

 

Why would this client be different than the rest?

 

Maybe I should run a permissions repair?

Share this post


Link to post
Share on other sites

That you cannot ping the machine in question suggests that this has nothing to do with Retrospect, but is instead a general networking issue.

 

- Does the iBook have its firewall settings clamped down?

Check the Firewall settings in the Sharing preference pane.

- Is the iBook be running any third party firewall configuration programs?

- Can the iBook ping the machine running Retrospect?

Share this post


Link to post
Share on other sites

The ibook can ping back to the server machine.

 

The Firewall is on, but port 497 is open. I've attmpted access with the Firewal off as well, but no luck.

 

No third party firewall.

 

However, I did notice that the machine is pulling the ip 10.0.0.10. Is there something about that which could be the problem? The router is 10.0.0.1.

Share this post


Link to post
Share on other sites

> I did notice that the machine is pulling the ip 10.0.0.10.

 

Which machine?

 

Is this a different subnet from the _other_ machine in this arrangement?

 

 

Dave

Share this post


Link to post
Share on other sites

Hi

 

To clarify: You can only ping in one direction?

 

OSX has a network utility that includes a portscan feature. It will let you scan another computer to see if port 497 is open or not. Thats a good place to start.

 

Nate

Share this post


Link to post
Share on other sites

What is strange is that you think this is a Retrospect issue.

 

It is not.

 

If the /sbin/ping utility that ships with OS X can't communicate with the remote machine then it would follow that other networking utilities would be unable to communicate with it too.

 

There's something wacky on one of these machine, most likely the iBook. But when you can figure out why you can't ping, you'll have solved why Retrospect can't connect.

 

 

Dave

Share this post


Link to post
Share on other sites

I finally have solved this issue.

 

Among other things, this had to do with reinstalling a client without removing the password from the previous client. Therefore the new client had not been logged in.

 

Thanks for the help and suggestions.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×