Support Forums

Okay, I downloaded and installed RIP on my local system (standalone, not part of a domain, XP SP2), and took a look at the output.  Neither Running Applications nor Open Ports have anything listed, and I ran this from an admin-level account.

Thoughts?

Thanks,

Harlan

Harlan,

Good to hear from you. Fetching the Running Applications on a local Vista system was a known issue on the release. The port scan may not have been enabled since it is not by default. Check the settings to see. The port scan happens in the background. We have a build with the Vista issue corrected and will have it posted later on this week.

 

Chris,

Chris:

Good to hear from you. Fetching the Running Applications on a local Vista system was a known issue on the release. The port scan may not have been enabled since it is not by default. Check the settings to see. The port scan happens in the background. We have a build with the Vista issue corrected and will have it posted later on this week.

Thanks but I'm not sure how that addresses my question...I had said:

" I downloaded and installed RIP on my local system (standalone, not part of a domain, XP SP2)"

My system is XP SP 2, not Vista.

Thanks,

Harlan

Harlan,

I guess it doesn't then. I’ve been moving fairly fast trying to recover from Chairing the HTCIA Conference this week. Maybe the issue is related to interfaces on your system. I know when testing we found issues when the local machine interface was identified as one that was firewalled or inside a connected VPN.  

I knew I could count on you to find something :)

Harlan,

Similar results here with Compaq laptop running Win XP Sp2:
1) not network connected: local computer reports only running apps and disk vol
2) connected to network (domain, large): local computer reports only  user info and network shares
(note that different areas are reported for local computer in both cases).

Also found that disabling network discovery in Tools - Settings does not disable remote computers scanning (scans the same remote computers regardless of the "enable network discovery" option enabled or disabled).

Derek

Derek/Harlan,

I recreated this on a system without network access. When network access was restored the issue was corrected.

Looks like this may have something to do with authentication or the state of the interface. We'll look into it.