dns and dhcp question?!

  • Thread starter Thread starter daniel
  • Start date Start date
D

daniel

Hi i am running a windows 2000 server (service pack 4)
with a dhcp server setup (it was setup before i started
working here)in the tcp/ip window, there are no
settings ..it says "obtain automatically"
dns is setup i think ...because everyone logs in to :
blahblah.com and under dns on the server it has this info
there.
The problem: When i boot up my windows 2000 client which
makes a connection to the server for data files and
such..IT TAKES OVER 30 MINUTES OR MORE TO BOOT UP! (if it
ever boots up that is)
there is something the client is searching for.. i dont
know what.
when i unplug the network cable on the client during the
extremely painfull waiting period on boot up, all of a
sudden the computer boots right up...then i reconect the
cable and proceed as usual to work.
HOW can i fix this problem??? is there a setting i need to
create on the server? workstation? PLEASE HELP!!!
thanks
---daniel
 
Does this happen only on this computer? Have you run an ipconfig/all at the
commend prompt and examined the results?
 
it happens only on the win 2000 pc's not any of the 98
machines.
ipconfig /all results:
dhcp enabled: yes
autoconfiguration enabled: yes
ip address: 192.168.254.31
subnet mask: 255.255.255.0
default gateway: 192.168.254.254
dhcp server: 192.168.254.254
dns servers: 192.168.254.254

is this any help??
thanks
 
Why is the DNS (and assume the DC) set as the client's Default Gateway? Is
the DC multihomed and configured as a LAN Router? Aside from the special
situation of SBS, a DC is recommended to *never* be multi-homed and should
not be used as a Router. The Default Gateway should only point to the LAN
Router,...if there is no LAN Router than it *might* point to a
Firewall,...if not that then the DFG is simply left blank.

The long delay can be caused by DNS problems when it contacts the DC, which
is commonly caused by a multihomed DC. Unplugging the network cable kills
any connection to the DC and allows the workstation to "login" with the
locally cached account just like it would if the DC was "missing" on the
network,... so then it "comes up" quickly. When you plug the cable back in
after the cached account is already loaded everything is "happy" more or
less.
 
hi im not sure how the server is configured..it was done
before i got here...all i know is that there are blank
settings in the TCP/IP window on the server, and a router
is plugged into the switch which all the connections are
plugged into as well.
Also on the client the settings i gave you, came up
automatically...even though there are blank settings
(automatically detect) in the TCP/IP window on the client
as well. What can i do to fix this situation, whether it
be reconfiguring the server or workstation to have static
IP settings?? or do i reconfigure the workstation to go
directly to the router??
I need help!
please advise, thank you
---daniel
(e-mail address removed)
-----Original Message-----
Why is the DNS (and assume the DC) set as the client's Default Gateway? Is
the DC multihomed and configured as a LAN Router? Aside from the special
situation of SBS, a DC is recommended to *never* be multi- homed and should
not be used as a Router. The Default Gateway should only point to the LAN
Router,...if there is no LAN Router than it *might* point to a
Firewall,...if not that then the DFG is simply left blank.

The long delay can be caused by DNS problems when it contacts the DC, which
is commonly caused by a multihomed DC. Unplugging the network cable kills
any connection to the DC and allows the workstation to "login" with the
locally cached account just like it would if the DC was "missing" on the
network,... so then it "comes up" quickly. When you plug the cable back in
after the cached account is already loaded everything is "happy" more or
less.


--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


daniel said:
it happens only on the win 2000 pc's not any of the 98
machines.
ipconfig /all results:
dhcp enabled: yes
autoconfiguration enabled: yes
ip address: 192.168.254.31
subnet mask: 255.255.255.0
default gateway: 192.168.254.254
dhcp server: 192.168.254.254
dns servers: 192.168.254.254

