Solved

2003 Standard Server and Netgear FVS318 Router

Posted on 2006-11-18
3
398 Views
Last Modified: 2013-11-29
I have a client who changed out his Netgear router yesterday. He finally got it working with the server but went in and changed around the DHCP settings and Server IP settings. Now he stated that clients take a long time to login. From what I gathered he probably does not have DNS setup correctly and DHCP. Here is his setup:

Roadrunner Business Class modem with staic IP | FVS 318 Router | 2003 Standard Server | Switch | Clients

My plan for this morning:

1) Login to Router and check / correct ISP settings / Set Router IP to same subnet as Network 192.168.2.X / Disable DHCP
2) Set static IP on Server to: (IP) 192.168.2.X / (Subnet) 255.255.255.0 / (Gateway) Router IP / (DNS) Server IP
3) Check and adjust DHCP scope
4) Setup DNS forwarders to ISP DNS servers.

Is there anything I am missing here?
0
Comment
Question by:flteng56
  • 2
3 Comments
 
LVL 77

Accepted Solution

by:
Rob Williams earned 500 total points
ID: 17971317
I suspect if you run through your list you will resolve the problem. Slow logons are most often caused by DNS on the workstation pointing to the ISP's DNS, even as a secondary when the primary is the internal DNS server. I'll post my DNS "checklist" below for you to review, but you have covered most of it.

Assuming you have completed the server installation, installed Active Directory, and joined the workstations to the Domain, make sure DNS is configured as follows, assuming a single network adapter:
-The server's NIC should be configured with a static IP, the Internet router as the gateway, and only the server itself as the DNS server. Do not use an ISP DNS server here
-Each workstation should be configured using DHCP (obtain and IP address and DNS automatically) or if configured with static addresses; a static IP in the same subnet as the server, same subnet mask as the server, the gateway pointing to your Internet router, and the DNS server pointing ONLY to the server/domain controller. Again do not put an ISP's DNS server here
-In the DNS management console under Administrative tools, right click on the server name and choose properties. On the Forwarders tab add your ISP's DNS servers
-If the workstations are using DHCP, open the DHCP management console on the server under Administrative tools and click on the server name to expand it, click on the scope to expand it, right click on scope options and choose configure options. On the general tab add the Internet router's IP in #003 router, the server's IP in #006 DNS Servers, and the domain name and suffix under #015 such as mydomain.local
-If  DHCP is enabled on the router, rather than the server, it should really be disabled on the router and configured on the server. Enabling DHCP on the server assists with dynamic updates to DNS, allows for central management, and far more scope options.
-The DHCP client service should be running on servers and workstations even where you are not using DHCP assignments. The DHCP client service controls the dynamic DNS updates

If you have been having DNS problems, on the workstations that have been having problems you should clear the DNS cache by entering at a command line  
  ipconfig  /flushdns
and then
  ipconfig  /registerdns

This should help with the slow logons. If you have the ISP's DNS's anywhere in the NIC's, the workstations will often go to the Internet to try to resolve names and cause them to "hang".
0
 

Author Comment

by:flteng56
ID: 17972338
Thanks for the solution. It worked like a charm!
0
 
LVL 77

Expert Comment

by:Rob Williams
ID: 17972381
Great, glad to hear. Thanks flteng56,
--Rob
0

Featured Post

What Should I Do With This Threat Intelligence?

Are you wondering if you actually need threat intelligence? The answer is yes. We explain the basics for creating useful threat intelligence.

Join & Write a Comment

Suggested Solutions

Short answer to this question: there is no effective WiFi manager in iOS devices as seen in Windows WiFi or Macbook OSx WiFi management, but this article will try and provide some amicable solutions to better suite your needs.
BIND is the most widely used Name Server. A Name Server is the one that translates a site name to it's IP address. There is a new bug in BIND (https://kb.isc.org/article/AA-01272), affecting all versions of BIND 9 from BIND 9.1.0 (inclusive) thro…
Viewers will learn how to connect to a wireless network using the network security key. They will also learn how to access the IP address and DNS server for connections that must be done manually. After setting up a router, find the network security…
In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're interested in additional methods for monitoring bandwidt…

705 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

17 Experts available now in Live!

Get 1:1 Help Now