Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 236
  • Last Modified:

Trust Relationship - Net Use Question

Windows 2000 - I have a user on domain "cat" that is currently visiting a field office.  This field office is on domain "dog"

cat and dog domains DO NOT have a trust relationship

I created an account for user on "dog" domain

Set WNS and DNS with both "cat" and "dog" TCP domain accounts.  Left gateway blank.

User is logged into "cat" domain and can see servers on "cat" domain.  Cannot see "dog" domain.

While I can ping "dog" domain when I go to start run
\\dog
get error that domain is locked and not accessible

Tried mapping drive to \\dog and get error "path not found"

So - tried using net use at the command line
syntax:
Y: \\dog\files /user:dog\jsmith
Get error domain not found

Is my syntax wrong?  Is it even possible to access files on a domain in which there is no trust relationship?

0
tituba2
Asked:
tituba2
  • 3
  • 2
  • 2
  • +3
1 Solution
 
darrenburkeCommented:
you left the gateway blank?  Are both domains on the same network/subnet?



0
 
LongbowCommented:

Without the thrust relationship you are not known from the other domain

Use the following command

net use x: \\Server\Share * /u:domain\username
"domain" may be a computername and server an ip

Longbow

0
 
jhanceCommented:
You're question is all confused and I think the reason is that you don't understand the relationship between networks, domains/trusts, and network services.

I'm not even sure where to start....

1) You must have a viable PHYSICAL network connection in place.  So be sure you are plugged into an active network port.

2) You must have a viable LOGICAL network connection in place.  In this case you seems to be using (or trying to use) TCPIP.  For TCPIP to work you MUST HAVE an IP address, a network MASK, and a GATEWAY.  If you left the gateway blank then ALL HOSTS you try to contact MUST BE ON THE LOCAL SUBNET as specified by the network MASK.  It would be VERY UNUSUAL to have a blank gateway.  Once TCPIP is working correctly you should be able to PING another host by IP address.

3) You must have a working name resolution and the most common here is DNS.  You need a DNS server and you need to set that up in the network control panel.  Once that is setup you should be able to PING by NAME.

4) For Window networking to work by name you must have WINS working.  WINS is similar to DNS but is specific to Windows networking.  If you specify a host like \\hostname\sharename, you are asking WINS or an alternate Windows name resolution service to figure out who "hostname" is.  Since you mentioned WINS I'm assuming you have a WINS server and know its IP address.

5) Now you are in a position to authenticate to the domain and this is all that NT DOMAINs are responsible for.  Basically logging you in and thereby controlling access to the Domain resources.  If you have no trust between cat and dog you must JOIN the domain before you can logon to it.  Once you join dog, you are no longer a member of cat.  You can only then logon to cat if you again join cat.  You cannot be a member of more than one domain at a time.
0
Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
tituba2Author Commented:
1.  Yes, I have a physical connection to the network
2.  Cat and Dog are on different subnets.  I tried putting their gateway and it did not make a difference
3.  I CAN ping "dog" by name and TCP.  What I cannot do is
then open folders on the dog domain
4.  WNS is working as I can ping both by name and TCP

What I cannot seem to do is join "dog" domain.


Longbow
This syntax produces error "domain not found"
0
 
jhanceCommented:
How are you attempting to joing the "dog" domain?

If the error is that the domain is not found then the domain is not found.  You are giving it the wrong name or in fact there is no domain by such a name.
0
 
LongbowCommented:
Are your shares corrects ?
Are they not hidden ?
Have you tried "net use" with the IP server ?


maybe some help :
http://support.microsoft.com/support/kb/articles/Q102/9/08.ASP

Longbow
0
 
msctecCommented:
Just create the trust.
0
 
tituba2Author Commented:
Can't create the trust - corporate decision.  They don't want a trust between these two domains.  They just send "visitors" here and want them to access both domains....you know the song

My shares are correct and user has permissions for the shared folder.
0
 
msctecCommented:
Thats the whole point of a trust. If you don't set up the trust you won't get to see the domain. You can ping it because it is just an ip address. There is no firewall blocking out pings or ip adress ranges. No trust - no access.
0
 
pssiewCommented:
have you considered ftp access ?
since you can't have a trust, ftp would also work. it will be bit more admistrative work

hope this helped
0
 
LongbowCommented:
tituba2,

The 1rst answer you receive already tell you you need a thrust relationship. What's wrong ?
0

Featured Post

Ask an Anonymous Question!

Don't feel intimidated by what you don't know. Ask your question anonymously. It's easy! Learn more and upgrade.

  • 3
  • 2
  • 2
  • +3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now