is this any help??
thanks (if
it need
to
Click to expand...


.
Click to expand...
 
Typically servers will have a static ip address. You mention that there is
a router plugged into the switch. What is the router being used for?
Internet access, another subnet? How is the dhcp server configured regarding
scopoe or server options?



daniel said:
hi im not sure how the server is configured..it was done
before i got here...all i know is that there are blank
settings in the TCP/IP window on the server, and a router
is plugged into the switch which all the connections are
plugged into as well.
Also on the client the settings i gave you, came up
automatically...even though there are blank settings
(automatically detect) in the TCP/IP window on the client
as well. What can i do to fix this situation, whether it
be reconfiguring the server or workstation to have static
IP settings?? or do i reconfigure the workstation to go
directly to the router??
I need help!
please advise, thank you
---daniel
(e-mail address removed)
-----Original Message-----
Why is the DNS (and assume the DC) set as the client's Default Gateway? Is
the DC multihomed and configured as a LAN Router? Aside from the special
situation of SBS, a DC is recommended to *never* be multi- homed and should
not be used as a Router. The Default Gateway should only point to the LAN
Router,...if there is no LAN Router than it *might* point to a
Firewall,...if not that then the DFG is simply left blank.

The long delay can be caused by DNS problems when it contacts the DC, which
is commonly caused by a multihomed DC. Unplugging the network cable kills
any connection to the DC and allows the workstation to "login" with the
locally cached account just like it would if the DC was "missing" on the
network,... so then it "comes up" quickly. When you plug the cable back in
after the cached account is already loaded everything is "happy" more or
less.


--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


daniel said:
it happens only on the win 2000 pc's not any of the 98
machines.
ipconfig /all results:
dhcp enabled: yes
autoconfiguration enabled: yes
ip address: 192.168.254.31
subnet mask: 255.255.255.0
default gateway: 192.168.254.254
dhcp server: 192.168.254.254
dns servers: 192.168.254.254

is this any help??
thanks
-----Original Message-----
Does this happen only on this computer? Have you run an
ipconfig/all at the
commend prompt and examined the results?

Hi i am running a windows 2000 server (service pack 4)
with a dhcp server setup (it was setup before i started
working here)in the tcp/ip window, there are no
settings ..it says "obtain automatically"
dns is setup i think ...because everyone logs in to :
blahblah.com and under dns on the server it has this
info
there.
The problem: When i boot up my windows 2000 client which
makes a connection to the server for data files and
such..IT TAKES OVER 30 MINUTES OR MORE TO BOOT UP! (if
it
ever boots up that is)
there is something the client is searching for.. i dont
know what.
when i unplug the network cable on the client during the
extremely painfull waiting period on boot up, all of a
sudden the computer boots right up...then i reconect the
cable and proceed as usual to work.
HOW can i fix this problem??? is there a setting i need
to
create on the server? workstation? PLEASE HELP!!!
thanks
---daniel


.
Click to expand...


.
Click to expand...
Click to expand...
 
I would reconfigure the server with a static IP address. Your DNS,
DHCP, WINS, and Domain Controllers, should always have static IP
addresses.

I think the problem you are having with the Windows 2000 machines is
with DNS. Windows 2000 Pro machines and above will query DNS for the
location of SRV records for Kerberos, and LDAP. Because you have the
server that is DHCP, and DNS set as a DHCP Client, there may be a
problem with performing Dynamic updates.

To resolve this, first configure the IP address as static. Second,
remove the address from DHCP active lease. Third, add the address as
an exclusion on DHCP. Fourth, run ipconfig /registerdns. Fifth, Add
a DHCP scope option for DNS Option 006 to point to the DNS IP address.
Sixth, run the following commands sequentially, net stop netlogon,
net start netlogon, on your DC. This allows the registration of SRV
records. lastly, run ipconfig /renew on your 2000 clients.


daniel said:
hi im not sure how the server is configured..it was done
before i got here...all i know is that there are blank
settings in the TCP/IP window on the server, and a router
is plugged into the switch which all the connections are
plugged into as well.
Also on the client the settings i gave you, came up
automatically...even though there are blank settings
(automatically detect) in the TCP/IP window on the client
as well. What can i do to fix this situation, whether it
be reconfiguring the server or workstation to have static
IP settings?? or do i reconfigure the workstation to go
directly to the router??
I need help!
please advise, thank you
---daniel
(e-mail address removed)
-----Original Message-----
Why is the DNS (and assume the DC) set as the client's Default Gateway? Is
the DC multihomed and configured as a LAN Router? Aside from the special
situation of SBS, a DC is recommended to *never* be multi- homed and should
not be used as a Router. The Default Gateway should only point to the LAN
Router,...if there is no LAN Router than it *might* point to a
Firewall,...if not that then the DFG is simply left blank.

The long delay can be caused by DNS problems when it contacts the DC, which
is commonly caused by a multihomed DC. Unplugging the network cable kills
any connection to the DC and allows the workstation to "login" with the
locally cached account just like it would if the DC was "missing" on the
network,... so then it "comes up" quickly. When you plug the cable back in
after the cached account is already loaded everything is "happy" more or
less.


--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


daniel said:
it happens only on the win 2000 pc's not any of the 98
machines.
ipconfig /all results:
dhcp enabled: yes
autoconfiguration enabled: yes
ip address: 192.168.254.31
subnet mask: 255.255.255.0
default gateway: 192.168.254.254
dhcp server: 192.168.254.254
dns servers: 192.168.254.254

is this any help??
thanks
-----Original Message-----
Does this happen only on this computer? Have you run an ipconfig/all at the
commend prompt and examined the results?

Hi i am running a windows 2000 server (service pack 4)
with a dhcp server setup (it was setup before i started
working here)in the tcp/ip window, there are no
settings ..it says "obtain automatically"
dns is setup i think ...because everyone logs in to :
blahblah.com and under dns on the server it has this info
there.
The problem: When i boot up my windows 2000 client which
makes a connection to the server for data files and
such..IT TAKES OVER 30 MINUTES OR MORE TO BOOT UP!
Click to expand...
(if
it
ever boots up that is)
there is something the client is searching for.. i dont
know what.
when i unplug the network cable on the client during the
extremely painfull waiting period on boot up, all of a
sudden the computer boots right up...then i reconect the
cable and proceed as usual to work.
HOW can i fix this problem??? is there a setting i
Click to expand...
need
to
create on the server? workstation? PLEASE HELP!!!
thanks
---daniel


.
Click to expand...


.
Click to expand...
Click to expand...
 
Back
Top