SimonC

Thanks - we're using a BAT file logon script at the moment. Is it possible to do a silent import of the key to the registry when the user logs on? Would we be better off using VBS?

I hope so as we should be moving to 2003 / 2007 once the Network Manager decides which to go for.... Does this mean users wont have to go through the exchange settings dialogue when they launch Outlook? Can see this being a nightmare for students & hot-desking staff....

Hi, We have 2 exchange 2000 servers - 1 for staff and 1 for students. We are using a logon script (bat file) profgen to map users to the right exchange server, but the college wants to move to Office 2003 - which dosen't use profgen. I know you can use the CMW / CIW to deploy profiles but I'm a bit confused over which way will work for us. We use ghost images instead of MSIs to deploy office, is there an easy way to deploy profiles without any user interaction? Cheers, Si

re: can't print from laptops Do the laptops have printers installed? if yes are you running local or network printers?

Hello, We are migrating to ISA 2004 from 2000, currently we have 2 ISA 2000 servers and 1 ISA 2004 server. The business has a split DNS, with internal DNS servers forwarding to the two ISA 2000 servers. This is a little unusual because the ISA 2000 servers are not caching-only, they contain host (etc.) records that point to services on the network (via the ISA 2000 servers external IPs). The ISA DNS servers perform recursive lookups for the internal DNS servers. I've successfully published RDP and other network services through ISA 2004, but I can't seem to publish any of our IIS-based websites (I haven't tried the apache one yet). Using a combo of Ethereal and ISA 2004's monitoring I think I've established that no traffic is received by the web listener - DNS queries for the website point to the ISA 2004 external IP & the server can reslove internal and external DNS via the command line, (plus other external to internal rules work) so I don't think DNS is the problem. I'm running Server 2003 R2 SP1 and ISA 2004 SP 2. The web publishing rule is set up to send the original host header to IIS via the webserver's FQDN, listening on port 80, external network, all users, with integrated authentication at the listener. I've also tried it with no authentication at all.... The site is available internally, but its "page cannot be displayed" externally... Anyone see what I'm missing?

Just though I'd let you know, the problem was DNS, I've installed it on the server, set it to transfer zones from the master external (network) DNS server & bingo, problem solved. Thanks for all the advice!

Sorry PiqueABoo, not really sure what you're telling me - I hadn't actually heard of PMTU until today...

Thanks for that Geoff, not sure I'll bother with PMTU after all - I think the problem lies with either external DNS, the rule I've created or perhaps the build (hotfixes). I've only been working in IT for 17 months & have a lot to learn... Might be a dumb question but our GP for IE proxy settings has HTTP traffic (and the rest) on port 8080 - the default port for ISA's HTTP filter is 80, do I have to create a new protocol for port 8080 traffic?

Thanks Ash, I've applied SP2 but I need to check if all post SP2 fixes have been applied. The test server is a member of the domain, using internal DNS - I've enabled internal DNS to the ISA server in the system rules. But I don't think I created a rule to allow internal DNS to external networks - isn't this a security risk? Thanks for the heads-up about PMTU and the best practise analyser, I'll look at these when I get back to work on Monday.

The PC I'm testing ISA on is a ordinary base unit - AMD 3200 X2 with beefed-up RAM (2 Gig), 2 gigabyte NICs & an 80 gig SATA drive. The reason I'm using 2004 is it was originally purchased before 2006 came out.

First of all, a big hello! As you can tell I'm new here & this is my first post. Sorry it's so long... I'm currently testing ISA 2004 on server 2003 R2 to act as a proxy, cache & firewall but I've run into a problem. External web pages are occasionally extremely slow to appear, that is, the same site can sometimes arrive almost straight away and sometimes sites don't appear until you refresh or click again on a link. I use major sites such as Google and the BBC to test access, clearing the cache, cookies and off-line files on the test client each time. When I make a change to ISA I restart the firewall service to give me a new connection. My access rule is: Allow Protocols: HTTP, HTTPS All users All the time Internal to External networks standard Caching is enabled on the server. When I use an "allow all outbound traffic" rule I do not encounter this problem. I'm stumped - does anyone see what I'm missing?