Solved

Get WPAD Autoconfig on port 80.

Posted on 2009-05-14
8
1,323 Views
Last Modified: 2012-05-07
Hello,

I have the DNS record in for wpad and wspad, and that works fine as far as I can see (test ping wpad).
When I test the Automatic config, I put http://ISASERVER/wpad.dat in my web browser, the page cannot be displayed. But when I put http://ISASERVER:8080/wpad.dat in the browser, it works.

The problem here is that I have to use prot 80, because I'm using DNS for the resolution. I have set the propperties in the ISA mgt console to use port 80, but it still goes to port 8080. The WEB Proxy detection is on port 8080.

How can I reset the Autoconfig to work on port 80?

Ampletrix.
0
Comment
Question by:Ampletrix
  • 4
  • 4
8 Comments
 
LVL 14

Assisted Solution

by:Raj-GT
Raj-GT earned 250 total points
ID: 24393141
Do you have IIS or any web servers running on your ISA Server?  (Dell OpenManage etc.)

Open a command prompt and run netstat -b and see what is listening on port 80.
0
 

Author Comment

by:Ampletrix
ID: 24401422
This is a capture from netstat -b:

Active Connections

  Proto  Local Address          Foreign Address        State           PID
  TCP    isa_server:1092          isa_server.sop.plm:3151  ESTABLISHED     2512
  [wspsrv.exe]

  TCP    isa_server:1092          isa_server.sop.plm:3158  ESTABLISHED     2512
  [wspsrv.exe]

  TCP    isa_server:remote-winsock  ln000081.sop.plm:2770  ESTABLISHED     2512
  [wspsrv.exe]

  TCP    isa_server:remote-winsock  ln000081.sop.plm:2787  ESTABLISHED     2512
  [wspsrv.exe]

  TCP    isa_server:remote-winsock  ln000081.sop.plm:1052  ESTABLISHED     2512
  [wspsrv.exe]

  TCP    isa_server:3151          dc3_server.sop.plm:epmap  ESTABLISHED     436
  [lsass.exe]

  TCP    isa_server:3152          dc3_server.sop.plm:epmap  ESTABLISHED     2512
  [wspsrv.exe]

  TCP    isa_server:3153          dc3_server.sop.plm:1026  ESTABLISHED     436
  [lsass.exe]

  TCP    isa_server:3158          dc1_Server.sop.plm:epmap  ESTABLISHED     436
  [lsass.exe]

  TCP    isa_server:3159          dc1_Server.sop.plm:epmap  ESTABLISHED     2512
  [wspsrv.exe]

  TCP    isa_server:3160          dc1_Server.sop.plm:1025  ESTABLISHED     436
  [lsass.exe]

  TCP    isa_server:3172          fp_server2.sop.plm:microsoft-ds  ESTABLISHED     4
  [System]

  TCP    isa_server:3191          fp_server3.sop.plm:microsoft-ds  ESTABLISHED     4
  [System]

  TCP    isa_server:3201          su_server1.sop.plm:microsoft-ds  ESTABLISHED     4
  [System]

  TCP    isa_server:3212          dc3_server.sop.plm:1026  ESTABLISHED     436
  [lsass.exe]

  TCP    isa_server:3146          dc1_Server.sop.plm:netbios-ssn  TIME_WAIT       0
  TCP    isa_server:3147          dc1_Server.sop.plm:microsoft-ds  TIME_WAIT       0
  TCP    isa_server:3149          192.168.1.10:http     TIME_WAIT       0
  TCP    isa_server:3161          dc1_Server.sop.plm:microsoft-ds  TIME_WAIT       0
  TCP    isa_server:3168          dc1_Server.sop.plm:ldap  TIME_WAIT       0
  TCP    isa_server:3170          dc3_server.sop.plm:microsoft-ds  TIME_WAIT       0
  TCP    isa_server:3178          dc1_Server.sop.plm:microsoft-ds  TIME_WAIT       0
  TCP    isa_server:3185          dc1_Server.sop.plm:msft-gc  TIME_WAIT       0
  TCP    isa_server:3186          dc1_Server.sop.plm:msft-gc  TIME_WAIT       0
  TCP    isa_server:3187          dc1_Server.sop.plm:msft-gc  TIME_WAIT       0
  TCP    isa_server:3188          dc4_server.sop.plm:microsoft-ds  TIME_WAIT       0
  TCP    isa_server:3206          sms_server.sop.plm:microsoft-ds  TIME_WAIT       0
  TCP    isa_server:8080          ln000081.sop.plm:2792  TIME_WAIT       0
  TCP    isa_server:8080          ln000081.sop.plm:2802  TIME_WAIT       0

It doesn't look (to me) as if there's anything listening on port 80.
I made sure again that Automatic config is configured for port 80 and that web proxy is on port 8080 in the management console.

Ampletrix
0
 
