Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Re: Clients have to refresh web pages to see them

7 views
Skip to first unread message

Marina Roos [SBS-MVP]

unread,
Aug 8, 2004, 5:00:44 PM8/8/04
to
Hi Doug,

So you aren't using 2 nics in the server?

--
Regards,

Marina
Microsoft SBS-MVP

"Doug" <Do...@discussions.microsoft.com> schreef in bericht
news:9B8C4887-18B9-4423...@microsoft.com...
> Hi,
>
> Im wondering if anyone knows how to resolve the DNS problem where web
pages
> timeout, and then appear once the user performs a page refresh.
>
> NSLOOKUP is fine, etc. The DNS Monitor's test is fine, etc.
>
> All my clients point to the 2k3 server as their DNS server. Their gateway
> is our firewall router. Our firewall router has a static IP and three DNS
IP
> addresses installed (Adding the DNS IPs was required by the linksys setup,
I
> guess I could try using an internal DNS server IP?). I just mention the
> gateway here to convey our topology. The firewall's DNS port is blocked
(I
> tried directing that port to the 2k3 server to no avail).
>
> The server's DNS server is the server, and I have tried having no
forwarders
> and various ISP-provided DNS IPs listed as forwarders with no change in
> behavior. The server's gateway is the firewall, just as the clients' are.
>
> The DNS monitor tab's test runs succesfully.
>
> Any ideas?


SuperGumby [SBS MVP]

unread,
Aug 8, 2004, 5:33:59 PM8/8/04
to

Doug

unread,
Aug 9, 2004, 7:21:05 AM8/9/04
to
No, just one NIC card. I have read problems on this news group where people
have had multiple nic cards, but unfortunately that wasn't my case.


"Marina Roos [SBS-MVP]" <mar...@roos.nodontwantspam.nl.com> wrote in message
news:eNxQHrYf...@TK2MSFTNGP09.phx.gbl...

Doug

unread,
Aug 9, 2004, 7:36:13 AM8/9/04
to
That sound promising. I have a linksys router that I recently upgraded
firmware in (linksys is cisco, which I guess is one of the problematic
routers with 512 bytes).

I did this on the server:
dnscmd /Config /EnableEDnsProbes 0
but it didn't really change anything. Should I reboot after doing that?

I also recently switched us to a static IP. Do you folks have static IPs
for your WAN? When you configure your firewall router with the static IP,
what did you put for your DNS entries? Im wondering since my router is
neither the DHCP server nor the DNS server why it would care about DNS
entries?

"SuperGumby [SBS MVP]" <n...@your.nellie> wrote in message
news:OYOIs9Yf...@TK2MSFTNGP12.phx.gbl...

SuperGumby [SBS MVP]

unread,
Aug 9, 2004, 9:53:31 AM8/9/04
to
I'm unsure whether the EDNS0 fix requires a restart. Easy fix: if you've
executed the command and are still experiencing problems, restart. (I am
SOOOOOO a GENIUS) [or maybe restart the DNS server after "ipconfig
/flushdns"]

Having a static IP on your external interface is desirable but not
necessary. Actually, having a static public IP is only desirable if you want
to let someone from the internet connect to your server. Having a static IP
between your server and the router which connects it to the internet is
considered a good idea. If you have no intention of making services
available to internet users you are BETTER OFF with a dynamic public IP.


"Doug" <nos...@nospam.com> wrote in message
news:%23WhEUTh...@tk2msftngp13.phx.gbl...

Marina Roos [SBS-MVP]

unread,
Aug 9, 2004, 9:54:26 AM8/9/04
to
Hi Doug,

Check out www.smallbizserver.net, network.

--
Regards,

Marina
Microsoft SBS-MVP

"Doug" <nos...@nospam.com> schreef in bericht
news:%23WhEUTh...@tk2msftngp13.phx.gbl...

Joe

unread,
Aug 9, 2004, 2:46:59 PM8/9/04
to
In message <eGFYDhhf...@TK2MSFTNGP11.phx.gbl>, "SuperGumby [SBS
MVP]" <n...@your.nellie> writes

>
>Having a static IP on your external interface is desirable but not
>necessary. Actually, having a static public IP is only desirable if you want
>to let someone from the internet connect to your server. Having a static IP
>between your server and the router which connects it to the internet is
>considered a good idea. If you have no intention of making services
>available to internet users you are BETTER OFF with a dynamic public IP.
>
Unless, of course, you want to send email. A number of large ISPs (e.g.
AOL) don't talk to mail servers on dynamic IPs. If you're on a dynamic
IP, you must either have access to an external smarthost or use webmail.
--
Joe

Doug

unread,
Aug 9, 2004, 9:34:16 AM8/9/04
to
I tried that, but it didn't do any good.

I am at an end here. Im just not sure what to do. For now, I removed all
the DNS forwarders on the server configuration, I closed the DNS port on the
firewall, I rebooted the server. I also removed the DNS settings in the
router (not sure why it ever wanted any).

So theoretically, the server is providing all the DNS info in this
configuration, correct? What would cause the hiccups?


"SuperGumby [SBS MVP]" <n...@your.nellie> wrote in message
news:OYOIs9Yf...@TK2MSFTNGP12.phx.gbl...

Doug

unread,
Aug 9, 2004, 9:40:14 AM8/9/04
to
Just a followup:

I am about to give up. I get no DNS events on the server's logs to help me
figure this out.

I did the following:
1) I closed the DNS port in the firewall router, and disabled any DNS IPs
set in the firewall router
2) I removed all DNS forwarders on the server.
3) The 2k3 server's DNS server is itself. It listens on any ip address for
DNS queries.
4) All clients have the 2k3 server as their DNS server.

Now this should make the server a standalone DNS provider for our network,
right? If this is the case, what can cause these hiccups where we have to
refresh our browsers?

"Doug" <nos...@nospam.com> wrote in message
news:%23WhEUTh...@tk2msftngp13.phx.gbl...

SuperGumby [SBS MVP]

unread,
Aug 11, 2004, 6:52:02 PM8/11/04
to
' I closed the DNS port on the firewall' - how? Routers allow you to open it
incoming but this has no effect on outgoing requests, not all routers allow
you to easily close outgoing. It's a non issue though, by removing the
forwarders on SBS you cause DNS to use 'root hints' and unless you've
removed the root servers, not a good idea, anything SBS can't answer it will
look up.

Put the ISP's DNS back into the router, or allow the router to use DHCP,
whichever is correct for your ISP. The problem may be your ISP's DNS, try
another maybe.

You might try running the internet wizard and telling it to use the router
for DNS.


"Doug" <nos...@nospam.com> wrote in message

news:O34h%2398fE...@TK2MSFTNGP10.phx.gbl...

0 new messages