Welcome to ISAserver.org

RE: "Automatically Detect Settings" in IE doesn't work.

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Threat Management Gateway (TMG) 2010] >> General >> RE: "Automatically Detect Settings" in IE doesn't work.

Page: << < prev 1 [2]

Message

<< Older Topic Newer Topic >>

RE: "Automatically Detect Settings" in IE doe... - 1.Dec.2009 11:08:20 AM

awj

Posts: 107
Joined: 26.Feb.2004
From: UK
Status: offline

I have not, i guess i hoped they may monitor here but that may be too much to hope for.

(in reply to dmutsaers)

Post #: 21

Featured Links*

RE: "Automatically Detect Settings" in IE doe... - 1.Dec.2009 2:05:26 PM

Emptyone

Posts: 12
Joined: 11.May2003
Status: offline

After changing over to a static pool, all looks good. And I also think the bug is a bit different that I first thought. If you try to add a static pool in the internal range, you will get an error. And I see the reason why. The VPN clients is supposed to be on a different network, to be able to seperate them from the internal and limit the traffic. I made a static pool of addresses outside the internal range, all works as it should. So from the error message MS shows on the static pool, I think they also need a message telling about the "error" when you choose a interface that is in the internal range

(in reply to awj)

Post #: 22

RE: "Automatically Detect Settings" in IE doe... - 3.Dec.2009 9:54:03 AM

tshinder

Posts: 50013
Joined: 10.Jan.2001
From: Texas
Status: offline

OK, let's define the problem:

When you use DHCP to assign IP addresses to VPN clients, the TMG firewall assigns wpad clients a random assortment of addresses to connect to the firewall to obtain autodiscovery information?

When you use static IP addresses, the internal IP address of the firewall is always used to point to the autodisocvery listener?

Thanks!
Tom

_____________________________

Thomas W Shinder, M.D.

(in reply to dmutsaers)

Post #: 23

RE: "Automatically Detect Settings" in IE doe... - 3.Dec.2009 10:17:51 AM

dmutsaers

Posts: 105
Joined: 1.Aug.2003
From: The Netherlands
Status: offline

Yes, that summarizes the problem. The random address is the DHCP address assigned to the RRAS server adapter.

(in reply to tshinder)

Post #: 24

RE: "Automatically Detect Settings" in IE doe... - 4.Dec.2009 9:07:39 AM

tshinder

Posts: 50013
Joined: 10.Jan.2001
From: Texas
Status: offline

OK, great.
Let's see if we can get MS to look at this.

Thanks!
Tom

_____________________________

Thomas W Shinder, M.D.

(in reply to dmutsaers)

Post #: 25

RE: "Automatically Detect Settings" in IE doe... - 7.Dec.2009 6:25:03 PM

tshinder

Posts: 50013
Joined: 10.Jan.2001
From: Texas
Status: offline

It looks like this is a potential problem and MS is looking into it.

Thanks!

Tom

_____________________________

Thomas W Shinder, M.D.

(in reply to tshinder)

Post #: 26

RE: "Automatically Detect Settings" in IE doe... - 8.Dec.2009 5:10:40 AM

azure

Posts: 9
Joined: 18.Nov.2009
Status: offline

Hey guys,

I am actually facing the same issue.

I have VPN clients (SSTP) WPAD used and according to network trace the clients require the wpad form the IP of the RAS interface insteads of the internal interace.
It is working fine for vpn clients but not for internal servers in the internal network.

The clients have the same range as the internal network and get their IPs from the internal DHCP.

Hope MS can clarify this ^^

(in reply to tshinder)

Post #: 27

RE: "Automatically Detect Settings" in IE doe... - 17.Dec.2009 8:09:59 AM

tshinder

Posts: 50013
Joined: 10.Jan.2001
From: Texas
Status: offline

Yes -- they're investigating.

HTH,
Tom

_____________________________

Thomas W Shinder, M.D.

(in reply to dmutsaers)

Post #: 28

RE: "Automatically Detect Settings" in IE doe... - 19.Jan.2010 7:37:08 AM

annihilator

Posts: 1
Joined: 19.Jan.2010
Status: offline

Any resolution as of yet? It's been a month.

(in reply to tshinder)

Post #: 29

RE: "Automatically Detect Settings" in IE doe... - 25.Feb.2010 4:15:34 PM

dvreede

Posts: 5
Joined: 25.Feb.2010
Status: offline

Hello Everybody, I have got the same problem. With ISA 2006 no problems, but today I upgraded to ISA 2010 TMG and now the auto discover for my internal clients does not work anymore. The wpad scipt that the TMG server provides to my clients contains the last assigned RAS address from my DHCP server in the "New Node" value. So the client does connect to the ISA's ras adress pool instead of the ISA internal LAN ip-address.

What am I doing wrong? Microsoft please help!

(in reply to dmutsaers)

Post #: 30

RE: "Automatically Detect Settings" in IE doe... - 8.Apr.2010 2:49:29 AM

dmutsaers

Posts: 105
Joined: 1.Aug.2003
From: The Netherlands
Status: offline

Any news?

(in reply to dvreede)

Post #: 31

RE: "Automatically Detect Settings" in IE doe... - 2.Jun.2010 5:55:30 AM

dmutsaers

Posts: 105
Joined: 1.Aug.2003
From: The Netherlands
Status: offline

Still no fix for this bug?

(in reply to dmutsaers)

Post #: 32

RE: "Automatically Detect Settings" in IE doe... - 21.Jul.2010 3:58:20 PM

a.vishnevskiy

Posts: 3
Joined: 4.Jun.2010
Status: offline

Hope that'll help someone who didn't find the fix. There is a known workaround with this script: http://isatools.org/tools/carpnamesystem.js

cscript carpnamesystem.js /set:DNS

It sets proxy address in the wpad.dat to FQDN instead of IP (which in our case is a RRAS one)

(in reply to dmutsaers)

Post #: 33