Hi,
We've got an Win2003/ISA2004 VPN server for external users to connect to.
This VPN server doesn't allow any other services, we have a separate ISA server which acts as a firewall/proxy/publishing for the whole network. This FW server is not a member of any domain, the VPN server is a member of the default (only) domain.
The problem is, about a couple of weeks ago, users (who all use XP) connecting over VPN started complaining that they were unable to browse the network or resolve any computer names (unless they already had network places mapped). Some people are also experience total or intermittent issues browsing the web through the VPN.
We have automatic updates set on the Win2003 servers and the XP clients. I think it's something to do with an update on either the DCs or the XP clients - a kerberos/dns issue? We have 3 DCs, two of which are DNS servers. It was all working fine up until a couple of weeks ago!!
Any ideas?
We've got an Win2003/ISA2004 VPN server for external users to connect to.
This VPN server doesn't allow any other services, we have a separate ISA server which acts as a firewall/proxy/publishing for the whole network. This FW server is not a member of any domain, the VPN server is a member of the default (only) domain.
The problem is, about a couple of weeks ago, users (who all use XP) connecting over VPN started complaining that they were unable to browse the network or resolve any computer names (unless they already had network places mapped). Some people are also experience total or intermittent issues browsing the web through the VPN.
We have automatic updates set on the Win2003 servers and the XP clients. I think it's something to do with an update on either the DCs or the XP clients - a kerberos/dns issue? We have 3 DCs, two of which are DNS servers. It was all working fine up until a couple of weeks ago!!
Any ideas?
