[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

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

unable to browse the network

When connected to my 'work' via RAS dial-up connection I am
not able to see network drives in Network neighborhood.  What are the steps to ensure that I have this correctly
configured?  I do have a TCP/IP connection that works, but
I think that I need netbeui to access the LAN which is running  a bunch of NT 3.51 servers.  I suspect my problem
is related to the workgroup name but who knows???
0
lw
Asked:
lw
  • 6
  • 5
1 Solution
 
j2Commented:
NetBeui isnt nescesary.. but it helps.. Thing is, if you are in a different workgroup then the one at work, it can take a LONG time before you see the other groups. Try to map a network drive and "manually" enter the path to one of your servers... If that works, it is all a mather of waiting until the browsing works. Or you could set your home workgroup to the same as the one at work which will expedite the browsing.
0
 
lwAuthor Commented:
I need more information about workgroups.  How do I change it?
Also, I seem to remember the Win95 login showing the workgroup.
My Win95 login only shows user and password.  Is this what is
causing my problems with the network neighborhood?
0
 
lwAuthor Commented:
Yes I checked someone else's login and theirs shows 'domain'.
Mine does not.  Is it related to doing a net login vs Windows
login?  Can someone explain if this is my problem?  
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
lwAuthor Commented:
Yes I checked someone else's login and theirs shows 'domain'.
Mine does not.  Is it related to doing a net login vs Windows
login?  Can someone explain if this is my problem?  
0
 
j2Commented:
That is definitely a reason: If they are running a domain, WindowsNT will not grant acces for ANY computer not officially in the domain. So you must set it for domain logon and "Create account in the domain" If this doesnt work, your admin must manuallly add your machine to the domain.
0
 
j2Commented:
That is definitely a reason: If they are running a domain, WindowsNT will not grant acces for ANY computer not officially in the domain. So you must set it for domain logon and "Create account in the domain" If this doesnt work, your admin must manuallly add your machine to the domain.
0
 
lwAuthor Commented:
j2 - How do I set it up for domain logon from my client?  I am
already setup on the LAN for access, but need to reflect that on
my client. I need step by step for this procedure.  I definitely
think this is the right track!
0
 
j2Commented:
control panel/networks/MS Network Client
and just check the "log on to NT domain" and enter the name of the domain (case sensitive i think)
0
 
lwAuthor Commented:
I have 'checked' the log on to NT domain and added the domain
name as stated, but when I reboot my system to logon, I do not
see a box with user, password, domain (as I would expect).  I am
missing the domain.  I this a registry problem?  

Can I remove the network 'stuff' and reinstall it (how) to resolve this?  Or is there another way?  Something is missing
when I logon.  It looks like it is not doing a network logon.
0
 
j2Commented:
Under W95, you wont se a "domain" entry... W95 is to stupid to handle roaming ;) If it wasnt working, it would tell you....
0
 
lwAuthor Commented:
Why is this a paq?  My problem is still open for discussion!
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 6
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now