Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


x509 last won the day on December 11 2019

x509 had the most liked content!

Community Reputation

22 Excellent

About x509

  • Rank

Recent Profile Visitors

667 profile views
  1. rjafman, Can you post this script. Thanks.
  2. I can't offer you any suggestions, but I'd like to describe a problem that I had when I tried to create a recovery USB drive for my laptop. The Retrospect windows that control the creation of the recovery USB are simply too tall to fit within the WinPE environment. it has everything to do with the native display parameters of my laptop, which is a Lenovo T560. If anyone has any suggestions, I would appreciate them.
  3. Last night, clients suddenly were NOT being backed up. Had I changed any network settings? No. Had there been a Windows update? I don't think so, because I configure updates to be run manually. So I checked all the Windows networking settings. Everything looked good. I checked the clients via Windows networking. Yup, they were both there. So what is Retrospect's problem here? As an experiment, I tried to ADD a new client. Same error message. So the issue isn't on the client side. In desperation, did a search on the Retrospect Knowledge Base and found this article https://www.retrospect.com/au/support/kb/error_code_table#stq= backup client%3A network interface unavailable&stp=4 So I clicked on the Interfaces button on one of the clients. I was using the default of course, and the current IP address of the interface was correct. So I played around with the various settings for the Default Interface, but didn't actually save any changes. Holy tape drives, Batman. Now the clients are being backed up. x509
  4. This thread, plus some of the weird things Windows updates does to network settings, probably explains why there is such grief around Windows networking. Way back in the 1980s, I was a product manager for networking protocols and stacks. That was before TCP/IP took over the world. Aside from LAN protocols, I dealt with SNA and DECNet, also oddballs like Banyan Vines. Thinking back on those days, I can't imagine what i was thinking. When TCP/IP became the One Protocol To Rule Them All, and Microsoft aligned its LAN networking around TCP/IP, life was supposed to get better. I must have been smoking some strong stuff back then. I like the belt and braces approach above.
  5. Since I personally don't have scripting skills beyond Windows CMD files, and not very good even at that a fixed IP for all clients (as David suggests) is probably the best approach for me. Right now, I'm busy with covid projects from my wife for fixing up things around the house, but I will get into my router's IP assignments table soon enough. To reprise an earlier comment, networking is the weakest part of Windows 10, since there is no one screen or set of screens to control all the entire TCP/IP stack or all the processes that can affect networking. Add to that the ways that a Windows update can silently reset some settings, and I spend way too much time on this issue. Retrospect client discovery is only one relatively small aspect of the overall issue. In my humble home LAN, all Retrospect clients and the server are wireless. One less issue.
  6. x509

    Retrospect 17 and low-end users

    If there were improvements in the UI of the client, as well as its performance, then I would have a solid reason to upgrade now. Otherwise I'll wait until 17.1 or 17.5, whatever its called. Any idea of when that upgrade might be released?
  7. In the Norton firewall, I added a rule for Port 497, for both TCP and UDP. Didn't fix the problem. Neither Configure -> Devices method discovered the clients. To respond to your point above, the Norton firewall has a concept of "trusted" networks devices. But as you say, Windows is notorious for changing network status in multiple ways. Sometimes after updates, sometimes for no apparent reason. Networking is to me, the biggest single source of grief and unwanted maintenance work in Windows. Perhaps PC networking works much better in a domain with an Active Directory server, but home networking is a hot mess. It's much easier to throw in the towel and use Direct IP Addresses for clients.
  8. Please see next message. This forum doesn't have the same reply formatting flexibilty as others.
  9. Please see properly formatted reply below.
  10. David, Agree with your point about needing an IP address plan for just the devices to back up, but if I had fixed addresses for my other devices that would help me to debug "strange" network problems. Big issue for me is the very complex password I use. It's a pain in the tuchus to type that in on an iPhone, or worse yet a Roku device. But in my heart I know I should do it. thanks for letting me know that SMB V1 is not an issue here. In general, home networking is a real weak spot within Windows. Windows forums are just filled with people complaining that system A can see system B and C, but C can't see A or B, and B can see only C.
  11. I just ran into the "client not found" error message on one client because Windows rebooted the system as part of a software update and the IP address, being DHCP-based, changed. 😩 So I was able to reconnect using IP Direct Connect, but that's not exactly a "scalable solution." I've been using Retrospect for at least 10 years now, and I don't remember having this problem years ago. I need Retrospect to automatically detect clients on my home LAN, even if the IP address has changed. The subnet address is always the same: 192.168.1.xx. So before posting, this time I did a search on "Piton client" and found six pages of links, and I opened up a lot of them. Lots of unfamiliar names in posts from 2005 or so. I even found some of my own old posts. One suggestion was to make sure that port 497 is open on the firewall. I use Norton Internet Security, not Windows Defender, so I added an Allow rule for port 497 on both server and a test client. No joy. So I fell back to direct connect to connect to the problem, which did work, but I'm not happy about it because that's just muddling along, and not addressing the root cause. I'm running Retrospect, with latest version client. The last post in this thread seems to hold out a glimmer of hope that Retrospect 17 can detect a client with a changed IP address. Is that true? If it is, then I will upgrade to V17 as fast as I can pull out my credit card. I know that another option is to make DHCP assign fixed addresses to the client machines, and I'll probably do that when I have some time. Maybe it's time for me to create a IP address plan for all the devices on my network, computers, phones, tablets, TVs, Roku stick, etc. (Believe or not, the Covid lockdown seems to keep me busier than ever. Who knew?) But I still think the problem should be fixed at the source. Question: Does Piton depend on SMB V1? That protocol is supposed to be disabled due to serious security vulnerabilities. Second question: Does Apple Bonjour interfere with Piton? Third question: Does your head hurt now?
  12. I removed all the Lenovo utilities I could using Revo Uninstaller, but some of them reappeared. For now I have probably solved this issue, but stomping out those utilities may take more effort.
  13. So I thought that maybe, just maybe, there was some software on the problem client that isn't running on my other laptop client. And sure enough, I found it. I ran Task Manager to look at all the background processes, and found a bunch of Lenovo system monitoring software tools. I stopped one of those services, ran two of those scripts, and whaddya know, as they say in my hometown of New York City, they both ran fine. Problem solved. Thanks to everyone in this group for their past posts, which I read through for ideas.
  14. I just ran three scripts to back up a system on which I had just gotten the client software to work again. These scripts have been in service for a long time. D DATA D DATA Transact Date E Media Library. The first script ran fine and performed the expected backup. The second script failed for this client, with the 505 error message. So did the third script. So I did Configure | Clients | Access tab and clicked the Change button. Using Multicast - Piton Name Service, this client was found instantly. Back in the General tab, I clicked on Refresh and the client was "in Use, as expected. Now I reran the second and third scripts. The second script ran fine, but the third script failed with the 505 error message. So i repeated the Configure | Clients step, got the client to be "in use," and reran the third script. Now the third script ran fine. I should add that when I first had this 505 error, I changed client access from Piton to direct address u sing the IP address of the client. Same result. I am aware of the common cause of 505 errors, which is some other software running on the client that somehow blocks Retrospect, but if that were the case here, then why would the first script to be run after Access operation work fine? So on the surface it would appear that rerunning client Access somehow "unreserves" the client. What am I missing here?
  15. So here is what I did, which solved my original problem and then created that damn 505, client reserved problem. To get the Retrospect client to work again, I did a full, complete uninstall (using Revo Uninstaller Pro) and then a full install. That worked, and now the server machine recognizes the client as being "in use." But I ran into a strange version of the 505 error, which I am going to cover in a new post.