Re: Intermittently Companyweb access fails
- From: "Lanwench [MVP - Exchange]" <lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 25 Oct 2006 11:53:24 -0400
In news:359674D6-BE93-4DB8-9F80-F128D2D0E470@xxxxxxxxxxxxx,
Tom Morris <tomm+@+onbcom+com> typed:
Actually if the change fixes the problem then I suspect the first
client DNS query timed-out -
Perhaps the SBS box was busy.
CompanyWeb is a slow loader - and the
client forwarded the request to the second DNS server for resolution.
Bu the page wouldn't have started loading at that point.....only *after*
the name had been resolved.
The issue is the client request that moves to the second DNS server;
there is not a specfic configuration issue. SBS Server is not aware
of a second DNS server on the client desktops.
Nor should it be. Get rid of the 2nd, and you should be good to go.
Thanks for the help. Hope it works.
Tom
"Lanwench [MVP - Exchange]" wrote:
In news:06B893B9-8999-4435-A97C-90B5DE2408F0@xxxxxxxxxxxxx,
Tom Morris <tomm+@+onbcom+com> typed:
Question: why does a named secondary DNS server cause resolution
problems for http:\\companyweb?
Because your internal AD relies on DNS for proper functionality. Your
router's built-in DNS cache will not know what to do with
"companyweb" - nor will your ISP's DNS servers. AD requires that
*only* internal (AD-integrated, in this case) DNS servers be
specified - and your SBS box's DNS server will use forwarders or
root hints to resolve external names.
DHCP changes underway. This inherited network has several
non-optimum configurations however I don't believe Static IP/DHCP
configurations play into the current problem unless I am missing
something?
No, but they make it a heck of a lot harder to fix in one fell swoop.
Thanks,
Tom
"Lanwench [MVP - Exchange]" wrote:
In news:F59AB9F1-09CD-4E62-830B-F172D59D3D7D@xxxxxxxxxxxxx,
Tom Morris <tomm+@+onbcom+com> typed:
Per request, IPConfig /all output
Windows IP Configuration
Host Name . . . . . . . . . . . . : julie-desktop
Primary Dns Suffix . . . . . . . : ALZWA.LOCAL
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : ALZWA.LOCAL
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139 Family
PCI Fast Ethernet NIC
Physical Address. . . . . . . . . : 00-11-D8-B5-12-12
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.30
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.150
192.168.1.1
Remove this last entry. All your workstations, and your server(s),
should specify only 192.168.1.150 (the SBS box's LAN IP, right? )
for DNS. AD does not work properly without DNS running
properly.....
Why aren't you using DHCP? It's so much easier. I'd set it up on
the SBS box - for 192.168.1.1 through .254, with exclusions set up.
Personally, I assign servers and other statics, within the .1 - .50
range, and exclude that from the scope - and also exclude .200 -
.254. Using a static server IP address in the middle of your
network as you're doing, is a little awkward. Not unworkable, but
awkward. If it were my network, I'd change the server's IP (use
the wizard for that....) to something lower.
Primary WINS Server . . . . . . . : 192.168.1.150
"Lanwench [MVP - Exchange]" wrote:
In news:736FAC76-59C3-4DBF-B677-A3A7542B3568@xxxxxxxxxxxxx,
Tom Morris <tomm+@+onbcom+com> typed:
Intermittently, apparently randomly, a user receives the browser
message "this page cannot be displayed" when opening
http:\\companyweb. Other users simultaneously can access the
site; all users are internal. And sometime later the user
experiencing the access problem will be able to access the
problem.
When the users experiences the problem I am able to perform
NSLookup, Ping, etc. from their desktop comptuer.
Any help appreciated.
Thank,
Tom
Post an ipconfig /all from a problem workstation.
.
- References:
- Re: Intermittently Companyweb access fails
- From: Lanwench [MVP - Exchange]
- Re: Intermittently Companyweb access fails
- From: Lanwench [MVP - Exchange]
- Re: Intermittently Companyweb access fails
- From: Tom Morris
- Re: Intermittently Companyweb access fails
- From: Lanwench [MVP - Exchange]
- Re: Intermittently Companyweb access fails
- From: Tom Morris
- Re: Intermittently Companyweb access fails
- Prev by Date: Re: WMI Problems
- Next by Date: Moving SBS Folders
- Previous by thread: Re: Intermittently Companyweb access fails
- Next by thread: Max Number of VPN's
- Index(es):
Relevant Pages
|
Loading