LVL 14

Expert Comment

by:Raj-GT
ID: 24402031
Run netstat -a -n >> netstat.txt and copy the netstat.txt file here please.
0
 

Author Comment

by:Ampletrix
ID: 24408697
Hello Jaj-GT.

Here you go.

It looks like the server is not listening on port 80.

Thanks.

Ampletrix.

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    0.0.0.0:80             0.0.0.0:0              LISTENING
  TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:1043           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:1044           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:1049           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:1054           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:3389           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:3847           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:8081           0.0.0.0:0              LISTENING
  TCP    127.0.0.1:8080         0.0.0.0:0              LISTENING
  TCP    192.168.80.96:139      0.0.0.0:0              LISTENING
  TCP    192.168.80.96:1044     192.168.160.237:1642   ESTABLISHED
  TCP    192.168.80.96:1044     192.168.160.237:1644   ESTABLISHED
  TCP    192.168.80.96:1044     192.168.160.237:1647   ESTABLISHED
  TCP    192.168.80.96:1044     192.168.160.237:1650   ESTABLISHED
  TCP    192.168.80.96:1044     192.168.160.237:1659   ESTABLISHED
  TCP    192.168.80.96:1049     192.168.160.237:1640   ESTABLISHED
  TCP    192.168.80.96:1049     192.168.160.237:1645   ESTABLISHED
  TCP    192.168.80.96:1049     192.168.160.237:1649   ESTABLISHED
  TCP    192.168.80.96:1049     192.168.160.237:1660   ESTABLISHED
  TCP    192.168.80.96:1049     192.168.160.237:1667   ESTABLISHED
  TCP    192.168.80.96:1054     192.168.160.237:1641   ESTABLISHED
  TCP    192.168.80.96:1054     192.168.160.237:1648   ESTABLISHED
  TCP    192.168.80.96:1054     192.168.160.237:1658   ESTABLISHED
  TCP    192.168.80.96:1054     192.168.160.237:1692   ESTABLISHED
  TCP    192.168.80.96:1092     0.0.0.0:0              LISTENING
  TCP    192.168.80.96:1745     0.0.0.0:0              LISTENING
  TCP    192.168.80.96:1745     192.168.160.100:2945   ESTABLISHED
  TCP    192.168.80.96:1745     192.168.160.101:1567   ESTABLISHED
  TCP    192.168.80.96:3847     192.168.160.237:1636   ESTABLISHED
  TCP    192.168.80.96:3847     192.168.160.237:1643   ESTABLISHED
  TCP    192.168.80.96:3847     192.168.160.237:1646   ESTABLISHED
  TCP    192.168.80.96:3847     192.168.160.237:1666   ESTABLISHED
  TCP    192.168.80.96:3847     192.168.160.237:1700   ESTABLISHED
  TCP    192.168.80.96:6198     0.0.0.0:0              LISTENING
  TCP    192.168.80.96:6198     192.168.80.96:6996     ESTABLISHED
  TCP    192.168.80.96:6996     192.168.80.72:135      ESTABLISHED
  TCP    192.168.80.96:6997     192.168.80.72:135      ESTABLISHED
  TCP    192.168.80.96:6998     192.168.80.72:1025     TIME_WAIT
  TCP    192.168.80.96:7004     192.168.80.72:1025     ESTABLISHED
  TCP    192.168.80.96:7006     192.168.80.72:445      TIME_WAIT
  TCP    192.168.80.96:7012     192.168.80.71:389      TIME_WAIT
  TCP    192.168.80.96:7014     192.168.80.71:389      TIME_WAIT
  TCP    192.168.80.96:7015     192.168.80.74:445      TIME_WAIT
  TCP    192.168.80.96:7018     192.168.80.67:445      ESTABLISHED
  TCP    192.168.80.96:7026     192.168.80.71:445      TIME_WAIT
  TCP    192.168.80.96:7029     192.168.80.71:3268     TIME_WAIT
  TCP    192.168.80.96:7031     192.168.80.71:3268     TIME_WAIT
  TCP    192.168.80.96:7032     192.168.80.71:3268     TIME_WAIT
  TCP    192.168.80.96:7039     192.168.80.72:445      TIME_WAIT
  TCP    192.168.80.96:7042     192.168.80.81:445      ESTABLISHED
  TCP    192.168.80.96:7050     192.168.80.89:445      ESTABLISHED
  TCP    192.168.80.96:7061     192.168.80.100:445     TIME_WAIT
  TCP    192.168.80.96:7126     192.168.63.10:80       ESTABLISHED
  TCP    192.168.80.96:7129     192.168.63.10:80       ESTABLISHED
  TCP    192.168.80.96:8080     0.0.0.0:0              LISTENING
  TCP    192.168.80.96:8080     192.168.160.100:2996   TIME_WAIT
  TCP    192.168.80.96:8080     192.168.160.100:3028   ESTABLISHED
  TCP    192.168.80.96:8080     192.168.160.100:3030   ESTABLISHED
  TCP    192.168.80.96:8080     192.168.160.147:1306   ESTABLISHED
  UDP    0.0.0.0:445            *:*                    
  UDP    0.0.0.0:500            *:*                    
  UDP    0.0.0.0:4500           *:*                    
  UDP    0.0.0.0:8081           *:*                    
  UDP    0.0.0.0:8082           *:*                    
  UDP    127.0.0.1:123          *:*                    
  UDP    127.0.0.1:1025         *:*                    
  UDP    127.0.0.1:1045         *:*                    
  UDP    127.0.0.1:1063         *:*                    
  UDP    127.0.0.1:1088         *:*                    
  UDP    127.0.0.1:1465         *:*                    
  UDP    192.168.80.96:123      *:*                    
  UDP    192.168.80.96:137      *:*                    
  UDP    192.168.80.96:138      *:*                    
  UDP    192.168.80.96:1745     *:*                    
