| Home | Register | Members | Search | Windows Vista Tips | File Database | Links |
 |
| Thread Tools | Display Modes |
|
Guest
Posts: n/a
|
|
|
|
||
|
|
| |
|
Guest
Posts: n/a
|
|
|
|
|
||
|
Guest
Posts: n/a
|
|
|
|
|
||
|
Guest
Posts: n/a
|
|
|
|
|
||
|
Guest
Posts: n/a
|
|
|
|
|
||
|
Guest
Posts: n/a
|
|
|
|
|
||
|
Guest
Posts: n/a
|
Your PC's won't get (or need to be set) to static IP's. The SBS DHCP
server will do the job. As others have recommended, I think you'll find everything will operate nicely if you do things the SBS way  -- Duncan. In article <6F00A09D-0AE1-4EF7-9224->, gjb957 @msn.com says... > > This is a small office and the router was here before the server. The SBS > serves as a file server and AD controller for security. It is not serving > exchange or SQL or any other SBS features (at the time of purchase SBS w/ 5 > CALs was cheaper than standard server). Would it make a difference in > performance if a client is not using DHCP and has a static IP? > > This is from one that is using DHCP: > X:\>ipconfig /all > > Windows IP Configuration > > Host Name . . . . . . . . . . . . : PC05 > Primary Dns Suffix . . . . . . . : JJB.local > Node Type . . . . . . . . . . . . : Hybrid > IP Routing Enabled. . . . . . . . : No > WINS Proxy Enabled. . . . . . . . : No > DNS Suffix Search List. . . . . . : JJB.local > RP614v4 > > Ethernet adapter Local Area Connection: > > Connection-specific DNS Suffix . : RP614v4 > Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit > Ethernet > Physical Address. . . . . . . . . : 00-1C-C4-91-C0-BF > Dhcp Enabled. . . . . . . . . . . : Yes > Autoconfiguration Enabled . . . . : Yes > IP Address. . . . . . . . . . . . : 192.168.1.57 > Subnet Mask . . . . . . . . . . . : 255.255.255.0 > Default Gateway . . . . . . . . . : 192.168.1.1 > DHCP Server . . . . . . . . . . . : 192.168.1.1 > DNS Servers . . . . . . . . . . . : 192.168.1.1 > Lease Obtained. . . . . . . . . . : Friday, November 13, 2009 > 7:58:18 AM > > Lease Expires . . . . . . . . . . : Saturday, November 14, 2009 > 7:58:18 AM > > > > > "SteveB" <> wrote in message > news:... > > SBS and its workstation clients are much happier if it runs DHCP and not > > the router. Why are you using DHCP on the router? > > > > Post an ipconfig /all from the server and workstations. > > > > You should also run the SBS BPA to see if it finds any problems. > > > > "gerald B." <> wrote in message > > news:7DB4958A-CC46-4C85-AAD2-... > >> I'm experiencing a situation on a small network in an office I support. > >> This has been an ongoing problem but just recently brought to my > >> attention. > >> Server: SBS 2003 > >> Clients: 3 XP pro & 3 Vista Pro > >> All are up to date on service packs. > >> DHCP from a Netgear Router for 4 of the workstations, 2 have static IPs > >> AVG 9 (problem existed before this was loaded) > >> > >> When a user goes to login, it can take several minutes to get to the > >> desktop. I remember reading about this a while ago and it being related > >> to an network issue. But I can't seam to find anything on it. These > >> systems are virus free. One machine is brand new out of the box only a > >> week. > >> > >> Has anyone seen this before? > >> > >> -------- > >> gerald > >> > >> > >> > >> > > > > |
|
|
|
|
|||
|
Guest
Posts: n/a
|
Others have answered, but haven't really explained the "why." If you look at your IP config below, you'll see that your DHCP server is 192.168.1.1. Your DNS server is *also* 192.168.1.1. This means that your client machines are asking your router for DNS data. This is all well and good for internet addresses. Your netgear can look up an A record for www.microsoft.com just fine. So once you are on, you don't notice anything. During logon, however, many DNS requests are made about various server services. The client asks which AD server is closest, which server is a global catalog server, and some other queries. Your netgear router has NONE of these answers so DNS queries fail here. Your clients have to initiate the search via broadcast discovery which takes MUCH longer than DNS. So you root problem is that your DHCP server is setting your DNS servers incorrectly. Now, in theory, you could fix this by going into the Netgear firmware and configuring it to give your clients the SBS server as DNS servers. You'd also have to go to your machines with static IPs and change their DNS server. SBS has all of those DNS records that AD uses for speedy logons so whether static or DHCP, that is the DNS server that should be listed in your clients' IPConfig. In practice, however, this is a serious pain to maintain static clients, a DHCP server on one device, and DNS on SBS. Moving DHCP to the SBS server (a very easy process) resolves all of this. SBS, by default, *knows* it should be the DNS server so its DHCP server is properly configured to do this out of the box. SBS's DHCP server supports reservations by MAC address, so your static clients...if for some reason you need assurance that they always have the same IP (usually required for shared printers, etc) can be done as well, but still allows you to make changes such as DNS servers on *just* the DHCP server and that propogates to all machines including your "reserved IP" machines. It may seem like a bit more up-front work, but long-term maintenance is *GREATLY* reduced. So take the advice given by many othrers and move DHCP to the SBS server. -Cliff "gerald B." <> wrote in message news:6F00A09D-0AE1-4EF7-9224-... > This is a small office and the router was here before the server. The SBS > serves as a file server and AD controller for security. It is not serving > exchange or SQL or any other SBS features (at the time of purchase SBS w/ > 5 CALs was cheaper than standard server). Would it make a difference in > performance if a client is not using DHCP and has a static IP? > > This is from one that is using DHCP: > X:\>ipconfig /all > > Windows IP Configuration > > Host Name . . . . . . . . . . . . : PC05 > Primary Dns Suffix . . . . . . . : JJB.local > Node Type . . . . . . . . . . . . : Hybrid > IP Routing Enabled. . . . . . . . : No > WINS Proxy Enabled. . . . . . . . : No > DNS Suffix Search List. . . . . . : JJB.local > RP614v4 > > Ethernet adapter Local Area Connection: > > Connection-specific DNS Suffix . : RP614v4 > Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit > Ethernet > Physical Address. . . . . . . . . : 00-1C-C4-91-C0-BF > Dhcp Enabled. . . . . . . . . . . : Yes > Autoconfiguration Enabled . . . . : Yes > IP Address. . . . . . . . . . . . : 192.168.1.57 > Subnet Mask . . . . . . . . . . . : 255.255.255.0 > Default Gateway . . . . . . . . . : 192.168.1.1 > DHCP Server . . . . . . . . . . . : 192.168.1.1 > DNS Servers . . . . . . . . . . . : 192.168.1.1 > Lease Obtained. . . . . . . . . . : Friday, November 13, 2009 > 7:58:18 AM > > Lease Expires . . . . . . . . . . : Saturday, November 14, 2009 > 7:58:18 AM > > > > > "SteveB" <> wrote in message > news:... >> SBS and its workstation clients are much happier if it runs DHCP and not >> the router. Why are you using DHCP on the router? >> >> Post an ipconfig /all from the server and workstations. >> >> You should also run the SBS BPA to see if it finds any problems. >> >> "gerald B." <> wrote in message >> news:7DB4958A-CC46-4C85-AAD2-... >>> I'm experiencing a situation on a small network in an office I support. >>> This has been an ongoing problem but just recently brought to my >>> attention. >>> Server: SBS 2003 >>> Clients: 3 XP pro & 3 Vista Pro >>> All are up to date on service packs. >>> DHCP from a Netgear Router for 4 of the workstations, 2 have static IPs >>> AVG 9 (problem existed before this was loaded) >>> >>> When a user goes to login, it can take several minutes to get to the >>> desktop. I remember reading about this a while ago and it being related >>> to an network issue. But I can't seam to find anything on it. These >>> systems are virus free. One machine is brand new out of the box only a >>> week. >>> >>> Has anyone seen this before? >>> >>> -------- >>> gerald >>> >>> >>> >>> >> >> |
|
|
|
|
|||
|
Guest
Posts: n/a
|
"Cliff Galiher" <> wrote in message
news:O%... > Others have answered, but haven't really explained the "why." If you look > at your IP config below, you'll see that your DHCP server is 192.168.1.1. > Your DNS server is *also* 192.168.1.1. This means that your client > machines are asking your router for DNS data. > > This is all well and good for internet addresses. Your netgear can look > up an A record for www.microsoft.com just fine. So once you are on, you > don't notice anything. > > During logon, however, many DNS requests are made about various server > services. The client asks which AD server is closest, which server is a > global catalog server, and some other queries. Your netgear router has > NONE of these answers so DNS queries fail here. Your clients have to > initiate the search via broadcast discovery which takes MUCH longer than > DNS. So you root problem is that your DHCP server is setting your DNS > servers incorrectly. > > Now, in theory, you could fix this by going into the Netgear firmware and > configuring it to give your clients the SBS server as DNS servers. You'd > also have to go to your machines with static IPs and change their DNS > server. SBS has all of those DNS records that AD uses for speedy logons > so whether static or DHCP, that is the DNS server that should be listed in > your clients' IPConfig. > > In practice, however, this is a serious pain to maintain static clients, a > DHCP server on one device, and DNS on SBS. Moving DHCP to the SBS server > (a very easy process) resolves all of this. SBS, by default, *knows* it > should be the DNS server so its DHCP server is properly configured to do > this out of the box. SBS's DHCP server supports reservations by MAC > address, so your static clients...if for some reason you need assurance > that they always have the same IP (usually required for shared printers, > etc) can be done as well, but still allows you to make changes such as DNS > servers on *just* the DHCP server and that propogates to all machines > including your "reserved IP" machines. It may seem like a bit more > up-front work, but long-term maintenance is *GREATLY* reduced. > > So take the advice given by many othrers and move DHCP to the SBS server. > > > -Cliff Just to add, which I don't think it was touched on, that the SBS must also only point to itself for its DNS address. Running the wizard should take care of this part anyway. Otherwise if the SBS is pointing elsewhere, such as the Netgear or the ISP's DNS, numerous errors will occur on the SBS. To Gerald: I also suggested is to create a Forwarder that will send outside queries to the ISP's DNS server. That's done in DNS server properties, Forwarders tab. Type in the ISP's DNS address. Do not use the Netgear as a DNS server. If not sure how to create a Forwarder, please read the following link with a how-to. HOW TO Configure DNS for Internet Access in Windows Server 2003 (including how to configure a Forwarder) : http://support.microsoft.com/?id=323380 Ace |
|
|
|
|
|||
|
Guest
Posts: n/a
|
And maybe a little more specifc to SBS 2003....
How to configure Internet access in Windows Small Business Server 2003 http://support.microsoft.com/kb/825763 -- Merv Porter [SBS-MVP] ============================ "Ace Fekay [MCT]" <> wrote in message news:uF3c$... > "Cliff Galiher" <> wrote in message > news:O%... >> Others have answered, but haven't really explained the "why." If you >> look at your IP config below, you'll see that your DHCP server is >> 192.168.1.1. Your DNS server is *also* 192.168.1.1. This means that your >> client machines are asking your router for DNS data. >> >> This is all well and good for internet addresses. Your netgear can look >> up an A record for www.microsoft.com just fine. So once you are on, you >> don't notice anything. >> >> During logon, however, many DNS requests are made about various server >> services. The client asks which AD server is closest, which server is a >> global catalog server, and some other queries. Your netgear router has >> NONE of these answers so DNS queries fail here. Your clients have to >> initiate the search via broadcast discovery which takes MUCH longer than >> DNS. So you root problem is that your DHCP server is setting your DNS >> servers incorrectly. >> >> Now, in theory, you could fix this by going into the Netgear firmware and >> configuring it to give your clients the SBS server as DNS servers. You'd >> also have to go to your machines with static IPs and change their DNS >> server. SBS has all of those DNS records that AD uses for speedy logons >> so whether static or DHCP, that is the DNS server that should be listed >> in your clients' IPConfig. >> >> In practice, however, this is a serious pain to maintain static clients, >> a DHCP server on one device, and DNS on SBS. Moving DHCP to the SBS >> server (a very easy process) resolves all of this. SBS, by default, >> *knows* it should be the DNS server so its DHCP server is properly >> configured to do this out of the box. SBS's DHCP server supports >> reservations by MAC address, so your static clients...if for some reason >> you need assurance that they always have the same IP (usually required >> for shared printers, etc) can be done as well, but still allows you to >> make changes such as DNS servers on *just* the DHCP server and that >> propogates to all machines including your "reserved IP" machines. It may >> seem like a bit more up-front work, but long-term maintenance is >> *GREATLY* reduced. >> >> So take the advice given by many othrers and move DHCP to the SBS server. >> >> >> -Cliff > > > Just to add, which I don't think it was touched on, that the SBS must also > only point to itself for its DNS address. Running the wizard should take > care of this part anyway. Otherwise if the SBS is pointing elsewhere, such > as the Netgear or the ISP's DNS, numerous errors will occur on the SBS. > > To Gerald: > > I also suggested is to create a Forwarder that will send outside queries > to the ISP's DNS server. That's done in DNS server properties, Forwarders > tab. Type in the ISP's DNS address. Do not use the Netgear as a DNS > server. If not sure how to create a Forwarder, please read the following > link with a how-to. > > HOW TO Configure DNS for Internet Access in Windows Server 2003 (including > how to configure a Forwarder) : > http://support.microsoft.com/?id=323380 > > Ace > > > > > |
|
|
|
|
|||
|
|
| |
|
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| XPOST: Fast boot, delay after 1st login if privileged action required | Linus Schroeder | Windows Vista Installation | 2 | 12-20-2008 01:38 PM |
| Long delay on "Connect to a network" after upgrading to Vista | Carl Farrington | Windows Vista Installation | 2 | 10-24-2007 10:30 PM |
| Long delay accessing XP Briefcase under Vista | Edge30 | Windows Vista Administration | 0 | 09-13-2007 06:14 PM |
| Delay After Login | Mike | Windows Vista Performance | 0 | 06-02-2007 02:10 AM |
| Fast boot, delay after 1st login if privileged action required | Linus Schroeder | Windows Vista Performance | 0 | 02-23-2007 05:33 PM |
Linear Mode
