Jump to content

stevew

Members
  • Content count

    2
  • Joined

  • Last visited

Community Reputation

0 Neutral

About stevew

  • Rank
    Occasional Forum Poster
  1. stevew

    Retrospect can't "see" client

    I am having the same problem described here. I used Ethereal to look at the network traffic and found that I can see both the burst of multicast packets probing for clients AND a response from the client. Retrospect is on 10.1.1.101 and the client is on 10.1.1.13. Apparently the reply from the client is making it back to the computer but not to Retrospect. This is what I saw: No. Time Source Destination Protocol Info 1 0.000000 10.1.1.101 224.1.0.38 UDP Source port: 1089 Destination port: 497 2 0.109513 10.1.1.101 224.1.0.38 UDP Source port: 1089 Destination port: 497 3 0.218912 10.1.1.101 224.1.0.38 UDP Source port: 1089 Destination port: 497 4 0.219220 10.1.1.13 10.1.1.101 UDP Source port: 497 Destination port: 1090 5 0.328312 10.1.1.101 224.1.0.38 UDP Source port: 1089 Destination port: 497 6 0.437550 10.1.1.101 224.1.0.38 UDP Source port: 1089 Destination port: 497 Since people are having so much trouble with the multicast search for clients it would be really nice if we could enter the client information manually. It's not like we don't know where the clients are installed. Does anyone know where Retrospect keeps the client information? It would be great to be able to just enter it into the registry or a file.
  2. stevew

    clients, cant find

    I am having a similar problem. Here are my details: Retrospect 6.5.343 running on Windows XP Retrospect client 6.5 running on RedHat Linux 9.0 Attempting to add a client brings up a window: Live Network Clients by Piton Name Service using multicast... Searching for backup clients... It never finds any clients. Clicking "Test..." and entering the IP address of the client immediately shows "Found a backup client:" with the client information. Some more detail on the multicast search: The Ethereal LAN protocol analyzer shows that Retrospect is sending a burst of 5 requests to IP address 224.1.0.38 port 497 every 10 seconds. Now here's the really interesting part: In the middle of this burst (usually between the third and fourth packet) a response is received from the client! It is EXTREMELY frustrating that Retrospect can talk to the client just fine but the lack of a way to enter the client information manually combined with a broken multicast mechanism prevents me from using the client. Does anyone know how Retrospect stores the client information? It would be great if I could manually enter the client information into the registry or a file. Thanks, Steve
×