Bit of a strange one this. Installed ISA onto a clean W2K server, got everything working (web, nntp, smtp etc) for the client machines and then ran the VPN wizard to let myself connect into the network from home.
Our internal network range is 192.168.0.1 -> 192.168.0.255. All of our internal machines are in the first 100 ip addresses, I set up the routing and remote access on the isa machine to allocate .250 -> .255 to external clients.
The problem that is occuring is that if I ping isaserver from certain machines I get 192.168.0.203, which is correct, but from other machines I get 192.168.0.250. All internal clients are W2K.
Obviously this is causing a problem for the Firewall Client as typing in ISASERVER into the server location causes it to fail as it is looking at .250.... or something.
Can someone with more experience of this sort of thing give me a push in the right direction as I think I am just p1ss1ng in the wind at the moment. ;o)
quote:Originally posted by TimCampbell: On the clients showing .250 for the isaserver, try running nslookup for isaserver. Watch the dns server it is connected to, and if it comes back with the .203, try an ipconfig /flushdns.
Good luck. Tim C.
Thanks Tim, I'll give it a try. Would DNS problems like this cause everything to slow down to a crawl aswell? <dave crosses fingers!>
From: Pinellas Park, FL
DNS can create all kinds of problems. However, slow connections to the same site would point to a different problem (Cache maybe), once the DNS is resolved, it is saved for a short while to reduce network traffic on return calls to the same domain. If all external sites are slow, I'd look at routing or gefault gateways.