Re: cannot log into computer, exchange down, dns issues
- From: "victor" <victorl@xxxxxxxxxx>
- Date: Thu, 12 Jan 2006 23:07:58 GMT
Merv,
To answer your questions, we are using ts in remote admin mode, and I right
now, we can't try too see if another admin account will work, since it is
(seemingly) back to normal now...
regards,
Victor.
"Merv Porter [SBS-MVP]" <mwport@xxxxxxxxxxxxxxxxxxx> wrote in message
news:OJPiFUsFGHA.1676@xxxxxxxxxxxxxxxxxxxxxxx
> Does the problem occur if you log onto the server with a different admin
> account?
>
> And just curious... In your original post, you said:
>
> > terminal server sessions open, but remain black (dead)...
>
> Is the SBS server being used as a Terminal Server in Application mode?
>
> --
> Merv Porter [SBS MVP]
> ===================================
>
> "victor" <victorl@xxxxxxxxxx> wrote in message
> news:wS%wf.213378$V7.122726@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> > Thanks for the fast reply Merv,
> >
> > No we do not (should not...) have any users dialling in via VPN.
> >
> > Could there be anything else triggering these problems?
> > The problems have started at:
> > 7:20am 11 jan
> > 6:41pm 10 jan
> > 3:50am 10 jan
> > 3:12pm 09 jan
> > 8.46am 09 jan
> > 9:30am 02 jan
> > and a few times before that, but approx 2 weeks+ apart.
> >
> > These times do not seem to coincide with anything we have scheduled to
run
> > on our server.
> >
> > Thank you for the link, but I have already read it... i couldn't find
> > anything relevant. nbtstat had never shown any conflicts, including when
i
> > run it just after we receive the message.
> >
> > We have not installed sbs sp1, so i will check out hotfix KB292822 and
get
> > back to you.
> >
> > Cheers,
> >
> > Victor.
> >
> >
> > "Merv Porter [SBS-MVP]" <mwport@xxxxxxxxxxxxxxxxxxx> wrote in message
> > news:OdVamLmFGHA.1124@xxxxxxxxxxxxxxxxxxxxxxx
> >> Do you have users dialing in using a VPN?
> >>
> >>
> >
http://www.eventid.net/display.asp?eventid=4319&eventno=554&source=NetBT&phase=1
> >> As per M292822: "This error occurs when:
> >> 1. Routing and Remote Access Service (RRAS) is configured to permit
> > incoming
> >> connections.
> >> 2. Domain Name System (DNS) is installed and configured locally".
> >>
> >> See also the Dell group thread for some wery helpful information.
> >>
> >> In my example, my Windows 2000 Advanced Server at 192.168.0.10 was
> >> picking
> >> up 192.168.0.100 from the Remote Access system as soon as someone
dialed
> > in;
> >> this broke WINS (running on the same server), causing the conflict.
> >> Rebooting would temporarily fix it until someone dialed in. "nbtstat"
> > showed
> >> "conflict" under the <20> and <00> unique fields.
> >> -----------------
> >>
> >> So, apply the hotfix and registry edit in KB292822... (if you have SBS
> > 2000
> >> SP1 installed, the hotfix should have installed with it but the
registry
> >> edits must still be done)
> >> Name resolution and connectivity issues on a Routing and Remote Access
> >> Server that also runs DNS or WINS
> >> http://support.microsoft.com/default.aspx?scid=kb;en-us;292822
> >>
> >> --
> >> Merv Porter [SBS MVP]
> >> ===================================
> >> "victor" <victorl@xxxxxxxxxx> wrote in message
> >> news:RF_wf.213322$V7.206758@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> >> > Hi,
> >> >
> >> > We are experiencing some major problems with our sbs2k server:
> >> > After typing in the domain admin user/pass at the login prompt, the
> > prompt
> >> > disappears leaving a light blue screen. The computer stays at this
> > screen
> >> > and will remain unresponsive until the power is switched off
manually.
> >> > Before turning it off, we are able to access the shared folders on it
> >> > (although slow), terminal server sessions open, but remain black
(dead)
> >> > and
> >> > backup jobs will run, although they will not fully complete. Exchange
> >> > is
> >> > down.
> >> > After the server is turned back on, it runs normally again, until the
> >> > issue
> >> > recurs, which is usually the following morning.
> >> >
> >> > While the computer is running, I have been examining the event logs
and
> > I
> >> > have discovered the following:
> >> > at seemingly random times, we get three instances of DNS error event
id
> >> > 4004, and 5 minutes later, followed by recurring instances of DNS
error
> >> > event id 4000, every 5 minutes.
> >> >
> >> > The three instances of event 4004 relate to "enumeration of zone ..",
> >> > "enumeration of zone 0.168.192.in-addr.arpa", "enumeration of zone
> >> > <ourdomain>.local".
> >> >
> >> > Event Type: Error
> >> > Event Source: DNS
> >> > Event Category: None
> >> > Event ID: 4004
> >> > Date: 11/01/2006
> >> > Time: 7:20:52 AM
> >> > User: N/A
> >> > Computer: JSRSBS01
> >> > Description:
> >> > The DNS server was unable to complete directory service enumeration
of
> >> > zone
> >> > .. This DNS server is configured to use information obtained from
> > Active
> >> > Directory for this zone and is unable to load the zone without it.
> > Check
> >> > that the Active Directory is functioning properly and repeat
> >> > enumeration
> >> > of
> >> > the zone. The event data contains the error.
> >> > Data:
> >> > 0000: 2a 23 00 00 *#..
> >> >
> >> >
> >> > Event Type: Error
> >> > Event Source: DNS
> >> > Event Category: None
> >> > Event ID: 4000
> >> > Date: 11/01/2006
> >> > Time: 7:27:47 AM
> >> > User: N/A
> >> > Computer: JSRSBS01
> >> > Description:
> >> > The DNS server was unable to open Active Directory. This DNS server
is
> >> > configured to obtain and use information from the directory for this
> > zone
> >> > and is unable to load the zone without it. Check that the Active
> >> > Directory
> >> > is functioning properly and reload the zone. The event data is the
> >> > error
> >> > code.
> >> > Data:
> >> > 0000: 3a 00 00 00 :...
> >> >
> >> >
> >> >
> >> > Also, in our FRS log, we get the following:
> >> >
> >> > Event Type: Warning
> >> > Event Source: NtFrs
> >> > Event Category: None
> >> > Event ID: 13562
> >> > Date: 11/01/2006
> >> > Time: 7:21:35 AM
> >> > User: N/A
> >> > Computer: JSRSBS01
> >> > Description:
> >> > Following is the summary of warnings and errors encountered by File
> >> > Replication Service while polling the Domain Controller
> > jsrsbs01.jsr.local
> >> > for FRS replica set configuration information.
> >> >
> >> > Could not find computer object for this computer. Will try again at
> >> > next
> >> > polling cycle.
> >> >
> >> >
> >> >
> >> > In our Directory service, we receive NTDS General warning event 1655
> >> > and
> >> > error event 1126:
> >> >
> >> >
> >> >
> >> > Event Type: Warning
> >> > Event Source: NTDS General
> >> > Event Category: Global Catalog
> >> > Event ID: 1655
> >> > Date: 11/01/2006
> >> > Time: 10:46:47 AM
> >> > User: Everyone
> >> > Computer: JSRSBS01
> >> > Description:
> >> > The attempt to communicate with global catalog \\jsrsbs01.jsr.local
> > failed
> >> > with the following status:
> >> >
> >> > The RPC server is unavailable.
> >> >
> >> > The operation in progress might be unable to continue. The directory
> >> > service will use the locator to try find an available global catalog
> >> > server
> >> > for the next operation that requires one.
> >> >
> >> > The record data is the status code.
> >> > Data:
> >> > 0000: ba 06 00 00 º...
> >> >
> >> >
> >> >
> >> > Event Type: Error
> >> > Event Source: NTDS General
> >> > Event Category: Global Catalog
> >> > Event ID: 1126
> >> > Date: 11/01/2006
> >> > Time: 10:46:47 AM
> >> > User: Everyone
> >> > Computer: JSRSBS01
> >> > Description:
> >> > Unable to establish connection with global catalog.
> >> >
> >> >
> >> > Also, we are receiving 3 W3SVC warnings whenever we boot the server:
> >> >
> >> > Event Type: Warning
> >> > Event Source: W3SVC
> >> > Event Category: None
> >> > Event ID: 101
> >> > Date: 11/01/2006
> >> > Time: 11:11:40 AM
> >> > User: N/A
> >> > Computer: JSRSBS01
> >> > Description:
> >> > The server was unable to add the virtual root '/public' for the
> > directory
> >> > 'M:\jsr.com.au\Public Folders' due to the following error: The system
> >> > cannot
> >> > find the path specified. The data is the error code.
> >> > For additional information specific to this message please visit the
> >> > Microsoft Online Support site located at:
> >> > http://www.microsoft.com/contentredirect.asp.
> >> > Data:
> >> > 0000: 03 00 00 00 ....
> >> >
> >> > Event Type: Warning
> >> > Event Source: W3SVC
> >> > Event Category: None
> >> > Event ID: 101
> >> > Date: 11/01/2006
> >> > Time: 11:11:40 AM
> >> > User: N/A
> >> > Computer: JSRSBS01
> >> > Description:
> >> > The server was unable to add the virtual root '/Exchange' for the
> >> > directory
> >> > 'M:\jsr.com.au\MBX' due to the following error: The system cannot
find
> > the
> >> > path specified. The data is the error code.
> >> > For additional information specific to this message please visit the
> >> > Microsoft Online Support site located at:
> >> > http://www.microsoft.com/contentredirect.asp.
> >> > Data:
> >> > 0000: 03 00 00 00 ....
> >> >
> >> >
> >> > Event Type: Warning
> >> > Event Source: W3SVC
> >> > Event Category: None
> >> > Event ID: 101
> >> > Date: 11/01/2006
> >> > Time: 11:11:40 AM
> >> > User: N/A
> >> > Computer: JSRSBS01
> >> > Description:
> >> > The server was unable to add the virtual root '/Exadmin' for the
> > directory
> >> > '\\.\BackOfficeStorage' due to the following error: The system cannot
> > find
> >> > the path specified. The data is the error code.
> >> > For additional information specific to this message please visit the
> >> > Microsoft Online Support site located at:
> >> > http://www.microsoft.com/contentredirect.asp.
> >> > Data:
> >> > 0000: 03 00 00 00 ....
> >> >
> >> >
> >> > The following is the output from IPCONFIG /ALL of our sbs2k server:
> >> > Windows 2000 IP Configuration
> >> >
> >> > Host Name . . . . . . . . . . . . : jsrsbs01
> >> > Primary DNS Suffix . . . . . . . : jsr.local
> >> > Node Type . . . . . . . . . . . . : Hybrid
> >> > IP Routing Enabled. . . . . . . . : No
> >> > WINS Proxy Enabled. . . . . . . . : No
> >> > DNS Suffix Search List. . . . . . : jsr.local
> >> >
> >> > Ethernet adapter Local Area Connection Gb:
> >> >
> >> > Connection-specific DNS Suffix . :
> >> > Description . . . . . . . . . . . : Intel(R) PRO/1000 MT
Server
> >> > Adapter
> >> > Physical Address. . . . . . . . . : 00-04-23-B9-AF-15
> >> > DHCP Enabled. . . . . . . . . . . : No
> >> > IP Address. . . . . . . . . . . . : 192.168.0.2
> >> > Subnet Mask . . . . . . . . . . . : 255.255.255.0
> >> > Default Gateway . . . . . . . . . : 192.168.0.1
> >> > DNS Servers . . . . . . . . . . . : 192.168.0.2
> >> >
> >> >
> >> > We are also running a file and application server which is running
> > windows
> >> > advanced server 2k. We are receiving the following errors whenever we
> > are
> >> > experiencing problems with the sbs2k server:
> >> >
> >> > A netBT error event 4319:
> >> >
> >> > Event Type: Error
> >> > Event Source: NetBT
> >> > Event Category: None
> >> > Event ID: 4319
> >> > Date: 11/01/2006
> >> > Time: 11:03:03 AM
> >> > User: N/A
> >> > Computer: JSRFS01
> >> > Description:
> >> > A duplicate name has been detected on the TCP network. The IP
address
> > of
> >> > the machine that sent the message is in the data. Use nbtstat -n in a
> >> > command window to see which name is in the Conflict state.
> >> > Data:
> >> > 0000: 00 00 04 00 01 00 54 00 ......T.
> >> > 0008: 00 00 00 00 df 10 00 c0 ....ß..À
> >> > 0010: 01 01 00 00 00 00 00 00 ........
> >> > 0018: 00 00 00 00 00 00 00 00 ........
> >> > 0020: 00 00 00 00 00 00 00 00 ........
> >> > 0028: 02 00 a8 c0 ..¨À
> >> >
> >> > (which shows the message is coming from 192.168.0.2 which is our
sbs2k
> >> > server)
> >> >
> >> >
> >> > and a Browser error event 8019:
> >> >
> >> > Event Type: Error
> >> > Event Source: BROWSER
> >> > Event Category: None
> >> > Event ID: 8019
> >> > Date: 11/01/2006
> >> > Time: 10:39:23 AM
> >> > User: N/A
> >> > Computer: JSRFS01
> >> > Description:
> >> > The browser was unable to promote itself to master browser. The
> >> > browser
> >> > will continue to attempt to promote itself to the master browser, but
> > will
> >> > no longer log any events in the event log in Event Viewer.
> >> > Data:
> >> > 0000: 34 00 00 00 4...
> >> >
> >> >
> >> > When the SBS2k machine is 'restarted' and the problems go away, so
too
> > do
> >> > the netbt and browser error on the file server. Below is the output
of
> >> > IPCONFIG /ALL for the file server:
> >> >
> >> > Windows 2000 IP Configuration
> >> >
> >> > Host Name . . . . . . . . . . . . : jsrfs01
> >> > Primary DNS Suffix . . . . . . . : jsr.local
> >> > Node Type . . . . . . . . . . . . : Broadcast
> >> > IP Routing Enabled. . . . . . . . : No
> >> > WINS Proxy Enabled. . . . . . . . : No
> >> > DNS Suffix Search List. . . . . . : jsr.local
> >> >
> >> > Ethernet adapter JSR Local Connection:
> >> >
> >> > Connection-specific DNS Suffix . :
> >> > Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit
> >> > Ethernet
> >> > Physical Address. . . . . . . . . : 00-0C-76-A0-0B-12
> >> > DHCP Enabled. . . . . . . . . . . : No
> >> > IP Address. . . . . . . . . . . . : 192.168.0.3
> >> > Subnet Mask . . . . . . . . . . . : 255.255.255.0
> >> > Default Gateway . . . . . . . . . : 192.168.0.1
> >> > DNS Servers . . . . . . . . . . . : 192.168.0.2
> >> >
> >> >
> >> > We have searched far and wide for a solution to this issue, but
> > everything
> >> > we have found relates to smaller pieces of the puzzle and does not
> > resolve
> >> > anything. We have verified and re-verified our DNS settings, and
tried
> >> > every
> >> > solution we could find. We even performed an authoritative restore on
> >> > AD
> >> > on
> >> > the sbs2k server and a non-authoritative restore on the file server.
> >> >
> >> > Any help would be very much appreciated!
> >> > many thanks in advance!
> >> >
> >> > kind regards,
> >> >
> >> > Victor
> >> >
> >> >
> >>
> >>
> >
> >
>
>
.
- References:
- cannot log into computer, exchange down, dns issues
- From: victor
- Re: cannot log into computer, exchange down, dns issues
- From: Merv Porter [SBS-MVP]
- Re: cannot log into computer, exchange down, dns issues
- From: victor
- Re: cannot log into computer, exchange down, dns issues
- From: Merv Porter [SBS-MVP]
- cannot log into computer, exchange down, dns issues
- Prev by Date: Re: cannot log into computer, exchange down, dns issues
- Next by Date: Re: cannot log into computer, exchange down, dns issues
- Previous by thread: Re: cannot log into computer, exchange down, dns issues
- Next by thread: Microsoft Security Bulletin MS06-003
- Index(es):
Relevant Pages
|
