Search results for query: *

Wesley, Okay I went through the prescribed steps and still have the same problem. I can reach the website from the DNS/Server machine, but not from the clients. Could it be something with DHCP server or what? Craig

Wesley, That helps, except for one thing. I am utilizing our server, and we only have one, as the name server. If I change the forward lookup zone to the internal address, it does not resolve correctly for external clients. Do you have this same type of setup? Craig

No. Don't even have a clue what it is. I use the Windows 2000 login script option and then utilize a batch file on the SYSVOL to set time and map all of the drives to shares.

I do run login scripts, however, here is the issue that I would have with that. We run every version of Windows from 98 on and it appears that the hosts file is located differently on each version of windows. Is there a way to write the script line to cover all versions of windows???

I will look at the external port allowing access to port 80. I'm not sure or that experienced on that. It definitely allows the traffic through. I can update the local hosts file, I was just hoping there was some automated way to do that, incase we add some new websites, etc. We only have...

No. Gives me a Could not open a connection to host on port 80: Connect Failed

I can ping the external address of the firewall. The firewall is a Watchguard Firebox. I'm pulling my hair out trying to figure this out. Anyone please help

Rory, Here is the problem when I do that, the outside world cannot view our website. We are utilizing our computer as the name server for the website, therefore, when I change the forward lookup, outside clients resolve to the internal address and not the external. Am I missing something here?

I'm not sure if it is the same problem. I am using DHCP and am sending DNS, Name Server, Domain to the clients and the network works great. The problem is that the forward lookup zone for www points to our external address. This address, when viewed from the inside does resolves to the...

Alright, here is the problem. We have a Windows 2000 network setup to host our email and website. DNS has been set up as the primary name server for the network and all is well with external clients. Internally, the name get's resolved to our public IP address and comes up with a "This...