Jump to content

mso

Member
  • Posts

    10
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Hong Kong

Posts posted by mso

  1. I have a difficulty adding a w23k sp1 server to a w2k server domain. Basically, i want to add the w2k server as a member of the w2k server, however, when i tried to add it and got the following messages:

    I could ping from w23K to w2k server. Does anyone can give me an advise? Or is there any information that i need to provide?? I am pretty sure there is nothing wrong with the w2k domain because there are more than 30's pc can join the domain. If there is any information is missed please do let me know so that i could collect it and give it to you guys thank you very much.

    "Note: This information is intended for a network administrator.  If you are not your network's administrator, notify the administrator that you received this information, which has been recorded in the file C:\WINDOWS\debug\dcdiag.txt.

    The domain name XXXXXX might be a NetBIOS domain name. If this is the case, verify that the domain name is properly registered with WINS.

    If you are certain that the name is not a NetBIOS domain name, then the following information can help you troubleshoot your DNS configuration.

    DNS was successfully queried for the service location (SRV) resource record used to locate a domain controller for domain XXXXXX:

    The query was for the SRV record for _ldap._tcp.dc._msdcs.XXXXXX

    The following domain controllers were identified by the query:

    xx.xxx.xx.xxx
    xx.xxx.xx.xxx

    Common causes of this error include:

    - Host (A) records that map the name of the domain controller to its IP addresses are missing or contain incorrect addresses.

    - Domain controllers registered in DNS are not connected to the network or are not running.

    For information about correcting this problem, click Help.
    ";

  2. Hi Mr. Snrub, sorry for the late reply, i did delete and create the pagefile.sys on both C: and D: today. The reason that i did that because it rebooted during weekend again. When i checked memory.dumb this time, the value of the arg3 was 0000000 instead of 00000001. Therefore, I deleted and created the pagefile.sys on both C: and D:.

    Hopefully, it can solve the problem because it is driving me crazy. Between, is there any information that i can get from the memory.dump file?

    Thank you very much

  3. Hi, I have a SAN disk connect to win2k server and i am having problems with Disk Manager. The drive are not showing drive letters but explorer does though. I can access to the SAN drive to create and delete file without any problems?! I just wondering is it possible to assign the same drive letter ( like F:)that is showing in explorer in disk management and without losing data ? Thank you very much

  4. That is what i got the result from !vm?! Is there any information that I can get here? Thank you very much

    kd> !vm

    *** Virtual Memory Usage ***
    Physical Memory: 524148 ( 2096592 Kb)
    Page File: \??\C:\pagefile.sys
    Current: 2097152Kb Free Space: 2090496Kb
    Minimum: 2097152Kb Maximum: 2097152Kb
    Page File: \??\D:\pagefile.sys
    Current: 1048576Kb Free Space: 1029368Kb
    Minimum: 1048576Kb Maximum: 1572864Kb
    Available Pages: 139046 ( 556184 Kb)
    ResAvail Pages: 443069 ( 1772276 Kb)
    Modified Pages: 150 ( 600 Kb)
    NonPagedPool Usage: 6292 ( 25168 Kb)
    NonPagedPool Max: 68609 ( 274436 Kb)
    PagedPool 0 Usage: 15964 ( 63856 Kb)
    PagedPool 1 Usage: 4515 ( 18060 Kb)
    PagedPool 2 Usage: 4494 ( 17976 Kb)
    PagedPool Usage: 24973 ( 99892 Kb)
    PagedPool Maximum: 87040 ( 348160 Kb)
    Shared Commit: 865 ( 3460 Kb)
    Special Pool: 0 ( 0 Kb)
    Free System PTEs: 84685 ( 338740 Kb)
    Shared Process: 4791 ( 19164 Kb)
    PagedPool Commit: 24973 ( 99892 Kb)
    Driver Commit: 1202 ( 4808 Kb)
    Committed pages: 257449 ( 1029796 Kb)
    Commit limit: 1271416 ( 5085664 Kb)

  5. The computer has rebooted randomly in the last few months and i have replaced all the hardwares, like HDD, RAM, cables, power supply and SCSI termination. Now this is my first time using Microsoft ® Windows Debugger Version 6.8.0004.0 X86

    I think I have done everything right up till now... when I open the dump file this is what WinDbg comes up with....BugCheck 77, {c000000e, c000000e, 1, f1a000}

    Furthermore, there was nothing much information that i could find from the event log, I was just able to find one , which was "The previous system shutdown at XXX was unexpected."

    I would like to seek someone here can give me some idea? The following is what i got from the WinDbg:


    Microsoft ® Windows Debugger Version 6.8.0004.0 X86
    Copyright © Microsoft Corporation. All rights reserved.


    Loading Dump File [Z:\MEMORY.DMP]
    Kernel Complete Dump File: Full address space is available

    Symbol search path is: c:\symbols
    Executable search path is:
    Windows 2000 Kernel Version 2195 (Service Pack 4) UP Free x86 compatible
    Product: Server, suite: Enterprise
    Kernel base = 0x80400000 PsLoadedModuleList = 0x80481580
    Debug session time: Tue Mar 25 04:04:50.213 2008 (GMT+8)
    System Uptime: 2 days 14:46:44.929
    Loading Kernel Symbols
    ..................................................................................................
    Loading User Symbols

    Loading unloaded module list
    ..........
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 77, {c000000e, c000000e, 1, f1a000}





    Probably caused by : memory_corruption ( nt!MiMakeOutswappedPageResident+2b9 )

    Followup: MachineOwner
    ---------

    kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    KERNEL_STACK_INPAGE_ERROR (77)
    The requested page of kernel data could not be read in. Caused by
    bad block in paging file or disk controller error.
    In the case when the first arguments is 0 or 1, the stack signature
    in the kernel stack was not found. Again, bad hardware.
    An I/O status of c000009c (STATUS_DEVICE_DATA_ERROR) or
    C000016AL (STATUS_DISK_OPERATION_FAILED) normally indicates
    the data could not be read from the disk due to a bad
    block. Upon reboot autocheck will run and attempt to map out the bad
    sector. If the status is C0000185 (STATUS_IO_DEVICE_ERROR) and the paging
    file is on a SCSI disk device, then the cabling and termination should be
    checked. See the knowledge base article on SCSI termination.
    Arguments:
    Arg1: c000000e, status code
    Arg2: c000000e, i/o status code
    Arg3: 00000001, page file number
    Arg4: 00f1a000, offset into page file

    Debugging Details:
    ------------------






    ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

    DISK_HARDWARE_ERROR: There was error with disk hardware

    BUGCHECK_STR: 0x77_c000000e

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    PROCESS_NAME: System

    LAST_CONTROL_TRANSFER: from 8044018a to 80440aef

    STACK_TEXT:
    f686bd50 8044018a c03d96fc 00000019 00000001 nt!MiMakeOutswappedPageResident+0x2b9
    f686bd7c 8046397d 88dcd300 00000000 00000000 nt!MmInPageKernelStack+0x10e
    f686bd90 80463942 00000000 00000000 00000000 nt!KiInSwapKernelStacks+0x2f
    f686bda8 80454ab6 00000000 00000000 00000000 nt!KeSwapProcessOrStack+0x80
    f686bddc 804692a2 804638c2 00000000 00000000 nt!PspSystemThreadStartup+0x54
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!MiMakeOutswappedPageResident+2b9
    80440aef b102 mov cl,2

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: nt!MiMakeOutswappedPageResident+2b9

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 44925809

    IMAGE_NAME: memory_corruption

    FAILURE_BUCKET_ID: 0x77_c000000e_nt!MiMakeOutswappedPageResident+2b9

    BUCKET_ID: 0x77_c000000e_nt!MiMakeOutswappedPageResident+2b9

    Followup: MachineOwner
    ---------

×
×
  • Create New...