Jump to content

tlemons

Members
  • Content count

    57
  • Joined

  • Last visited

Community Reputation

0 Neutral

About tlemons

  • Rank
    Frequent Poster
  1. tlemons

    Disable Retrospect Monitor

    Hi Robin Thanks for the reply! In Retrospect 'Startup preferences', I have selected both: - Enable Retrospect Launcher service - Automatically launch Retrospect So I don't see how I can manually launch Retrospect before scheduled bacukps, UNLESS I disable use of these services. What say you? Thanks tl
  2. Hi I have Roxio Retrospect for Windows V7.7. When Retrospect start automatically (when I boot my computer and log in), the Retrospect Monitor utility starts, instead of the main Retrospect window. Since the Retrospect Monitor gives almost no useful information, I don't ever want to use it. How can I disable it from running? Thanks! tl
  3. Hi I often (several times a month) see the dreaded -203 error when writing to my DVD drive. I've replaced the drive with a different manufacturer, tried media from different manufacturers, and still see the error. I'm just accepting it as a fact of life with DVD drives. But I want to get better about dealing with the error, which I see when the verify phase of the backup occurs. When I see the error, I know that the backup is invalid. Problem is, I'm not sure what to do about it. Should I 'forget' the snapshot? I _think_ I'd want to 'forget' the session, but I don't see a way to do this. What I want to do is to repeat the backup that, during verify, was found to be invalid. What's the correct way to do this? I searched the knowledgebase for guidance on 203, but didn't see this covered. My apologies if I missed this. Thanks! tl
  4. Hi I have a customer who has been using an eMachines system for several years, and now wants to move the software environment that she has on the eMachines system over to a new Dell system. Needless to say, the only thing they have in common is Windows XP SP2; all of the installed applications, as well as the hardware, are different. If I've taken backups of the eMachines system, can I use a Retrospect restore to 'move' EVERYTHING (files, applications, Registry information, everything) to the new Dell? I think the answer is 'yes', but I want to make sure before I start. I read the Retrospect 7 documentation, and noticed that one restore option is the one documented here: "Restore an entire volume, selects and restores all files and folders from the source Snapshot to the destination, deleting all other contents. Restores registry and System State information from the Snapshot (if available)." Does this restore mode really delete all of the existing files on a system, and all of its Registry information, and then restore the needed files and the needed Registry information? Is the Registry restore handled by the Retrospect Helper Service? I did a 'all' restore and watched it work. Thanks! tl
  5. tlemons

    -530, yet again

    Hi Nate Thanks for these suggestions! >Other clients log in correctly right? Right. I added a client on a Windows 2003 64-bit system with no issues. >Can you enable the other interface on the client, disable the current interface and see how that goes? I tried that, and was able to add the client to the server. Hm. So, I looked at the differences between the two network adapters on the client system. I opened the Network Connections window on the client. I noticed that the primary network adapter (which, when used, wasn't allowing me to add the client) was in a state of 'Disabled, shared'. Hm. Shared by what, I wondered. I noticed in Network Connections -> Local Area Connection -> Properties -> Advanced -> Internet Connection Sharing, the option "Allow other network users to connect through this computer's Internet connection" was checked, as was the "Allow other users to control or disable the shared Internet Connection". In Settings, I noticed two entries: Retrospect Client 255.255.255.255 497 497 TCP Retrospect Client (UDP) 255.255.255.255 497 497 UDP When I unchecked the "Allow other network users to connect through this computer's Internet connection" option and tried to add the client on the server, voila!, it worked! So, maybe there is something wrong with those entries in the Settings section? At any rate, just disabling that feature allows Retrospect to work. This might be worthy of a Knowledge Base article, me thinks. Thanks again, as always, for the help, Nate! tl
  6. tlemons

    -530, yet again

    Ni Nate Thanks for the suggestion, but even with starting the Retrospect client with 'retroclient /ip nn.nn.nn.nn', I still have the same problem. Other thoughts? Thanks! tl
  7. tlemons

    -530, yet again

    Thanks, Nate. Here is an Ethereal trace (sorry for the lines of detail, but wanted to provide them in case they are needed. 192.168.11.116 is the Retrospect Server; 192.168.11.99 is the Retrospect client on Windows XP SP2. It's important to note that I ran this ON THE RETROSPECT CLIENT, because I can see all of the dialogue we would expect: - UDP broadcast from the server to port 497 - UDP response from the client from port 497 - TCP packet from the server to the client (repeated three times) BUT no TCP response from the client to the server Since the client sees all of this traffic, including the incoming UDP and TCP packets, how can a firewall be causing the client to, apparently, NOT send the TCP response? Again, I've turned the Windows firewall off. Thanks! tl No. Time Source Destination Protocol Info No. Time Source Destination Protocol Info 176 19.165407 192.168.11.116 192.168.11.255 UDP Source port: 1602 Destination port: 497 Frame 176 (238 bytes on wire, 238 bytes captured) Ethernet II, Src: 192.168.11.116 (00:0f:1f:6f:ad:21), Dst: Broadcast (ff:ff:ff:ff:ff:ff) Internet Protocol, Src: 192.168.11.116 (192.168.11.116), Dst: 192.168.11.255 (192.168.11.255) User Datagram Protocol, Src Port: 1602 (1602), Dst Port: 497 (497) Source port: 1602 (1602) Destination port: 497 (497) Length: 204 Checksum: 0xc23f [correct] Data (196 bytes) 0000 00 01 00 01 f0 f0 f0 ff 9f bd 45 0f 00 00 00 00 ..........E..... 0010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0060 02 00 06 43 c0 a8 0b 74 00 00 00 00 00 00 00 00 ...C...t........ 0070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00c0 00 00 00 00 .... No. Time Source Destination Protocol Info 179 19.165618 192.168.11.99 192.168.11.116 UDP Source port: 497 Destination port: 1603 Frame 179 (238 bytes on wire, 238 bytes captured) Ethernet II, Src: 192.168.11.99 (00:0b:db:e2:93:88), Dst: 192.168.11.116 (00:0f:1f:6f:ad:21) Internet Protocol, Src: 192.168.11.99 (192.168.11.99), Dst: 192.168.11.116 (192.168.11.116) User Datagram Protocol, Src Port: 497 (497), Dst Port: 1603 (1603) Source port: 497 (497) Destination port: 1603 (1603) Length: 204 Checksum: 0xcb87 [correct] Data (196 bytes) 0000 00 01 00 01 f0 f0 f0 fe 00 00 00 29 6e 77 63 6c ...........)nwcl 0010 69 65 6e 74 31 00 00 00 00 00 00 00 00 00 00 00 ient1........... 0020 00 00 00 00 00 00 00 00 00 00 00 00 37 34 35 37 ............7457 0030 63 63 38 39 35 36 64 64 30 37 61 61 00 00 00 00 cc8956dd07aa.... 0040 00 00 00 00 00 00 00 00 00 00 00 00 00 02 01 f1 ................ 0050 c0 a8 0b 63 00 00 00 00 00 00 00 00 00 00 00 00 ...c............ 0060 02 00 06 43 c0 a8 0b 74 00 00 00 00 00 00 00 00 ...C...t........ 0070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00c0 00 00 00 00 .... No. Time Source Destination Protocol Info 199 21.165624 192.168.11.116 192.168.11.255 UDP Source port: 1602 Destination port: 497 Frame 199 (238 bytes on wire, 238 bytes captured) Ethernet II, Src: 192.168.11.116 (00:0f:1f:6f:ad:21), Dst: Broadcast (ff:ff:ff:ff:ff:ff) Internet Protocol, Src: 192.168.11.116 (192.168.11.116), Dst: 192.168.11.255 (192.168.11.255) User Datagram Protocol, Src Port: 1602 (1602), Dst Port: 497 (497) Source port: 1602 (1602) Destination port: 497 (497) Length: 204 Checksum: 0xc23e [correct] Data (196 bytes) 0000 00 01 00 01 f0 f0 f0 ff 9f bd 45 0f 00 00 00 00 ..........E..... 0010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0060 02 00 06 43 c0 a8 0b 74 00 00 00 00 00 00 00 00 ...C...t........ 0070 00 00 00 00 00 01 00 00 00 00 00 00 00 00 00 00 ................ 0080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00c0 00 00 00 00 .... No. Time Source Destination Protocol Info 221 23.165815 192.168.11.116 192.168.11.255 UDP Source port: 1602 Destination port: 497 Frame 221 (238 bytes on wire, 238 bytes captured) Ethernet II, Src: 192.168.11.116 (00:0f:1f:6f:ad:21), Dst: Broadcast (ff:ff:ff:ff:ff:ff) Internet Protocol, Src: 192.168.11.116 (192.168.11.116), Dst: 192.168.11.255 (192.168.11.255) User Datagram Protocol, Src Port: 1602 (1602), Dst Port: 497 (497) Source port: 1602 (1602) Destination port: 497 (497) Length: 204 Checksum: 0xc23d [correct] Data (196 bytes) 0000 00 01 00 01 f0 f0 f0 ff 9f bd 45 0f 00 00 00 00 ..........E..... 0010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0060 02 00 06 43 c0 a8 0b 74 00 00 00 00 00 00 00 00 ...C...t........ 0070 00 00 00 00 00 02 00 00 00 00 00 00 00 00 00 00 ................ 0080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00c0 00 00 00 00 .... No. Time Source Destination Protocol Info 225 23.973511 192.168.11.116 192.168.11.99 TCP 1604 > 497 [sYN] Seq=0 Ack=0 Win=65535 Len=0 MSS=1460 Frame 225 (62 bytes on wire, 62 bytes captured) Ethernet II, Src: 192.168.11.116 (00:0f:1f:6f:ad:21), Dst: 192.168.11.99 (00:0b:db:e2:93:88) Internet Protocol, Src: 192.168.11.116 (192.168.11.116), Dst: 192.168.11.99 (192.168.11.99) Transmission Control Protocol, Src Port: 1604 (1604), Dst Port: 497 (497), Seq: 0, Ack: 0, Len: 0 Source port: 1604 (1604) Destination port: 497 (497) Sequence number: 0 (relative sequence number) Header length: 28 bytes Flags: 0x0002 (SYN) Window size: 65535 Checksum: 0xfb79 [correct] Options: (8 bytes) No. Time Source Destination Protocol Info 237 25.166066 192.168.11.116 192.168.11.255 UDP Source port: 1602 Destination port: 497 Frame 237 (238 bytes on wire, 238 bytes captured) Ethernet II, Src: 192.168.11.116 (00:0f:1f:6f:ad:21), Dst: Broadcast (ff:ff:ff:ff:ff:ff) Internet Protocol, Src: 192.168.11.116 (192.168.11.116), Dst: 192.168.11.255 (192.168.11.255) User Datagram Protocol, Src Port: 1602 (1602), Dst Port: 497 (497) Source port: 1602 (1602) Destination port: 497 (497) Length: 204 Checksum: 0xc23c [correct] Data (196 bytes) 0000 00 01 00 01 f0 f0 f0 ff 9f bd 45 0f 00 00 00 00 ..........E..... 0010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0060 02 00 06 43 c0 a8 0b 74 00 00 00 00 00 00 00 00 ...C...t........ 0070 00 00 00 00 00 03 00 00 00 00 00 00 00 00 00 00 ................ 0080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00c0 00 00 00 00 .... No. Time Source Destination Protocol Info 252 27.166249 192.168.11.116 192.168.11.255 UDP Source port: 1602 Destination port: 497 Frame 252 (238 bytes on wire, 238 bytes captured) Ethernet II, Src: 192.168.11.116 (00:0f:1f:6f:ad:21), Dst: Broadcast (ff:ff:ff:ff:ff:ff) Internet Protocol, Src: 192.168.11.116 (192.168.11.116), Dst: 192.168.11.255 (192.168.11.255) User Datagram Protocol, Src Port: 1602 (1602), Dst Port: 497 (497) Source port: 1602 (1602) Destination port: 497 (497) Length: 204 Checksum: 0xc23b [correct] Data (196 bytes) 0000 00 01 00 01 f0 f0 f0 ff 9f bd 45 0f 00 00 00 00 ..........E..... 0010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0060 02 00 06 43 c0 a8 0b 74 00 00 00 00 00 00 00 00 ...C...t........ 0070 00 00 00 00 00 04 00 00 00 00 00 00 00 00 00 00 ................ 0080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00c0 00 00 00 00 .... No. Time Source Destination Protocol Info 253 27.228620 192.168.11.116 192.168.11.99 TCP 1604 > 497 [sYN] Seq=0 Ack=0 Win=65535 Len=0 MSS=1460 Frame 253 (62 bytes on wire, 62 bytes captured) Ethernet II, Src: 192.168.11.116 (00:0f:1f:6f:ad:21), Dst: 192.168.11.99 (00:0b:db:e2:93:88) Internet Protocol, Src: 192.168.11.116 (192.168.11.116), Dst: 192.168.11.99 (192.168.11.99) Transmission Control Protocol, Src Port: 1604 (1604), Dst Port: 497 (497), Seq: 0, Ack: 0, Len: 0 Source port: 1604 (1604) Destination port: 497 (497) Sequence number: 0 (relative sequence number) Header length: 28 bytes Flags: 0x0002 (SYN) Window size: 65535 Checksum: 0xfb79 [correct] Options: (8 bytes) No. Time Source Destination Protocol Info 276 29.166474 192.168.11.116 192.168.11.255 UDP Source port: 1602 Destination port: 497 Frame 276 (238 bytes on wire, 238 bytes captured) Ethernet II, Src: 192.168.11.116 (00:0f:1f:6f:ad:21), Dst: Broadcast (ff:ff:ff:ff:ff:ff) Internet Protocol, Src: 192.168.11.116 (192.168.11.116), Dst: 192.168.11.255 (192.168.11.255) User Datagram Protocol, Src Port: 1602 (1602), Dst Port: 497 (497) Source port: 1602 (1602) Destination port: 497 (497) Length: 204 Checksum: 0xc23a [correct] Data (196 bytes) 0000 00 01 00 01 f0 f0 f0 ff 9f bd 45 0f 00 00 00 00 ..........E..... 0010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0060 02 00 06 43 c0 a8 0b 74 00 00 00 00 00 00 00 00 ...C...t........ 0070 00 00 00 00 00 05 00 00 00 00 00 00 00 00 00 00 ................ 0080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00c0 00 00 00 00 .... No. Time Source Destination Protocol Info 314 33.791672 192.168.11.116 192.168.11.99 TCP 1604 > 497 [sYN] Seq=0 Ack=0 Win=65535 Len=0 MSS=1460 Frame 314 (62 bytes on wire, 62 bytes captured) Ethernet II, Src: 192.168.11.116 (00:0f:1f:6f:ad:21), Dst: 192.168.11.99 (00:0b:db:e2:93:88) Internet Protocol, Src: 192.168.11.116 (192.168.11.116), Dst: 192.168.11.99 (192.168.11.99) Transmission Control Protocol, Src Port: 1604 (1604), Dst Port: 497 (497), Seq: 0, Ack: 0, Len: 0 Source port: 1604 (1604) Destination port: 497 (497) Sequence number: 0 (relative sequence number) Header length: 28 bytes Flags: 0x0002 (SYN) Window size: 65535 Checksum: 0xfb79 [correct] Options: (8 bytes) No. Time Source Destination Protocol Info 381 41.260778 192.168.11.116 192.168.11.255 UDP Source port: 1602 Destination port: 497 Frame 381 (238 bytes on wire, 238 bytes captured) Ethernet II, Src: 192.168.11.116 (00:0f:1f:6f:ad:21), Dst: Broadcast (ff:ff:ff:ff:ff:ff) Internet Protocol, Src: 192.168.11.116 (192.168.11.116), Dst: 192.168.11.255 (192.168.11.255) User Datagram Protocol, Src Port: 1602 (1602), Dst Port: 497 (497) Source port: 1602 (1602) Destination port: 497 (497) Length: 204 Checksum: 0xc23f [correct] Data (196 bytes) 0000 00 01 00 01 f0 f0 f0 ff 9f bd 45 0f 00 00 00 00 ..........E..... 0010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0060 02 00 06 43 c0 a8 0b 74 00 00 00 00 00 00 00 00 ...C...t........ 0070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00c0 00 00 00 00 .... No. Time Source Destination Protocol Info 382 41.260904 192.168.11.99 192.168.11.116 UDP Source port: 497 Destination port: 1603 Frame 382 (238 bytes on wire, 238 bytes captured) Ethernet II, Src: 192.168.11.99 (00:0b:db:e2:93:88), Dst: 192.168.11.116 (00:0f:1f:6f:ad:21) Internet Protocol, Src: 192.168.11.99 (192.168.11.99), Dst: 192.168.11.116 (192.168.11.116) User Datagram Protocol, Src Port: 497 (497), Dst Port: 1603 (1603) Source port: 497 (497) Destination port: 1603 (1603) Length: 204 Checksum: 0xcb87 [correct] Data (196 bytes) 0000 00 01 00 01 f0 f0 f0 fe 00 00 00 29 6e 77 63 6c ...........)nwcl 0010 69 65 6e 74 31 00 00 00 00 00 00 00 00 00 00 00 ient1........... 0020 00 00 00 00 00 00 00 00 00 00 00 00 37 34 35 37 ............7457 0030 63 63 38 39 35 36 64 64 30 37 61 61 00 00 00 00 cc8956dd07aa.... 0040 00 00 00 00 00 00 00 00 00 00 00 00 00 02 01 f1 ................ 0050 c0 a8 0b 63 00 00 00 00 00 00 00 00 00 00 00 00 ...c............ 0060 02 00 06 43 c0 a8 0b 74 00 00 00 00 00 00 00 00 ...C...t........ 0070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00c0 00 00 00 00 .... No. Time Source Destination Protocol Info 403 43.260856 192.168.11.116 192.168.11.255 UDP Source port: 1602 Destination port: 497 Frame 403 (238 bytes on wire, 238 bytes captured) Ethernet II, Src: 192.168.11.116 (00:0f:1f:6f:ad:21), Dst: Broadcast (ff:ff:ff:ff:ff:ff) Internet Protocol, Src: 192.168.11.116 (192.168.11.116), Dst: 192.168.11.255 (192.168.11.255) User Datagram Protocol, Src Port: 1602 (1602), Dst Port: 497 (497) Source port: 1602 (1602) Destination port: 497 (497) Length: 204 Checksum: 0xc23e [correct] Data (196 bytes) 0000 00 01 00 01 f0 f0 f0 ff 9f bd 45 0f 00 00 00 00 ..........E..... 0010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0060 02 00 06 43 c0 a8 0b 74 00 00 00 00 00 00 00 00 ...C...t........ 0070 00 00 00 00 00 01 00 00 00 00 00 00 00 00 00 00 ................ 0080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00c0 00 00 00 00 .... No. Time Source Destination Protocol Info 419 45.260941 192.168.11.116 192.168.11.255 UDP Source port: 1602 Destination port: 497 Frame 419 (238 bytes on wire, 238 bytes captured) Ethernet II, Src: 192.168.11.116 (00:0f:1f:6f:ad:21), Dst: Broadcast (ff:ff:ff:ff:ff:ff) Internet Protocol, Src: 192.168.11.116 (192.168.11.116), Dst: 192.168.11.255 (192.168.11.255) User Datagram Protocol, Src Port: 1602 (1602), Dst Port: 497 (497) Source port: 1602 (1602) Destination port: 497 (497) Length: 204 Checksum: 0xc23d [correct] Data (196 bytes) 0000 00 01 00 01 f0 f0 f0 ff 9f bd 45 0f 00 00 00 00 ..........E..... 0010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0060 02 00 06 43 c0 a8 0b 74 00 00 00 00 00 00 00 00 ...C...t........ 0070 00 00 00 00 00 02 00 00 00 00 00 00 00 00 00 00 ................ 0080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00c0 00 00 00 00 .... No. Time Source Destination Protocol Info 440 47.261098 192.168.11.116 192.168.11.255 UDP Source port: 1602 Destination port: 497 Frame 440 (238 bytes on wire, 238 bytes captured) Ethernet II, Src: 192.168.11.116 (00:0f:1f:6f:ad:21), Dst: Broadcast (ff:ff:ff:ff:ff:ff) Internet Protocol, Src: 192.168.11.116 (192.168.11.116), Dst: 192.168.11.255 (192.168.11.255) User Datagram Protocol, Src Port: 1602 (1602), Dst Port: 497 (497) Source port: 1602 (1602) Destination port: 497 (497) Length: 204 Checksum: 0xc23c [correct] Data (196 bytes) 0000 00 01 00 01 f0 f0 f0 ff 9f bd 45 0f 00 00 00 00 ..........E..... 0010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0060 02 00 06 43 c0 a8 0b 74 00 00 00 00 00 00 00 00 ...C...t........ 0070 00 00 00 00 00 03 00 00 00 00 00 00 00 00 00 00 ................ 0080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00c0 00 00 00 00 .... No. Time Source Destination Protocol Info 457 49.261211 192.168.11.116 192.168.11.255 UDP Source port: 1602 Destination port: 497 Frame 457 (238 bytes on wire, 238 bytes captured) Ethernet II, Src: 192.168.11.116 (00:0f:1f:6f:ad:21), Dst: Broadcast (ff:ff:ff:ff:ff:ff) Internet Protocol, Src: 192.168.11.116 (192.168.11.116), Dst: 192.168.11.255 (192.168.11.255) User Datagram Protocol, Src Port: 1602 (1602), Dst Port: 497 (497) Source port: 1602 (1602) Destination port: 497 (497) Length: 204 Checksum: 0xc23b [correct] Data (196 bytes) 0000 00 01 00 01 f0 f0 f0 ff 9f bd 45 0f 00 00 00 00 ..........E..... 0010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0060 02 00 06 43 c0 a8 0b 74 00 00 00 00 00 00 00 00 ...C...t........ 0070 00 00 00 00 00 04 00 00 00 00 00 00 00 00 00 00 ................ 0080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00c0 00 00 00 00 .... No. Time Source Destination Protocol Info 473 51.261362 192.168.11.116 192.168.11.255 UDP Source port: 1602 Destination port: 497 Frame 473 (238 bytes on wire, 238 bytes captured) Ethernet II, Src: 192.168.11.116 (00:0f:1f:6f:ad:21), Dst: Broadcast (ff:ff:ff:ff:ff:ff) Internet Protocol, Src: 192.168.11.116 (192.168.11.116), Dst: 192.168.11.255 (192.168.11.255) User Datagram Protocol, Src Port: 1602 (1602), Dst Port: 497 (497) Source port: 1602 (1602) Destination port: 497 (497) Length: 204 Checksum: 0xc23a [correct] Data (196 bytes) 0000 00 01 00 01 f0 f0 f0 ff 9f bd 45 0f 00 00 00 00 ..........E..... 0010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0060 02 00 06 43 c0 a8 0b 74 00 00 00 00 00 00 00 00 ...C...t........ 0070 00 00 00 00 00 05 00 00 00 00 00 00 00 00 00 00 ................ 0080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00c0 00 00 00 00 ....
  8. Hi I have Retrospect 7.0.326 with 7.0.8.103 update running on a Windows 2000 SP4 system with two Ethernet adapters, of which only one is enabled. I have Retrospect client 7.0.107 running on a Windows XP SP2 system with two Ethernet adapters, of which only one is enabled. I've tried adding the client many times, but always get "Sorry, can't add backup client, error -530 (backup client not found). I can ping the backup client from the backup server, both by name and IP address. I can ping the backup server from the backup client, both by name and IP address. In Retrospect Configure -> Clients -> Add... -> Live Network, when I enter my subnet information in the 'Subnets' box, my client name does appear in the main window. This tells me that (1) the Retrospect server can see the Retrospect client, (2) the Retrospect server knows that that the Retrospect client is running Retrospect client software. But, when I click on the client name and click the Add button, I see a 'Client Connection' box appear with the word 'Opening'; then, that disappears, and I see a box with the words "Sorry, can't add backup client, error -530 (backup client not found. I've read many posts here on this topic. I've turned off the Windows firewall on the backup client. I've run retfwset.exe on the backup client. I've rebooted several times. I'm also running McAfee VirusScan Enterprise v8.0.0 on both the backup client and the backup server. I can't find any settings in it that would block the backup client and the backup server from talking. Since the backup server can see the backup software running in the backup client, what would cause it to be unable to complete the add client process? Is there some debugging I can do to gain more information? I can run Ethereal and capture packet traces, but I'm not sure how that would help. Thanks tl
  9. Heather Thanks VERY much for posting this! I had exactly the same problem after a Retrospect 6.5->7.0 upgrade. I deleted the Config70.* files (which were, like the Config65.* files, ~286KB in size). When I restarted Retrospect, I entered the license key. Then I did Tools -> Repair Catalog -> Update existing Catalog File -> More -> Open, and opened each of the catalog files for my existing Backup Sets created by Retrospect 6.5. After that, Retrospect 'remembered' all of my prior backup sets and sessions. Now, my backups are Normal backups. Thanks again! tl
  10. According to the Microsoft web site: Details Product: Windows Operating System ID: 51 Source: Cdrom Version: 5.2 Symbolic Name: IO_WARNING_PAGING_FAILURE Message: An error was detected on device %1 during a paging operation. Explanation An input/output (I/O) request to a memory-mapped file failed and the operation was retried. User Action No user action is required. Okay, so why would an I/O request to a memory-mapped file fail? Is this memory-mapped file a Retrospect file, or is it a file that Retrospect is trying to back up? I'm on my third try to back up some files on disk. Retrospect seems to back up some smaller file, including my Outlook .pst/ost files, but it seems to be stuck on backing up a large .mpg file. Thanks in advance for your advice. tl
  11. Hi Frequently, my Retrospect 7 backups will cause the following message to appear in the System Evnet Viewer log: Event Type: Warning Event Source: Cdrom Event Category: None Event ID: 51 Date: 7/4/2005 Time: 10:17:23 AM User: N/A Computer: JD Description: An error was detected on device \Device\CdRom1 during a paging operation. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 03 00 68 00 01 00 b8 00 ..h...¸. 0008: 00 00 00 00 33 00 04 80 ....3.. 0010: 2d 01 00 00 10 00 00 c0 -......À 0018: 00 00 00 00 00 00 00 00 ........ 0020: 00 00 00 00 00 00 00 00 ........ 0028: 8d 92 22 00 00 00 00 00 "..... 0030: ff ff ff ff 01 00 00 00 ÿÿÿÿ.... 0038: 40 00 00 c4 02 00 01 00 @..Ä.... 0040: 00 20 0a 12 48 02 00 40 . ..H..@ 0048: 00 00 00 00 0a 00 00 00 ........ 0050: 00 00 00 00 a8 cf 6b 84 ....¨Ïk 0058: 00 00 00 00 c8 58 68 84 ....ÈXh 0060: 02 00 00 00 00 00 00 00 ........ 0068: 28 00 00 00 00 00 00 00 (....... 0070: 02 00 00 00 00 00 00 00 ........ 0078: 70 00 05 00 00 00 00 0a p....... 0080: 00 00 00 00 64 00 00 00 ....d... 0088: 00 00 00 00 00 00 00 00 ........ I don't see these errors generated frmo any other applicatio. I read through many posts to this forum, trying to find an answer. One poster noted that Retrospect does not provide its own device drivers for DVD drives, but uses what is present in the system. I looked at the driver stack for my DVD drive, and found drivers from four applications. I de-installed all applications, and was left with just Microsoft provided drivers. But the problem above continued. I've also read in this forum that Retrospect does things that other applicatinos don't. These are done, so I've read in the interest of making sure Retrospect 'does it right'. But, as I look at these errors occur, time after time, with non idea what they mean, on a device that other applications use without error, I'm not seeing the goodness. I've Google'd and searched the Microsoft web site, with no help on what might cause this error. Any thoughts? Thanks tl
  12. Sorry to nag; any thoughts on this? Thanks tl
  13. Retrospect for Windows v7 I've had a lot of problems writing to my output device (a DVD drive) lately, and so have 21 members of my current backup set. Most of those members have incomplete backup sessions written to them. I'd like to take these 21 DVDs of backups (complete and in-complete), and re-write only the complete backups onto new media. I think the Transfer Backup Set function is what I need to do this. Transfer Backup Sets would certainly make a copy of the backup set, but would it copy all of the incomplete backups as well? I would hope not, but wanted to make sure before I plunged in. Thanks! tl
  14. tlemons

    Trouble reading error -206

    Here's another thought: I'm trying to backup to my DVD drive ~100 files. Several of these files are very large .MPG files; one file is 5.3 GB. I've tried to backup these files several times. It seems to write one DVD, fill that DVD, request and get from me a second DVD media, and then I get the 'Trouble writing media' messages. Does Retrospect have a maximum size to a backup set writing on DVD media? Does Retrospect have a maximum size for a file being backed up? Thanks tl
  15. tlemons

    Trouble reading error -206

    Hi I'm now seeing: Trouble writing media error -102 (trouble communicating) every time I try to do a backup. I'm using the same Fujifilm DVD-R media that I've used successfully for many months. I'm using the same Retrospect V6.5 with the same Retrospect Driver Update, version 5.4.110 that I've used for some weeks now. It seems like, all of a sudden, in the last two days, my DVD drive has gone bad, and won't write correctly any more. Do these writeable DVD drives wear out? Should this be happening, after one year of almost daily use? Thanks tl
×