0
Threat Intelligence Starter Resources

Integrating threat intelligence can be challenging, and not all companies are ready. These resources can help you build awareness and prepare for defense.

 
LVL 14

Expert Comment

by:Raj-GT
ID: 24446404
Apologies for not answering this on time, been away for a few days :-)

1. Anyways, use the link below and check you have all the updates installed on your ISA Server.
http://technet.microsoft.com/en-us/forefront/edgesecurity/bb734854.aspx

2. Copy output from "ipconfig /all" here

3. Try disabling and re-enabling "Auto Discovery"
0
 

Author Comment

by:Ampletrix
ID: 24447842
Hello Raj-GT,

No worries. I was pretty croock too. Had a couple of days in bed.  ;-)

Here is the IPCONFIG info:



Windows IP Configuration



   Host Name . . . . . . . . . . . . : isa_server

   Primary Dns Suffix  . . . . . . . : sop.plm

   Node Type . . . . . . . . . . . . : Hybrid

   IP Routing Enabled. . . . . . . . : Yes

   WINS Proxy Enabled. . . . . . . . : No

   DNS Suffix Search List. . . . . . : sop.plm



Ethernet adapter Local Area Connection:



   Connection-specific DNS Suffix  . :

   Description . . . . . . . . . . . : VMware Accelerated AMD PCNet Adapter

   Physical Address. . . . . . . . . : 00-50-56-BD-35-98

   DHCP Enabled. . . . . . . . . . . : No

   IP Address. . . . . . . . . . . . : 192.168.80.96

   Subnet Mask . . . . . . . . . . . : 255.255.255.0

   Default Gateway . . . . . . . . . : 192.168.80.1

   DNS Servers . . . . . . . . . . . : 192.168.80.71

                                       192.168.80.72

   Primary WINS Server . . . . . . . : 192.168.80.74

I found and article about running IIS on the same server as ISA, and had a look at Autoconfig, but that didn't help me either.

I have tried reapplying as you suggested, but that did not work either.
After that, I rebuilt the server, and the AUtoconfig worked for a while, and I was doing all the rules and URL sets again, and it stopped working again. Very frustrating!

If I use http://wpad/wpad.dat it doesn't work, but http://wpad:8080/wpad.dat works.
I has to be on port 80.

Thanks for your help.
Ampletrix
0
 
LVL 14

Expert Comment

by:Raj-GT
ID: 24448927
Is your ISA Server fully patched?
Did you install any other software or drivers after the rebuild?
0
 

Accepted Solution

by:
Ampletrix earned 0 total points
ID: 24500061
I eneded up building a new IIS server and used this for the hosting of the WPAD files. I could not get it working on the same server. It is working fine now.

Ampletrix
0

Featured Post

Find Ransomware Secrets With All-Source Analysis

Ransomware has become a major concern for organizations; its prevalence has grown due to past successes achieved by threat actors. While each ransomware variant is different, we’ve seen some common tactics and trends used among the authors of the malware.

Join & Write a Comment

ISA Server detected routes through the network adapter LAN that do not correlate with the network to which this network adapter belongs What does this mean and how can one go about correcting it? In simple terms, this error message indicates t…
There are several problems reported according slow link speeds or poor performance in TMG 2010, UAG 2010 or ISA 2006. I want to collect here some of the common issues together to give a brief overview what can be the reason. Nevertheless, not all of…
Access reports are powerful and flexible. Learn how to create a query and then a grouped report using the wizard. Modify the report design after the wizard is done to make it look better. There will be another video to explain how to put the final p…
You have products, that come in variants and want to set different prices for them? Watch this micro tutorial that describes how to configure prices for Magento super attributes. Assigning simple products to configurable: We assigned simple products…

758 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

19 Experts available now in Live!

Get 1:1 Help Now