• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Webserver Problems

H

Hoober

Diamond Member
I'm running Windows 2000 server and a basic website. Just trying to learn DNS and IIS and everything else. Anyway, the server is behind a router with all ports forwarded correctly. Its on a private IP with the rest of the internal network. Computers outside of the internal network can see the domain just fine and don't have any problems connecting to it. Computers on the network, however, can't pull up the domain. They see the server just fine, log into the domain just fine, but you can't browse to the website, ftp, anything. File transfers to and from the server work great and are very speedy.

Something with DNS?
 
The internal computers r using that server as a DNS? and u which entry u have in the DNS for the web and ftp sites?
 
sounds like a DNS server issue on the internal hosts..

what are they using for a DNS server?

my network is setup so the internal hosts use @homes DNS servers...
 
Yeah, the internal computers are using the server for DNS. Otherwise they can't find the server to log into the domain and load profiles, files, those sorts of things.
 
can you connect to http://192.whatever directly and pull up the web page served there? I'm trying to understand the prob, is it just when you access http://yourdomain.com that it doesnt work or does it not work at all in tcp/ip internally? (i.e. ftp/http directly to ip.address.of.server)

have u tried setting a route to the domain in the lmhosts file, bypassing your dns server?
 


<< I'm running Windows 2000 server and a basic website. Just trying to learn DNS and IIS and everything else. Anyway, the server is behind a router with all ports forwarded correctly. Its on a private IP with the rest of the internal network. Computers outside of the internal network can see the domain just fine and don't have any problems connecting to it. Computers on the network, however, can't pull up the domain. They see the server just fine, log into the domain just fine, but you can't browse to the website, ftp, anything. File transfers to and from the server work great and are very speedy.

Something with DNS? >>



The problem is that your win2k's IP address is 192.168.xxx.xxx inside the network. You computers access DNS server outside your network and it gaves them IP address of your router. Router forwardes all requests from outside to win2k machine, but it doesn't do that from the inside. There are 3 solutions:

1. Set forwarding al unknown DNS requests to IP address of router on win2k box. Set IP address of DNS server on every machine to IP address of win2k. So, when computers are trying to access the internet they will ask win2k for IP adresses, win2k will forward this to router and router will answer. If computers will access win2k, win2k will reply with correct own IP adress.

2. Simply add IP adresss to local DNS entries of each computer. So, if your win2k domain name is foo.com and it's IP is 192.168.1.100
a) on Windows 98 add next 2 lines to c:\windows\hosts (look for c:\windows\hosts.sam for example)
192.168.1.100 www.foo.com
192.168.1.100 foo.com

a) on Windows 2000 add next 2 lines to c:\winnt\system32\drivers\etc\hosts
192.168.1.100 www.foo.com
192.168.1.100 foo.com

3. Don't to anything. You can access website using it's IP address (say http://192.168.1.100) or it's NetBIOS (say your win2k's box appears as win2k in network neighborhood, then type http://win2k )
 
Just add the ip address of the DNS servers of ur ISP as forwarders and give to the clients the ip address of ur internal DNS.
 
Thanks for your help, I appreciate it.

I've already got forwarders set up on the DNS server under 2k. DNS port is forwarded through the router, as is webserver port. The internal IP of the DNS server is hardcoded into the DNS server search order on both of the XP professional boxes running on the LAN. They find the webpage just fine when you type in the internal IP address of the server. Both of the boxes also connect instantly when you type in the public IP of the website. I have the forwarders set to the DNS server at work and the external IP of my network. Still no go, however, when you simply type in www.hoobersempire.com in the browser.
 
I have the domain under forward lookup, but not a record for the www. What sort of record is that? If I right click and hit "new," I don't see anything for www or anything like. Course Microsoft wouldn't make it that easy or else we'd all have lots of certs. Where would I put the record for the website?
 
Ok, 1st u need a foward lookup and a reverse lookup zones, after that in the foward lookup zone in the domain right-click and select an
A record, in the host name u r gonna type "www" and in the ip address the ip that u what for the site and be sure u mark the for box for
create the pointer.

Good Luck
 
Was out to dinner 🙂

Anyway, by A record do you mean Alias record? And if so, there isn't any "pointer" box to check. Just alias name and "fully qualified name for record"
 
Holy Moley, its works like charm now! Thanks!

One more question... the reverse lookup zone... I created the A record before the reverse lookup. For the reverse lookup I created the 216.226.45.x subnet because that's what the external IP address of the domain is. Is that correct? Or should I have done the private range coming from the DHCP server (router)?
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top