Jump to content

PeterJT

Members
  • Content count

    11
  • Joined

  • Last visited

Community Reputation

0 Neutral

About PeterJT

  • Rank
    Occasional Forum Poster
  1. PeterJT

    Windows XP / SP2

    With the general availabilty of Windows/XP SP2, it's built in firewall causes problems for Retrospect Professional 6.5.350. With the Retrospect installed on a machine with XP/SP2, and the firewall active, it it unable to find another Windows/XP machine that has the Retrospect client installed. If the firewall is shut down, this problem does disappear. Does Dantz have any ETA for an updated version that will not have this isse? Peter
  2. PeterJT

    Retrospect for LINUX

    Well, one solution that is very possible (although maybe overkill) is IBM's Tivoli Storage Manager. Server can be Linux / AIX / HPux / Windows /Solaris / Mainframe Clients can be all of the above plus Mac (and other's I didn't feel like listing). http://www-306.ibm.com/software/tivoli/products/storage-mgr/
  3. PeterJT

    Retrospect Professional and Port Usage

    I think you'll find I was the original poster <g> I'm more than willing to work with you on this; All I've been trying to say all along is that there WAS a problem, and how do I work with you and with Microsoft to get this resolved. Not quite so frustrated... Petet
  4. PeterJT

    Retrospect Professional and Port Usage

    I;m not sure if you looked closely at that trace. if yoiu break the fields according to the information above them you will see the follpowing: #Fields: date 2004-05-06 time 01:23:13 action DROP protocol UDP src-ip 192.168.1.102 dst-ip 192.168.1.101 src-port 497 dst-port 2709 size 224 tcpflags - tcpsyn - tcpack - tcpwin - icmptype - icmpcode - info - path RECEIVE The 224 that is above has nothing to do with multicast; rather it is the size of the datagram that was "returned" by the client machine on 192.168.1.102 to the server on 192.168.1.101. Client data flow was initiated from port 497 to server port 2709. As I indicated in my earlier post, the "port"s in use on the server side change; this has nothing to do with "udp scan-change", rather in how the Operating system is assigning port's to the application as it runs. Normally, "server" class applications while they might INITIATE a communications from any port, will "LISTEN" on a well-known port; this for instance is why a web-server "listens" on port 80. This is also the model that Microsoft has implemented within their firewall component; you "name" the ports that a server LISTENS on. Unfortunately, it would appear that the Retrospect SERVER INITIATES from a non-well known port, and also LISTENS on a non-well known, TRANSIENT port. Peter
  5. PeterJT

    Retrospect Professional and Port Usage

    Here's some information that I think might show otherwise. This is captured from the Microsoft Windows Firewall log file, and shows two attempts to "connect" to a client machine from within Retrospect Professional. Please observe that while the Retrospect attempts to talk to the CLIENT on port 497, the client is attempting to establish a connection to a non-registered [ephermal] port on the SERVER; in fact, the CLIENT "appears" to be connecting to the a port one greater than the port that the SERVER had initiated his session from. With Microsoft's forthcoming standard of ACTIVATING this Windows Firewall on all XP systems with the deployment of SP2, it is safe to say that unless Dantz ACTIVELY investigates this issue, that when SP2 IS released to the public you will have many, many additional support requests. ======= Rules in effect at this time: ALLOW Program name "C:\Program Files\Dantz\Retrospect.exe" FULL access to internet Attempt made from 192.168.1.101 to "REFRESH" the stats of a client located at 192.168.1.102 #Version: 1.5 #Software: Microsoft Windows Firewall #Time Format: Local #Fields: date time action protocol src-ip dst-ip src-port dst-port size tcpflags tcpsyn tcpack tcpwin icmptype icmpcode info path 2004-05-06 01:23:13 OPEN UDP 192.168.1.101 192.168.1.102 2708 497 - - - - - - - - - 2004-05-06 01:23:13 DROP UDP 192.168.1.102 192.168.1.101 497 2709 224 - - - - - - - RECEIVE 2004-05-06 01:23:15 DROP UDP 192.168.1.102 192.168.1.101 497 2709 224 - - - - - - - RECEIVE 2004-05-06 01:23:17 DROP UDP 192.168.1.102 192.168.1.101 497 2709 224 - - - - - - - RECEIVE 2004-05-06 01:23:19 DROP UDP 192.168.1.102 192.168.1.101 497 2709 224 - - - - - - - RECEIVE 2004-05-06 01:23:21 DROP UDP 192.168.1.102 192.168.1.101 497 2709 224 - - - - - - - RECEIVE 2004-05-06 01:23:21 DROP UDP 192.168.1.102 192.168.1.101 497 2709 224 - - - - - - - RECEIVE 2004-05-06 01:23:21 DROP UDP 192.168.1.102 192.168.1.101 497 2709 224 - - - - - - - RECEIVE 2004-05-06 01:23:23 DROP UDP 192.168.1.102 192.168.1.101 497 2709 224 - - - - - - - RECEIVE 2004-05-06 01:23:24 DROP UDP 192.168.1.102 192.168.1.101 497 2709 224 - - - - - - - RECEIVE 2004-05-06 01:23:26 DROP UDP 192.168.1.102 192.168.1.101 497 2709 224 - - - - - - - RECEIVE 2004-05-06 01:23:26 DROP UDP 192.168.1.102 192.168.1.101 497 2709 224 - - - - - - - RECEIVE 2004-05-06 01:23:28 DROP UDP 192.168.1.102 192.168.1.101 497 2709 224 - - - - - - - RECEIVE 2004-05-06 01:23:28 DROP UDP 192.168.1.102 192.168.1.101 497 2709 224 - - - - - - - RECEIVE 2004-05-06 01:23:30 DROP UDP 192.168.1.102 192.168.1.101 497 2709 224 - - - - - - - RECEIVE 2004-05-06 01:23:30 DROP UDP 192.168.1.102 192.168.1.101 497 2709 224 - - - - - - - RECEIVE Observe: Communication initated from Server -> Client Server Port 2708 -> Client 497 2004-05-06 01:23:13 OPEN UDP 192.168.1.101 192.168.1.102 2708 497 - - - - - - - - - Client attempts to talk back to server but is blocked Client Port 497 -> Server 2709 2004-05-06 01:23:13 DROP UDP 192.168.1.102 192.168.1.101 497 2709 224 - - - - - - - RECEIVE ------ Second attempt: Rules in effect at this time: ALLOW Program name "C:\Program Files\Dantz\Retrospect.exe" FULL access to internet ALLOW Ports 497 both TCP and UDP Attempt made from 192.168.1.101 to "REFRESH" the stats of a client located at 192.168.1.102 #Version: 1.5 #Software: Microsoft Windows Firewall #Time Format: Local #Fields: date time action protocol src-ip dst-ip src-port dst-port size tcpflags tcpsyn tcpack tcpwin icmptype icmpcode info path 2004-05-06 01:29:37 OPEN UDP 192.168.1.101 192.168.1.102 2718 497 - - - - - - - - - 2004-05-06 01:29:37 DROP UDP 192.168.1.102 192.168.1.101 497 2719 224 - - - - - - - RECEIVE 2004-05-06 01:29:39 DROP UDP 192.168.1.102 192.168.1.101 497 2719 224 - - - - - - - RECEIVE 2004-05-06 01:29:41 DROP UDP 192.168.1.102 192.168.1.101 497 2719 224 - - - - - - - RECEIVE 2004-05-06 01:29:43 DROP UDP 192.168.1.102 192.168.1.101 497 2719 224 - - - - - - - RECEIVE 2004-05-06 01:29:45 DROP UDP 192.168.1.102 192.168.1.101 497 2719 224 - - - - - - - RECEIVE 2004-05-06 01:29:45 DROP UDP 192.168.1.102 192.168.1.101 497 2719 224 - - - - - - - RECEIVE 2004-05-06 01:29:45 DROP UDP 192.168.1.102 192.168.1.101 497 2719 224 - - - - - - - RECEIVE 2004-05-06 01:29:47 DROP UDP 192.168.1.102 192.168.1.101 497 2719 224 - - - - - - - RECEIVE 2004-05-06 01:29:48 DROP UDP 192.168.1.102 192.168.1.101 497 2719 224 - - - - - - - RECEIVE 2004-05-06 01:29:50 DROP UDP 192.168.1.102 192.168.1.101 497 2719 224 - - - - - - - RECEIVE 2004-05-06 01:29:50 DROP UDP 192.168.1.102 192.168.1.101 497 2719 224 - - - - - - - RECEIVE 2004-05-06 01:29:52 DROP UDP 192.168.1.102 192.168.1.101 497 2719 224 - - - - - - - RECEIVE 2004-05-06 01:29:52 DROP UDP 192.168.1.102 192.168.1.101 497 2719 224 - - - - - - - RECEIVE 2004-05-06 01:29:54 DROP UDP 192.168.1.102 192.168.1.101 497 2719 224 - - - - - - - RECEIVE 2004-05-06 01:29:54 DROP UDP 192.168.1.102 192.168.1.101 497 2719 224 - - - - - - - RECEIVE No change; observe though that this time the Retrospect server is using the port pair 2718/2719 as opposed to the first run using 2708/2709
  6. PeterJT

    Retrospect Professional and Port Usage

    Believe me, this HAS been done and has not helped. Peter
  7. Dantz I'm getting kind of frustrated by the lack of responses to questions myself and other are posting regarding Retrospect Professional and TCP/IP port usage. Presently, I have NO choice but to disable any firewall sofiware on the machine where Retrospect Professional 6.5.350 is running when I attempt to perform a backup of another machine. Statements that 'Port 497 are required to be open' might be true on the CLIENT side but not the server. This evening I found that onve again, backups of my wife's machine had failed with the message 'unable to find SUESP4', A quick shutdown of the the Microsoft Firewall from XP-SP2 and a manual run worked. Viewing the connections active between the two systems we see TCP 192.168.1.100:2506 192.168.1.102:497 ESTABLISHED where 192.168.1.100 is the BACKUP server and 192.168.1.102 is the CLIENT machine. Yes; 497 is the SOURCE port for traffic from the client, but not the DESTINATION port. The Microsoft Firewall is after the DESTINATION port on the BACKUP server. At what point will Dantz make any statement about a workaround for this? I see some people have taken the approach of openning a large range of ports. This is not a vialble option... Peter
  8. PeterJT

    6.5 for Windows Update

    No it does not.. I have openned 497 (both TCP and UDP) on the server and still have no luck.
  9. PeterJT

    6.5 for Windows Update

    Has there yet been any steps taken to solve the issues of the Retrospect SERVER running on a machine that has the Microwoftt Firewall active (see a post I made in March in this forum that has yet to get any resposnes).... I know that there ios documentation on how to get the CLIENT to coexist with the firewall, but the upcoming challenge will be with the introduction of XP SP2 as to HOW to get the SERVER to coexist with the firewall. Patiently Waiting for a reponse Peter
  10. I've been taking part in the Microsoft Beta program, and now, with the newest release of XP SP2 I decided to activate the Window's Firewall on the machine that is axting as my Retrospect server. I have (I beleive) followed directions and enabled port 497 (for both TCP and UDP protocols) within the firewall setup, but, when I attempt to connect to another XP machine [just running RC1] I am told "SOrry, couldn't connect to SUESP4, error -530 (backup client not found)". The instant I disable the firewall all works again. The properties for this client indicate the correct IP address and access method of "Multicast - Piton Name service". I have experimented within the Firewall setup tool with changing the subnet's from which connectins are allowed from same subnet to any address, but this has made no change. Looking in the log file that Microsoft has (pfirewall.log) however I see the following: #Fields: date time action protocol src-ip dst-ip src-port dst-port size tcpflags tcpsyn tcpack tcpwin icmptype icmpcode info 2004-03-23 08:21:23 DROP UDP 192.168.1.104 192.168.1.105 497 1356 224 - - - - - - - RECEIVE 2004-03-23 08:21:25 DROP UDP 192.168.1.104 192.168.1.105 497 1356 224 - - - - - - - RECEIVE 2004-03-23 08:21:27 DROP UDP 192.168.1.104 192.168.1.105 497 1356 224 - - - - - - - RECEIVE 2004-03-23 08:21:29 DROP UDP 192.168.1.104 192.168.1.105 497 1356 224 - - - - - - - RECEIVE 2004-03-23 08:21:31 DROP UDP 192.168.1.104 192.168.1.105 497 1356 224 - - - - - - - RECEIVE 2004-03-23 08:21:31 DROP UDP 192.168.1.104 192.168.1.105 497 1356 224 - - - - - - - RECEIVE 2004-03-23 08:21:32 DROP UDP 192.168.1.104 192.168.1.105 497 1356 224 - - - - - - - RECEIVE 2004-03-23 08:21:34 DROP UDP 192.168.1.104 192.168.1.105 497 1356 224 - - - - - - - RECEIVE 2004-03-23 08:21:34 DROP UDP 192.168.1.104 192.168.1.105 497 1356 224 - - - - - - - RECEIVE 2004-03-23 08:21:36 DROP UDP 192.168.1.104 192.168.1.105 497 1356 224 - - - - - - - RECEIVE 2004-03-23 08:21:36 DROP UDP 192.168.1.104 192.168.1.105 497 1356 224 - - - - - - - RECEIVE 2004-03-23 08:21:38 DROP UDP 192.168.1.104 192.168.1.105 497 1356 224 - - - - - - - RECEIVE 2004-03-23 08:21:38 DROP UDP 192.168.1.104 192.168.1.105 497 1356 224 - - - - - - - RECEIVE 2004-03-23 08:21:40 DROP UDP 192.168.1.104 192.168.1.105 497 1356 224 - - - - - - - RECEIVE 2004-03-23 08:21:40 DROP UDP 192.168.1.104 192.168.1.105 497 1356 224 - - - - - - - RECEIVE 2004-03-23 08:22:31 DROP UDP 192.168.1.104 192.168.1.105 497 1370 224 - - - - - - - RECEIVE 2004-03-23 08:22:33 DROP UDP 192.168.1.104 192.168.1.105 497 1370 224 - - - - - - - RECEIVE 2004-03-23 08:22:35 DROP UDP 192.168.1.104 192.168.1.105 497 1370 224 - - - - - - - RECEIVE 2004-03-23 08:22:37 DROP UDP 192.168.1.104 192.168.1.105 497 1370 224 - - - - - - - RECEIVE 2004-03-23 08:22:39 DROP UDP 192.168.1.104 192.168.1.105 497 1370 224 - - - - - - - RECEIVE 2004-03-23 08:22:39 DROP UDP 192.168.1.104 192.168.1.105 497 1370 224 - - - - - - - RECEIVE 2004-03-23 08:22:39 DROP UDP 192.168.1.104 192.168.1.105 497 1370 224 - - - - - - - RECEIVE 2004-03-23 08:22:41 DROP UDP 192.168.1.104 192.168.1.105 497 1370 224 - - - - - - - RECEIVE 2004-03-23 08:22:41 DROP UDP 192.168.1.104 192.168.1.105 497 1370 224 - - - - - - - RECEIVE 2004-03-23 08:22:43 DROP UDP 192.168.1.104 192.168.1.105 497 1370 224 - - - - - - - RECEIVE 2004-03-23 08:22:43 DROP UDP 192.168.1.104 192.168.1.105 497 1370 224 - - - - - - - RECEIVE 2004-03-23 08:22:46 DROP UDP 192.168.1.104 192.168.1.105 497 1370 224 - - - - - - - RECEIVE 2004-03-23 08:22:46 DROP UDP 192.168.1.104 192.168.1.105 497 1370 224 - - - - - - - RECEIVE 2004-03-23 08:22:48 DROP UDP 192.168.1.104 192.168.1.105 497 1370 224 - - - - - - - RECEIVE 2004-03-23 08:22:48 DROP UDP 192.168.1.104 192.168.1.105 497 1370 224 - - - - - - - RECEIVE 2004-03-23 08:25:29 DROP UDP 192.168.1.104 192.168.1.105 497 1408 224 - - - - - - - RECEIVE 2004-03-23 08:25:32 DROP UDP 192.168.1.104 192.168.1.105 497 1408 224 - - - - - - - RECEIVE 2004-03-23 08:25:34 DROP UDP 192.168.1.104 192.168.1.105 497 1408 224 - - - - - - - RECEIVE 2004-03-23 08:25:36 DROP UDP 192.168.1.104 192.168.1.105 497 1408 224 - - - - - - - RECEIVE 2004-03-23 08:25:38 DROP UDP 192.168.1.104 192.168.1.105 497 1408 224 - - - - - - - RECEIVE 2004-03-23 08:25:38 DROP UDP 192.168.1.104 192.168.1.105 497 1408 224 - - - - - - - RECEIVE 2004-03-23 08:25:38 DROP UDP 192.168.1.104 192.168.1.105 497 1408 224 - - - - - - - RECEIVE 2004-03-23 08:25:40 DROP UDP 192.168.1.104 192.168.1.105 497 1408 224 - - - - - - - RECEIVE 2004-03-23 08:25:40 DROP UDP 192.168.1.104 192.168.1.105 497 1408 224 - - - - - - - RECEIVE 2004-03-23 08:25:42 DROP UDP 192.168.1.104 192.168.1.105 497 1408 224 - - - - - - - RECEIVE 2004-03-23 08:25:42 DROP UDP 192.168.1.104 192.168.1.105 497 1408 224 - - - - - - - RECEIVE 2004-03-23 08:25:44 DROP UDP 192.168.1.104 192.168.1.105 497 1408 224 - - - - - - - RECEIVE 2004-03-23 08:25:44 DROP UDP 192.168.1.104 192.168.1.105 497 1408 224 - - - - - - - RECEIVE 2004-03-23 08:25:47 DROP UDP 192.168.1.104 192.168.1.105 497 1408 224 - - - - - - - RECEIVE 2004-03-23 08:25:47 DROP UDP 192.168.1.104 192.168.1.105 497 1408 224 - - - - - - - RECEIVE 192.168.1.104 == SUESP4 == The CLIENT 192.168.1.105 == PETERSP3 == The server Any advice? Peter All versions of Retrospect clients are current as of what is available on your website. Server 6.5.343 RDU 4.9.101 Client 6.5.136
  11. I have an Onstream DI30 in my system. Am using Windwos/XP Pro, Retrospect Desktop 5.6.132 and drivers 2.8.111. I find that if I insert the tape I know is needed for the next backup, when I quit and select the "Verify Media" option, it will always come back and tell me that the required media is not mounted. If I then quit (and check) a second time, it finds the correct tape is loaded. Also, if I change the tape while sitting in Devices | Status it will show me the right volume (howver, it takes far longer than the Verify Media option appears to want to wait ) Is this working as expected, or should the verify media wait longer before reporting that the the required media is NOT available? Peter
×