Re: Domain to Domain Browsing

Tech-Archive recommends: Fix windows errors by optimizing your registry

Thanks guys, for all yur help.

I will try what is suggested as soon as I get back to work on Monday!



"Al Mulnick" <amulnick_No_SPAM@xxxxxxxxxxx> wrote in message
news:uoXRnsZXHHA.4628@xxxxxxxxxxxxxxxxxxxxxxx
We've both suggested duding and netting as ways to help with the
troubleshooting. I think it's time you use them.

But there's a terminology issue we need to clear up before we go too much
further to ensure we're talking about the same things.

"We can browse to shares on the admin domain successfully from any
workstation on the curriculum domain. It's just the curriculum server
that
has the problem trying to get to the admin domain."

When you say you can browse to it, that's NOT the same as being able to
connect successfully. Because you can browse to it, you can see it. After
that, you (as the client in this case) try to connect. The symptom you
describe is that you have a pop-up box that appears and you are unable to
successfully CONNECT to the share (as opposed to browse to it- distinctly
different issues that are sometimes related.)

Since the problem is with authentication, we need to focus the data
gathering on that. Could it still be name related? Yes. But we have to
have a look and find out what's happening at the time of the
authentication to really figure out what the issue is.

Can you run duding and netting? Use the verbose switches so you get
additional information. The more the merrier.
Can you also confirm that a up workstation in the curriculum domain can
successfully attach to the network share in administration that you're
trying to get to from the curriculum domain controller? That's a
significant step. Should be quick to test as well and it should help to
isolate the machines affected.

Al


"ICTSM" <aaa@xxxxxxx> wrote in message
news:54s2osF2185loU1@xxxxxxxxxxxxxxxxxxxxx
One more point of interest...

We can browse to shares on the admin domain successfully from any
workstation on the curriculum domain. It's just the curriculum server
that has the problem trying to get to the admin domain.

Timings are nearly identical on both domains.
As far as I know, this has never been right since the admin/curriculum
domains have been in existence.
There is nothing in the event logs that highlight the problem.
I have tried many authentication accounts to get onto the admin server to
no avail.


"Al Mulnick" <amulnick_No_SPAM@xxxxxxxxxxx> wrote in message
news:eIxJNRTXHHA.1764@xxxxxxxxxxxxxxxxxxxxxxx
No problem, but that does change the issue and hence the
troubleshooting.
As I understand it now, you can find the share, but cannot attach due to
a problem with authentication.

Is that correct? This used to work before?

Some questions to help narrow it down:

If so, what have you done to verify that the trust is operational?
What's changed lately? Add any hotfixes or such? Reboots that you
correlate to the time the problem started? Network changes?
What's in the event logs of interest?
Can you get to other resources from curriculum in administration
successfully? Or are they all broken?
What happens if, when presented with the credentials box you instead put
a user account that has rights from Administration?

My initial thoughts are to check the time skew (easy) and the trust
(easy - NLTEST) to ensure that it's working properly after checking the
event logs on both curriculum dc's and administration dc's. DCDIAG and
NETDIAG are also realatively easy to run and may show the issue much
easier. If that doesn't yield anything then we may have to look
elsewhere.




"ICTSM" <aaa@xxxxxxx> wrote in message
news:54rvg4F22ov17U1@xxxxxxxxxxxxxxxxxxxxx
Yeah, I can browse to the network shares on the admin server via admin
server.

Just to clarify...I can browse to the admin server from our curriculum
server...but cannot open any shares. The username/password box appears
and even when I type in the domain admin credentials for the admin
server, the box just re-appears.

Sorry for the confusion earlier!


"Al Mulnick" <amulnickNo_SPAM@xxxxxxxxxxx> wrote in message
news:euGtlcSXHHA.3500@xxxxxxxxxxxxxxxxxxxxxxx
They're all on the same subnet? And you can't browse the server
shares?
Hmm.... if that's the case, then you may want to do some
troubleshooting to see if you can narrow it down some more.

For example, can you browse the shares you're after on the admin
servers (while logged on at the admin server?)

There are so many things that could be a problem here. Narrowing it
down some might be helpful. Also, have you looked in the event logs to
see if there are any errors related to computer browser?

Al


"ICTSM" <aaa@xxxxxxx> wrote in message
news:54rrujF223l1lU1@xxxxxxxxxxxxxxxxxxxxx
Aw come on guys...take it easy! Ok, so I don't know enough about
topologies and other things.

Both our Admin and curriculum servers are on the same IP range AND
subnet. That LMHosts rings a bell for me though...I'm almost certain
that the techies 'adjusted' some settings. Although I don't knw
what.




"Herb Martin" <news@xxxxxxxxxxxxxx> wrote in message
news:uDeCvOSXHHA.3972@xxxxxxxxxxxxxxxxxxxxxxx

"Al Mulnick" <amulnick_No_SPAM@xxxxxxxxxxx> wrote in message
news:%236WFpgRXHHA.1036@xxxxxxxxxxxxxxxxxxxxxxx
Hence the questions about name resolution topology.

You know that <grin> but there are a large number of people who
incorrectly think that NetBIOS and WINS server no longer
necessary -- and practically all of the people with browsing
problems fall into this trap.
















.

Relevant Pages

  • Re: Domain to Domain Browsing
    ... "We can browse to shares on the admin domain successfully from any ... workstation on the curriculum domain. ... It's just the curriculum server ... There is nothing in the event logs that highlight the problem. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Accessing SBS 2003 Shares with XP Home
    ... I have setup a few xp home clients this way but I have put a new server ... I have tried user password and admin password. ... access shares very easily. ... of the Admin account that was assigned to that share. ...
    (microsoft.public.windows.server.sbs)
  • Re: Netlogon Share and Script Folder missing
    ... All the other Admin ... Shares are there, and working. ... Everyone that has access to the server calims ... that they never deleted the script folder. ...
    (microsoft.public.win2000.active_directory)
  • Re: Accessing SBS 2003 Shares with XP Home
    ... can see in server in network neighborhood. ... I have tried user password and admin password. ... access shares very easily. ... of the Admin account that was assigned to that share. ...
    (microsoft.public.windows.server.sbs)
  • Re: Domain to Domain Browsing
    ... We can browse to shares on the admin domain successfully from any ... workstation on the curriculum domain. ... I have tried many authentication accounts to get onto the admin server to no ...
    (microsoft.public.windows.server.active_directory)