General discussion

Locked

Weird XP Pro WS & WinServ2K domain prob

By datakid ·
I am on a small domain (15 winxp pro/win2k WS, 1 win serv2k DC/file share) and have no problems logging into the domain, my mapped drive is there, and I can browse the files on that mapped drive, I'm even installing things off it.

The problem is that when I go to My Network Places->Entire Network->MS WIN Network->Natoffice(the domain) I can't get any further - it says it has "0 objects".

If I open a new explorer, and type \\server into the address, it comes up fine, I can browse the server, and then it appears in the domain, but no other computers do. They all disappeared about two weeks ago I think, but it didn't seem to be causing any problems (as I could still see my mapped drive, etc), so I ignored it (my bad). I have no idea what I might have done.

Other computers can see all on domain, and they also have "workgroup" listed in the MS Win Network folder, but I don't. We don't use the Workgroups for anything, it's all domain based. I get no error messages.

I'm used to linux, so this is quite weird and new for me, and I'm having to learn Win OS on the fly.

I have rebooted both machines to no effect.

This conversation is currently closed to new comments.

16 total posts (Page 1 of 2)   01 | 02   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

by BFilmFan In reply to Weird XP Pro WS & WinServ ...

Is this an Active Directory domain?

When you open Active Directory Users and Computers what do you see?

This may be a browse issue, rather than a domain issue. Need more information to be of assistance.

Collapse -

by datakid In reply to

Poster rated this answer.

Collapse -

by datakid In reply to Weird XP Pro WS & WinServ ...

Yes, this is an AD.

"When you open Active Directory Users and Computers what do you see?"

I see "console root:\_AD Users + comp|_natoffice.wilderness.org.au"

When I expand that, I get Builtin, Computers (all are visible), DC (fserver), ForeignSecPrincips, Lost+Found, System and Users (all users visible, and some global and domain local security groups).

I am an admin, with full control. I usually use
"Administrative Tools" from this XP pro WS (the one with the missing domain objects - it's my own WS).

Collapse -

by datakid In reply to Weird XP Pro WS & WinServ ...

I should also note that XP WS is completely up to date re Window's Update, and Win2k server is missing .Net hotfix, because .Net is not installed properly. I'll get to that eventually

Collapse -

by datakid In reply to Weird XP Pro WS & WinServ ...

Point value changed by question poster.

Collapse -

by BFilmFan In reply to Weird XP Pro WS & WinServ ...

Okay next step is to log onto the domain controller. Make sure the support tools for 2000 are installed and run this command line from a prompt:

dcdiag /v /e /f:dcdiagLOG.txt /ferr:dcdiagERROR.txt

Check the dcdiag report for any issues.

If you type the command net view >view.report do you see a list of computers/shares when you view that list?

Collapse -

by BFilmFan In reply to

I am positive this is a Browser Issue. I recommend you follow the steps listed in this article:

http://www.chicagotech.net/browser.htm

Collapse -

by datakid In reply to

Poster rated this answer.

Collapse -

by sgt_shultz In reply to Weird XP Pro WS & WinServ ...

turn back on netbios over tcpip.
so what box went on the network 2 weeks ago? this xp box? some other dual-homed box?
bfilm is genius and has put finger it imho.
read that final link he gave you and if i may i will elaborate. give the points to him, kay?
when he says you have browser issue, he does not mean html browser (IE,netscape) he means the windows browser service.
it is a complicated, uh, protocol, windows has for maintaing list of workgroup computers. if you want good hoot, check out the steps and tools for troubleshooting the browser service and you will see a complex thing that your network depends on that has become fragile due mostly imho to xp doesn't play nice unless *all* client are xp.
wait for it:
thnx bill
in a workgroup you are not supposed to *have* to have any computers on all the time (like a server). so by default all your wokrgroup clients are capable of becoming the Master Browser if the master browser is off.
bfilms link explains it.
the way ms set it up, certain important network functions, the ones that don't work in your post, need to use a list of computers (browser list) provided by a 'Master Browser' computer. since at any give time the Master Browser computer might be off, there is an elaborate pretty funny actually scheme to 'elect' a new Master Browser if the current one is unavailable. lots and lots of unnecessary network traffic. lots of potential to not work right.
what your symptoms suggest to bfilm is that some computer is winning the master browswer election but not operating correctly as the master browser. browsing is broken. the MB is NG
you should have some events in the event viewer on a client showing the problem.
so you can shotgun this by going to computers you suspect (since they came onto the network recently) and turning off their ability to become master browsers. see howto at support.microsoft.com
and Search for your symptoms

Collapse -

by datakid In reply to Weird XP Pro WS & WinServ ...

When I ran the command line dcdiag that you told me too, I got this response from the computer:

"The oricedure entry point DsIsMangledDnW could not be located in the dynamic link library NTDSAPI.dll"?

I've not had as much time to work on this as I would have liked, but I'll get there slowly.

Back to Networks Forum
16 total posts (Page 1 of 2)   01 | 02   Next

Related Discussions

Related Forums