GD Bloggers

This is the blog site for Microsoft Global Delivery Communities focused in sharing the technical knowledge about devices, apps and cloud.
Follow Us On Twitter! Subscribe To Our Blog! Contact Us

WSPAD file is in bad format

WSPAD file is in bad format

  • Comments 1
  • Likes

 

 

I’ve been configuring TMG auto client proxy detection and it was failing. After researching it online and internally, didn’t find anything useful.

So when I installed the TMG client and run this test:

C:\Program Files (x86)\Forefront TMG Client>FwcTool.exe testautodetect
FwcTool version 7.0.7734.100
Forefront TMG Client support tool
Copyright (c) Microsoft Corporation. All rights reserved.
Action: Test the auto detection mechanism
Type: Default
Detection details:
Timeout is set to 60 seconds
Locating WSPAD URL on the Active Directory server
WSPAD object was found in the global Active Directory container
WSPAD URL found on the Active Directory server:
http://XXX.YYY.com:8080/wpad.dat

Initializing Web server connection
Resolving IP addresses for XXX.YYY.com
Resolved 1 address(es):
10.0.110.110
Connecting to address #1: 10.0.110.110:8080
Waiting for address #1 to connect
Address #1 successfully connected
Requesting wspad.dat file
Web server is connected and ready to send WSPAD file
Downloading WSPAD file
WSPAD file was downloaded successfully
WSPAD file is in bad format
Failed to detect Forefront TMG
Result: The command failed and was not completed.

 

So in able to fix that, I’ve changed the SCP from wpad to wspad using adsiedit (or you can use the tmgadconfig tool again with –f switch)

 

Hope this helps!

M

Comments
  • i have the same issue. please any one can help us

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment