 |
|
|
|
Next: event log corruption
|
| Author |
Message |
External
Since: Aug 27, 2007
Posts: 213
|
(Msg. 16) Posted: Wed Oct 24, 2007 4:07 pm
Post subject: Re: Domain controller not found [Login to view extended thread Info.]
Archived from groups: microsoft>public>windows>server>setup (more info?)
|
|
|
Hello Jim,
Sorry for asking again about the 192.168.0.1 Did you use it anywhere in the
network? You said the router is x.x.1.4 and now you say the gateway "knows"?
the address. This address has nothing to do with your network.
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
> No, the gateway/router is the only device that "knows" that IP.
>
> "Meinolf Weber" wrote in message
>
>
>> Hello Jim,
>>
>> So the 192.168.0.1 is not longer used on any server or workstation?
>>
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers no rights.
>>> 1.4 is the only default gateway/router. It's WAN port is hooked up
>>> to the DSL modem and it gets it's external IP and DNS info from the
>>> modem. But all that should be transparent to the office network, and
>>> it has worked fine for quite some time. It just seems that the DNS
>>> and/or Active Directory services have been slowly degrading.
>>>
>>> Again, the forwarders on the DC's DNS properties are the external
>>> ones QWest uses for the DSL connection.
>>>
>>> Thanks again,
>>> Jim
>>> "Meinolf Weber" wrote in message
>>>
>>>> Hello Jim,
>>>>
>>>> Coming back to the ip settings. Your workstations and server works
>>>> with ip's like 192.168.1.4 192.168.1.10 192.168.1.102
>>>>
>>>> The router (Default gateway) ip 192.168.0.1
>>>>
>>>> And you specify also 192.168.1.4 as a default gateway. Can you give
>>>> some more info about the network setup please. You can not work
>>>> with two default gateways in one network that have different ip
>>>> ranges.
>>>>
>>>> Best regards
>>>>
>>>> Meinolf Weber
>>>> Disclaimer: This posting is provided "AS IS" with no warranties,
>>>> and
>>>> confers no rights.
>>>>> Okay, I have only the DC given out as a DNS. But, I am getting the
>>>>> same error messages on startup.
>>>>>
>>>>> But, with the DHCP server giving out only the DC as the DNS, my
>>>>> browser cannot resolve DNS requests. So either the DNS on the
>>>>> server is not forwarding or something.
>>>>>
>>>>> "Meinolf Weber" wrote in message
>>>>>
>>>>>
>>>>>> Hello Jim,
>>>>>>
>>>>>> see inline
>>>>>>
>>>>>> Best regards
>>>>>>
>>>>>> Meinolf Weber
>>>>>> Disclaimer: This posting is provided "AS IS" with no warranties,
>>>>>> and
>>>>>> confers no rights.
>>>>>>> Thanks for getting back to me!
>>>>>>>
>>>>>>> The modem IP was not in the forwarders list. Only two DNS's that
>>>>>>> belong to QWest.
>>>>>>>
>>>>>>> The 192.168.0.1 ip was in the network card TCP/IP properties as
>>>>>>> the secondary DNS. I changed that to 192.168.1.4 which is the
>>>>>>> gateway. Unless I should just leave it blank
>>>>>>>
>>>>>> The NIC should only point to your INTERNAL DNS server, that's
>>>>>> all.
>>>>>>
>>>>>>> Here are the startup errors now on the XP workstation, which
>>>>>>> takes, again, about 5 minutes to get a functional desktop:
>>>>>>>
>>>>>>> Windows cannot determine the user or computer name. (The
>>>>>>> specified domain either does not exist or could not be
>>>>>>> contacted. ). Group Policy processing aborted.
>>>>>>>
>>>>>>> Automatic certificate enrollment for local system failed to
>>>>>>> contact the active directory (0x8007054b). The specified domain
>>>>>>> either does not exist or could not be contacted.
>>>>>>>
>>>>>>> The PrintQueue Container could not be found because the DNS
>>>>>>> Domain name could not be retrieved. Error: 54b
>>>>>>>
>>>>>> This will depend on the ip address from the router, remove it
>>>>>> like i wrote before. DNS settings should only point to the
>>>>>> internal DNS. In the moment the computer tries to find the domain
>>>>>> also outside your network, what will not work.
>>>>>>
>>>>>>> "Meinolf Weber" wrote in message
>>>>>>>
>>>>>>>
>>>>>>>> Hello Jim,
>>>>>>>>
>>>>>>>> Is the first problem solved? Other wise lets go on with that.
>>>>>>>> Did you remove the entry from DNS settings?
>>>>>>>>
>>>>>>>> Best regards
>>>>>>>>
>>>>>>>> Meinolf Weber
>>>>>>>> Disclaimer: This posting is provided "AS IS" with no
>>>>>>>> warranties,
>>>>>>>> and
>>>>>>>> confers no rights.
>>>>>>>>> Well, the external DNS is already set up in the forwarders
>>>>>>>>> tab. I rechecked the IP's, and they are what the DSL modem is
>>>>>>>>> using.
>>>>>>>>>
>>>>>>>>> Another symptom: now my XP machine is taking 30 to 60 seconds
>>>>>>>>> just to open programs. But, when I'm off the net, they come
>>>>>>>>> right up, as does the desktop.
>>>>>>>>>
>>>>>>>>> "Meinolf Weber" wrote in message
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Hello Jim,
>>>>>>>>>>
>>>>>>>>>> You have to configure a forwarder to your ISP's DNS server on
>>>>>>>>>> the
>>>>>>>>>> DNS
>>>>>>>>>> server properties in the DNS management console. Here you
>>>>>>>>>> find
>>>>>>>>>> a
>>>>>>>>>> tab
>>>>>>>>>> called "Forwarders". If it is greyed out inside just remove
>>>>>>>>>> the
>>>>>>>>>> .zone
>>>>>>>>>> in
>>>>>>>>>> DNS, close the DNS console and reopen it. Then you can add
>>>>>>>>>> the
>>>>>>>>>> ISP's
>>>>>>>>>> DNS
>>>>>>>>>> server, not your router ip address. It should be an external
>>>>>>>>>> internet
>>>>>>>>>> ip
>>>>>>>>>> address.
>>>>>>>>>> So all internal request from the machines go to your inside
>>>>>>>>>> DNS
>>>>>>>>>> server, if
>>>>>>>>>> that can't provide the information it will forward the
>>>>>>>>>> request
>>>>>>>>>> to
>>>>>>>>>> the
>>>>>>>>>> ISP's DNS server and get theire the answer.
>>>>>>>>>> Remove the modem ip address and your internal errors should
>>>>>>>>>> go
>>>>>>>>>> away.
>>>>>>>>>> But
>>>>>>>>>> you also be aible to browse the internet.
>>>>>>>>>> Best regards
>>>>>>>>>> Meinolf Weber
>>>>>>>>>> Disclaimer: This posting is provided "AS IS" with no
>>>>>>>>>> warranties,
>>>>>>>>>> and
>>>>>>>>>> confers no rights.
>>>>>>>>>>> That is a DSL modem, on the other side of the gateway, which
>>>>>>>>>>> is supposed to forward to an external DNS if 192.168.1.10 is
>>>>>>>>>>> unable to fulfill the request. What is the ideal setting for
>>>>>>>>>>> the secondary DNS? What would this have to do with finding
>>>>>>>>>>> the DC?
>>>>>>>>>>>
>>>>>>>>>>> "Meinolf Weber" wrote in message
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> Hello Jim,
>>>>>>>>>>>>
>>>>>>>>>>>> What is the 192.168.0.1 for a machine? It is a different
>>>>>>>>>>>> network
>>>>>>>>>>>> address
>>>>>>>>>>>> and can cause your problems.
>>>>>>>>>>>> Best regards
>>>>>>>>>>>> Meinolf Weber
>>>>>>>>>>>> Disclaimer: This posting is provided "AS IS" with no
>>>>>>>>>>>> warranties,
>>>>>>>>>>>> and
>>>>>>>>>>>> confers no rights.
>>>>>>>>>>>>> 192.168.0.1
>>>>>>>>>>>>> |
|
| Back to top |
|
 | |
External
Since: Mar 25, 2006
Posts: 15
|
(Msg. 17) Posted: Thu Oct 25, 2007 9:35 am
Post subject: Re: Domain controller not found [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
The WAN port on the gateway has an IP of 192.168.0.4. All internet traffic
from the 192.168.1.x subnet goes through the gateway, which sends it to the
DSL modem on the 192.168.0.x subnet. Technically, the gateway is really
acting as a bridge, and the DSL modem is the "real" gateway.
"Meinolf Weber" wrote in message
> Hello Jim,
>
> Sorry for asking again about the 192.168.0.1 Did you use it anywhere in
> the network? You said the router is x.x.1.4 and now you say the gateway
> "knows"? the address. This address has nothing to do with your network.
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and
> confers no rights.
>
>> No, the gateway/router is the only device that "knows" that IP.
>>
>> "Meinolf Weber" wrote in message
>>
>>
>>> Hello Jim,
>>>
>>> So the 192.168.0.1 is not longer used on any server or workstation?
>>>
>>> Best regards
>>>
>>> Meinolf Weber
>>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>>> confers no rights.
>>>> 1.4 is the only default gateway/router. It's WAN port is hooked up
>>>> to the DSL modem and it gets it's external IP and DNS info from the
>>>> modem. But all that should be transparent to the office network, and
>>>> it has worked fine for quite some time. It just seems that the DNS
>>>> and/or Active Directory services have been slowly degrading.
>>>>
>>>> Again, the forwarders on the DC's DNS properties are the external
>>>> ones QWest uses for the DSL connection.
>>>>
>>>> Thanks again,
>>>> Jim
>>>> "Meinolf Weber" wrote in message
>>>>
>>>>> Hello Jim,
>>>>>
>>>>> Coming back to the ip settings. Your workstations and server works
>>>>> with ip's like 192.168.1.4 192.168.1.10 192.168.1.102
>>>>>
>>>>> The router (Default gateway) ip 192.168.0.1
>>>>>
>>>>> And you specify also 192.168.1.4 as a default gateway. Can you give
>>>>> some more info about the network setup please. You can not work
>>>>> with two default gateways in one network that have different ip
>>>>> ranges.
>>>>>
>>>>> Best regards
>>>>>
>>>>> Meinolf Weber
>>>>> Disclaimer: This posting is provided "AS IS" with no warranties,
>>>>> and
>>>>> confers no rights.
>>>>>> Okay, I have only the DC given out as a DNS. But, I am getting the
>>>>>> same error messages on startup.
>>>>>>
>>>>>> But, with the DHCP server giving out only the DC as the DNS, my
>>>>>> browser cannot resolve DNS requests. So either the DNS on the
>>>>>> server is not forwarding or something.
>>>>>>
>>>>>> "Meinolf Weber" wrote in message
>>>>>>
>>>>>>
>>>>>>> Hello Jim,
>>>>>>>
>>>>>>> see inline
>>>>>>>
>>>>>>> Best regards
>>>>>>>
>>>>>>> Meinolf Weber
>>>>>>> Disclaimer: This posting is provided "AS IS" with no warranties,
>>>>>>> and
>>>>>>> confers no rights.
>>>>>>>> Thanks for getting back to me!
>>>>>>>>
>>>>>>>> The modem IP was not in the forwarders list. Only two DNS's that
>>>>>>>> belong to QWest.
>>>>>>>>
>>>>>>>> The 192.168.0.1 ip was in the network card TCP/IP properties as
>>>>>>>> the secondary DNS. I changed that to 192.168.1.4 which is the
>>>>>>>> gateway. Unless I should just leave it blank
>>>>>>>>
>>>>>>> The NIC should only point to your INTERNAL DNS server, that's
>>>>>>> all.
>>>>>>>
>>>>>>>> Here are the startup errors now on the XP workstation, which
>>>>>>>> takes, again, about 5 minutes to get a functional desktop:
>>>>>>>>
>>>>>>>> Windows cannot determine the user or computer name. (The
>>>>>>>> specified domain either does not exist or could not be
>>>>>>>> contacted. ). Group Policy processing aborted.
>>>>>>>>
>>>>>>>> Automatic certificate enrollment for local system failed to
>>>>>>>> contact the active directory (0x8007054b). The specified domain
>>>>>>>> either does not exist or could not be contacted.
>>>>>>>>
>>>>>>>> The PrintQueue Container could not be found because the DNS
>>>>>>>> Domain name could not be retrieved. Error: 54b
>>>>>>>>
>>>>>>> This will depend on the ip address from the router, remove it
>>>>>>> like i wrote before. DNS settings should only point to the
>>>>>>> internal DNS. In the moment the computer tries to find the domain
>>>>>>> also outside your network, what will not work.
>>>>>>>
>>>>>>>> "Meinolf Weber" wrote in message
>>>>>>>>
>>>>>>>>
>>>>>>>>> Hello Jim,
>>>>>>>>>
>>>>>>>>> Is the first problem solved? Other wise lets go on with that.
>>>>>>>>> Did you remove the entry from DNS settings?
>>>>>>>>>
>>>>>>>>> Best regards
>>>>>>>>>
>>>>>>>>> Meinolf Weber
>>>>>>>>> Disclaimer: This posting is provided "AS IS" with no
>>>>>>>>> warranties,
>>>>>>>>> and
>>>>>>>>> confers no rights.
>>>>>>>>>> Well, the external DNS is already set up in the forwarders
>>>>>>>>>> tab. I rechecked the IP's, and they are what the DSL modem is
>>>>>>>>>> using.
>>>>>>>>>>
>>>>>>>>>> Another symptom: now my XP machine is taking 30 to 60 seconds
>>>>>>>>>> just to open programs. But, when I'm off the net, they come
>>>>>>>>>> right up, as does the desktop.
>>>>>>>>>>
>>>>>>>>>> "Meinolf Weber" wrote in message
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> Hello Jim,
>>>>>>>>>>>
>>>>>>>>>>> You have to configure a forwarder to your ISP's DNS server on
>>>>>>>>>>> the
>>>>>>>>>>> DNS
>>>>>>>>>>> server properties in the DNS management console. Here you
>>>>>>>>>>> find
>>>>>>>>>>> a
>>>>>>>>>>> tab
>>>>>>>>>>> called "Forwarders". If it is greyed out inside just remove
>>>>>>>>>>> the
>>>>>>>>>>> .zone
>>>>>>>>>>> in
>>>>>>>>>>> DNS, close the DNS console and reopen it. Then you can add
>>>>>>>>>>> the
>>>>>>>>>>> ISP's
>>>>>>>>>>> DNS
>>>>>>>>>>> server, not your router ip address. It should be an external
>>>>>>>>>>> internet
>>>>>>>>>>> ip
>>>>>>>>>>> address.
>>>>>>>>>>> So all internal request from the machines go to your inside
>>>>>>>>>>> DNS
>>>>>>>>>>> server, if
>>>>>>>>>>> that can't provide the information it will forward the
>>>>>>>>>>> request
>>>>>>>>>>> to
>>>>>>>>>>> the
>>>>>>>>>>> ISP's DNS server and get theire the answer.
>>>>>>>>>>> Remove the modem ip address and your internal errors should
>>>>>>>>>>> go
>>>>>>>>>>> away.
>>>>>>>>>>> But
>>>>>>>>>>> you also be aible to browse the internet.
>>>>>>>>>>> Best regards
>>>>>>>>>>> Meinolf Weber
>>>>>>>>>>> Disclaimer: This posting is provided "AS IS" with no
>>>>>>>>>>> warranties,
>>>>>>>>>>> and
>>>>>>>>>>> confers no rights.
>>>>>>>>>>>> That is a DSL modem, on the other side of the gateway, which
>>>>>>>>>>>> is supposed to forward to an external DNS if 192.168.1.10 is
>>>>>>>>>>>> unable to fulfill the request. What is the ideal setting for
>>>>>>>>>>>> the secondary DNS? What would this have to do with finding
>>>>>>>>>>>> the DC?
>>>>>>>>>>>>
>>>>>>>>>>>> "Meinolf Weber" wrote in message
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> Hello Jim,
>>>>>>>>>>>>>
>>>>>>>>>>>>> What is the 192.168.0.1 for a machine? It is a different
>>>>>>>>>>>>> network
>>>>>>>>>>>>> address
>>>>>>>>>>>>> and can cause your problems.
>>>>>>>>>>>>> Best regards
>>>>>>>>>>>>> Meinolf Weber
>>>>>>>>>>>>> Disclaimer: This posting is provided "AS IS" with no
>>>>>>>>>>>>> warranties,
>>>>>>>>>>>>> and
>>>>>>>>>>>>> confers no rights.
>>>>>>>>>>>>>> 192.168.0.1
>>>>>>>>>>>>>>
>
> |
|
| Back to top |
|
| |
External
Since: Mar 25, 2006
Posts: 15
|
(Msg. 18) Posted: Wed Oct 31, 2007 7:33 am
Post subject: Re: Domain controller not found [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
So....what's up? No further thoughts?
"Jim" wrote in message
> From an XP pro system, all the latest updates installed, the system event
> log records a netlogon error:
>
> "No Domain Controller is available for domain SIENA due to the following:
> There are currently no logon servers available to service the logon
> request. . "
>
> Yet, I can access the DC's shares and certainly ping it. But, it takes
> several minutes to get a functional desktop upon startup. Also, I can get
> sudden denial of access errors out of the blue and lose connection,
> apparently. Then I get "log in as" boxes popping up which do not accept
> even my domain admin login. Also, my system has taken to a 20 second delay
> to come back when it's "locked". It used to come up instantly. Finally,
> accessing files on the file server/DC is very sluggish. I have to wait a
> few seconds for explorer to refresh itself everytime I click on a file,
> change a name, click on a folder, etc. It's maddening.
>
> I have a fairly fresh install of SBS2003 and there are no apps installed
> on the server. It shows no errors in its event log. My local net stats are
> (the server has the 192.168.1.10 address):
>
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : ignatius
> Primary Dns Suffix . . . . . . . : Siena.local
> Node Type . . . . . . . . . . . . : Hybrid
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : Siena.local
> Siena
>
> Ethernet adapter PCI Card:
>
> Connection-specific DNS Suffix . : Siena
> Description . . . . . . . . . . . : Lite-On Communications
> Compatable PCI Fast Ethernet Adapter
> Physical Address. . . . . . . . . : 00-C0-F0-2D-BA-43
> Dhcp Enabled. . . . . . . . . . . : Yes
> Autoconfiguration Enabled . . . . : Yes
> IP Address. . . . . . . . . . . . : 192.168.1.102
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.1.4
> DHCP Server . . . . . . . . . . . : 192.168.1.4
> DNS Servers . . . . . . . . . . . : 198.168.1.10
> 192.168.1.4
> Lease Obtained. . . . . . . . . . : Friday, October 19, 2007
> 8:50:09 AM
> Lease Expires . . . . . . . . . . : Monday, October 22, 2007
> 8:50:09 AM
>
> Thanks for any help.
> Jim
> >> Stay informed about: Domain controller not found |
|
| Back to top |
|
| |
External
Since: Aug 27, 2007
Posts: 213
|
(Msg. 19) Posted: Wed Oct 31, 2007 2:13 pm
Post subject: Re: Domain controller not found [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
Hello Jim,
For my point of view you still use 2 different networks. 192.168.0.x for
DG and 192.168.1.x for your LAN. One of them you have to change to get it
working complete.
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.dts-l.org/goodpost.htm
> So....what's up? No further thoughts?
>
> "Jim" wrote in message
>
>
>> From an XP pro system, all the latest updates installed, the system
>> event log records a netlogon error:
>>
>> "No Domain Controller is available for domain SIENA due to the
>> following: There are currently no logon servers available to service
>> the logon request. . "
>>
>> Yet, I can access the DC's shares and certainly ping it. But, it
>> takes several minutes to get a functional desktop upon startup. Also,
>> I can get sudden denial of access errors out of the blue and lose
>> connection, apparently. Then I get "log in as" boxes popping up
>> which do not accept even my domain admin login. Also, my system has
>> taken to a 20 second delay to come back when it's "locked". It used
>> to come up instantly. Finally, accessing files on the file server/DC
>> is very sluggish. I have to wait a few seconds for explorer to
>> refresh itself everytime I click on a file, change a name, click on a
>> folder, etc. It's maddening.
>>
>> I have a fairly fresh install of SBS2003 and there are no apps
>> installed on the server. It shows no errors in its event log. My
>> local net stats are (the server has the 192.168.1.10 address):
>>
>> Windows IP Configuration
>>
>> Host Name . . . . . . . . . . . . : ignatius
>> Primary Dns Suffix . . . . . . . : Siena.local
>> Node Type . . . . . . . . . . . . : Hybrid
>> IP Routing Enabled. . . . . . . . : No
>> WINS Proxy Enabled. . . . . . . . : No
>> DNS Suffix Search List. . . . . . : Siena.local
>> Siena
>> Ethernet adapter PCI Card:
>>
>> Connection-specific DNS Suffix . : Siena
>> Description . . . . . . . . . . . : Lite-On Communications
>> Compatable PCI Fast Ethernet Adapter
>> Physical Address. . . . . . . . . : 00-C0-F0-2D-BA-43
>> Dhcp Enabled. . . . . . . . . . . : Yes
>> Autoconfiguration Enabled . . . . : Yes
>> IP Address. . . . . . . . . . . . : 192.168.1.102
>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> Default Gateway . . . . . . . . . : 192.168.1.4
>> DHCP Server . . . . . . . . . . . : 192.168.1.4
>> DNS Servers . . . . . . . . . . . : 198.168.1.10
>> 192.168.1.4
>> Lease Obtained. . . . . . . . . . : Friday, October 19, 2007
>> 8:50:09 AM
>> Lease Expires . . . . . . . . . . : Monday, October 22, 2007
>> 8:50:09 AM
>> Thanks for any help.
>> Jim >> Stay informed about: Domain controller not found |
|
| Back to top |
|
| |
External
Since: Mar 25, 2006
Posts: 15
|
(Msg. 20) Posted: Thu Nov 01, 2007 9:37 am
Post subject: Re: Domain controller not found [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
I must use two different subnets, and I know what I'm doing here as far as
the physical lan, bridges, gateways, etc. But there is no reason why that
should affect logging into the DC, since the computers are all on the same
subnet. But thanks for trying...
"Meinolf Weber" wrote in message
> Hello Jim,
>
> For my point of view you still use 2 different networks. 192.168.0.x for
> DG and 192.168.1.x for your LAN. One of them you have to change to get it
> working complete.
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and
> confers no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.dts-l.org/goodpost.htm
>
>> So....what's up? No further thoughts?
>>
>> "Jim" wrote in message
>>
>>
>>> From an XP pro system, all the latest updates installed, the system
>>> event log records a netlogon error:
>>>
>>> "No Domain Controller is available for domain SIENA due to the
>>> following: There are currently no logon servers available to service
>>> the logon request. . "
>>>
>>> Yet, I can access the DC's shares and certainly ping it. But, it
>>> takes several minutes to get a functional desktop upon startup. Also,
>>> I can get sudden denial of access errors out of the blue and lose
>>> connection, apparently. Then I get "log in as" boxes popping up
>>> which do not accept even my domain admin login. Also, my system has
>>> taken to a 20 second delay to come back when it's "locked". It used
>>> to come up instantly. Finally, accessing files on the file server/DC
>>> is very sluggish. I have to wait a few seconds for explorer to
>>> refresh itself everytime I click on a file, change a name, click on a
>>> folder, etc. It's maddening.
>>>
>>> I have a fairly fresh install of SBS2003 and there are no apps
>>> installed on the server. It shows no errors in its event log. My
>>> local net stats are (the server has the 192.168.1.10 address):
>>>
>>> Windows IP Configuration
>>>
>>> Host Name . . . . . . . . . . . . : ignatius
>>> Primary Dns Suffix . . . . . . . : Siena.local
>>> Node Type . . . . . . . . . . . . : Hybrid
>>> IP Routing Enabled. . . . . . . . : No
>>> WINS Proxy Enabled. . . . . . . . : No
>>> DNS Suffix Search List. . . . . . : Siena.local
>>> Siena
>>> Ethernet adapter PCI Card:
>>>
>>> Connection-specific DNS Suffix . : Siena
>>> Description . . . . . . . . . . . : Lite-On Communications
>>> Compatable PCI Fast Ethernet Adapter
>>> Physical Address. . . . . . . . . : 00-C0-F0-2D-BA-43
>>> Dhcp Enabled. . . . . . . . . . . : Yes
>>> Autoconfiguration Enabled . . . . : Yes
>>> IP Address. . . . . . . . . . . . : 192.168.1.102
>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>> Default Gateway . . . . . . . . . : 192.168.1.4
>>> DHCP Server . . . . . . . . . . . : 192.168.1.4
>>> DNS Servers . . . . . . . . . . . : 198.168.1.10
>>> 192.168.1.4
>>> Lease Obtained. . . . . . . . . . : Friday, October 19, 2007
>>> 8:50:09 AM
>>> Lease Expires . . . . . . . . . . : Monday, October 22, 2007
>>> 8:50:09 AM
>>> Thanks for any help.
>>> Jim
>
> >> Stay informed about: Domain controller not found |
|
| Back to top |
|
| |
External
Since: Jul 10, 2007
Posts: 7
|
(Msg. 21) Posted: Thu Nov 01, 2007 9:37 am
Post subject: Re: Domain controller not found [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
Jim wrote:
> I must use two different subnets, and I know what I'm doing here as
> far as the physical lan, bridges, gateways, etc. But there is no
> reason why that should affect logging into the DC, since the
> computers are all on the same subnet. But thanks for trying...
DC's are located using the SBS DNS server. Slow desktops, slow unlocks, are
all symptoms of DNS/AD misconfiguration.
Configure *ALL* clients and Servers to use *only* the SBS (AD/DNS) as DNS,
run the CEICW wizard for proper SBS DNS server forwarding and your problems
will disappear. Also SBS has it's own very active newsgroup ;
microsoft.public.windows.server.sbs
>>>> DHCP Server . . . . . . . . . . . : 192.168.1.4
>>>> DNS Servers . . . . . . . . . . . : 198.168.1.10
>
> "Meinolf Weber" wrote in message
>
>> Hello Jim,
>>
>> For my point of view you still use 2 different networks. 192.168.0.x
>> for DG and 192.168.1.x for your LAN. One of them you have to change
>> to get it working complete.
>>
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers no rights.
>> ** Please do NOT email, only reply to Newsgroups
>> ** HELP us help YOU!!! http://www.dts-l.org/goodpost.htm
>>
>>> So....what's up? No further thoughts?
>>>
>>> "Jim" wrote in message
>>>
>>>
>>>> From an XP pro system, all the latest updates installed, the system
>>>> event log records a netlogon error:
>>>>
>>>> "No Domain Controller is available for domain SIENA due to the
>>>> following: There are currently no logon servers available to
>>>> service the logon request. . "
>>>>
>>>> Yet, I can access the DC's shares and certainly ping it. But, it
>>>> takes several minutes to get a functional desktop upon startup.
>>>> Also, I can get sudden denial of access errors out of the blue and
>>>> lose connection, apparently. Then I get "log in as" boxes popping
>>>> up which do not accept even my domain admin login. Also, my system
>>>> has taken to a 20 second delay to come back when it's "locked". It
>>>> used to come up instantly. Finally, accessing files on the file
>>>> server/DC is very sluggish. I have to wait a few seconds for
>>>> explorer to refresh itself everytime I click on a file, change a
>>>> name, click on a folder, etc. It's maddening.
>>>>
>>>> I have a fairly fresh install of SBS2003 and there are no apps
>>>> installed on the server. It shows no errors in its event log. My
>>>> local net stats are (the server has the 192.168.1.10 address):
>>>>
>>>> Windows IP Configuration
>>>>
>>>> Host Name . . . . . . . . . . . . : ignatius
>>>> Primary Dns Suffix . . . . . . . : Siena.local
>>>> Node Type . . . . . . . . . . . . : Hybrid
>>>> IP Routing Enabled. . . . . . . . : No
>>>> WINS Proxy Enabled. . . . . . . . : No
>>>> DNS Suffix Search List. . . . . . : Siena.local
>>>> Siena
>>>> Ethernet adapter PCI Card:
>>>>
>>>> Connection-specific DNS Suffix . : Siena
>>>> Description . . . . . . . . . . . : Lite-On Communications
>>>> Compatable PCI Fast Ethernet Adapter
>>>> Physical Address. . . . . . . . . : 00-C0-F0-2D-BA-43
>>>> Dhcp Enabled. . . . . . . . . . . : Yes
>>>> Autoconfiguration Enabled . . . . : Yes
>>>> IP Address. . . . . . . . . . . . : 192.168.1.102
>>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>>> Default Gateway . . . . . . . . . : 192.168.1.4
>>>> DHCP Server . . . . . . . . . . . : 192.168.1.4
>>>> DNS Servers . . . . . . . . . . . : 198.168.1.10
>>>> 192.168.1.4
>>>> Lease Obtained. . . . . . . . . . : Friday, October 19, 2007
>>>> 8:50:09 AM
>>>> Lease Expires . . . . . . . . . . : Monday, October 22, 2007
>>>> 8:50:09 AM
>>>> Thanks for any help.
>>>> Jim
--
/kj >> Stay informed about: Domain controller not found |
|
| Back to top |
|
| |
| Related Topics: | Windows 2000 domain controller to Win2k3 domain controller - I am currently looking to change a windows 2000 server for a win2k3 server. The old server is the DC, DNS, DHCP and print server. i want the new W2k3 server to be the DC, also the DNS ans DHCP, and have the users login/authenticate to the new server. ...
Domain path not found - Hi All! I have a Windows 2003 server with quite a few XP clients connecting to it fine on a certain network card. If clients try to connect from another subnet to a second network card, they cannot log on to the domain. These clients can ping the..
Windows 2k domain no longer found - I have a windows 2000 domain set up in one room of our company. This consisted of one Windows 2000 server (Domain Controller), and 7 clients - all connected to one hub. This setup was working perfectly. We then decided to extend the network to another...
can not see domain controller - I have installed w2k3 on a server and I cannot add any of the workstations to the domain. I can ping the workstation from the server but not vice versa. I went to the cmd prompt and ran an "arp" to test the media response and I can see the serv...
AD without being a domain controller - Can I install Active Directory on a Windows2K server without being a domain controller? DCPROMO always asks a W2K server to be a domain controller first in order to install Active Directory on the machine. |
|
You can post new topics in this forum
You can reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
|
|
|
FAQ
Search
Profile
Private Messages
Log in
