
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-26-2005 03:13 AM
Hi guys,
Hopefully someone can help me out here. I've got this product working great for 75% of our fleet, BUT we are piloting XP SP2 on some of the remainder. When i turn OFF the XP firewall completely, the scan works great, but when its turned ON I get the error below. Extra Info .... I have added an exemption for port 9524 in the XP firewall as the notes say too. Other TCP ports open include 135, 139, 445, 1226
026 26/05/2005 8:50:47 AM (IEEXT) compname.xxx.com.au The format of the specified computer name is invalid.
006 26/05/2005 8:52:06 AM (IEBARS) compname.xxx.com.au The format of the specified computer name is invalid.
I've turned on logging for the XP firewall and noticed many different ports being used for communication between client and audit server during the audit that have been dropped by XP.
I really want to nail this port problem because i then have to open the same ports for our remote dial up users on the router. Remote users are showing the same symptoms but are only Win2k clients. They work sweet when plugged directly to the LAN, but fail when dialing in with the same errors above.
Has anyone else encountered something like this that can shed some light on the subject ??
Cheers,
Mitch
:w)
Hopefully someone can help me out here. I've got this product working great for 75% of our fleet, BUT we are piloting XP SP2 on some of the remainder. When i turn OFF the XP firewall completely, the scan works great, but when its turned ON I get the error below. Extra Info .... I have added an exemption for port 9524 in the XP firewall as the notes say too. Other TCP ports open include 135, 139, 445, 1226
026 26/05/2005 8:50:47 AM (IEEXT) compname.xxx.com.au The format of the specified computer name is invalid.
006 26/05/2005 8:52:06 AM (IEBARS) compname.xxx.com.au The format of the specified computer name is invalid.
I've turned on logging for the XP firewall and noticed many different ports being used for communication between client and audit server during the audit that have been dropped by XP.
I really want to nail this port problem because i then have to open the same ports for our remote dial up users on the router. Remote users are showing the same symptoms but are only Win2k clients. They work sweet when plugged directly to the LAN, but fail when dialing in with the same errors above.
Has anyone else encountered something like this that can shed some light on the subject ??
Cheers,
Mitch
:w)
Labels:
- Labels:
-
Archive
5 REPLIES 5

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-12-2005 03:39 PM
That seems to have done it for my XP SP2 installs. Thanks for the help. Great product.
Thanks
Dave
Thanks
Dave
Thanks
Dave

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-11-2005 03:37 PM
Group policy:
Computer Configuration/administrative templates/network/network connections/windows firewall/domain profile/allow remote administration exception
Computer Configuration/administrative templates/network/network connections/windows firewall/domain profile/allow remote administration exception

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-08-2005 08:38 PM
I have searched through my Group Policies and cannot find the "Remote management" setting. Can anyone point me in the correct direction?
Thanks
"Blind" person.
Thanks
"Blind" person.
Thanks
Dave

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-27-2005 05:31 AM
IEEXT and IEBARS scan uses remote registry, so you have to allow this.
In a future update (next week if I have time) the scan will be based on ipaddress instead of hostname, this will solve the dial in errors.
In a future update (next week if I have time) the scan will be based on ipaddress instead of hostname, this will solve the dial in errors.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-27-2005 04:32 AM
You have to enable "remote management" (this should be enough)
You can do this using group policies.
You can do this using group policies.
