Why can't I reach my own website - Router issues?

[ksumner]

1. I have a linksys wireless router at work that is attached to our firewall (or is it our cisco router) for internet connection. users are able to open most sites, but cannot open our own website. It seems anything to do with our domain "the server cannot be found". Yet connecting any other way is fine. Are we somehow blocking our own domain? If so, where do i look to make the change on the linksys router/firewall or our cisco router?

2. The linksys router is obviously not a business wireless solution. What should i consider in extending out wireless connectivity throughout the entire office instead of its limited reach?

k.SUMNER

 

[Beowulf005]

1. Is the router performing the DHCP service or your server? You need to make sure that the clients are using a dns service within you network otherwise the dns request will not recoigze your internal network.

When frustrated remember, in the computer world there is almost always a backdoor.

 

[ksumner]

the wireless router is providing the DHCP service. so what exactly should i do for client machines?

k.SUMNER

 

[Beowulf005]

Whats happening is the wireless router is sending the dns request towards you ISP and that why ouside sites are working. But when you try to connect to you internal site the ISP dns dosn't know it. Have you tried to browse by the IP address of the server its running on? IF this works its diffently an dns issue (unless you are running multi sites on server)

Typically what needs to happen you need to move the DHCP service to the server. Make the scope see the server as the dns server for the clients and then configure the dns server to foward unknown requests to your ISP dns

When frustrated remember, in the computer world there is almost always a backdoor.

 

[dput]

Aren't we really discussing the DNS service? Not the DHCP service? Just to try and clarify for those reading.

Dan

 

[Beowulf005]

The DHCP service is what maps the clients pcs to the correct server. If the router is the DHCP it will send all requests to the ISP dns. If the server is the DHCP it will handle the dns requests, thus reponding to dns inquiries to address it own.

Example
Server has a website running with the hostheader of "companyweb"

The network is designed as Modem--Router--All clients and Server

When the Router acts as the DHCP server when a client pc request a IP the router will usally assign
IP 192.168.x.x
Sub 255.255.255.0
Gateway 192.168.1.1(router address)
DNS 192.168.1.1(router address)

Thus when the client pc types in a url of "companyweb" the router doesn't know that name so it sends the request thru the modem to the ISP.

Now when the server is the dns server all connecting clients will get Ip's assigned something like
IP 192.168.x.x
Sub 255.255.255.0
Gateway 192.168.1.1(router address)
DNS 192.168.1.100 (server address0

Now when the client pc types in a url of "companyweb" ther server has that listed in its dns records as a site it is running and will display the site.

Hope this helps

When frustrated remember, in the computer world there is almost always a backdoor.