Windows Networking -- aaarrrrghghghgh!!!!
by OK, I know absolutely nothing about windows networking (groups, domains, blehhh, blehh.) Basically I know that if I want to share folders and printers on my home network (of Windows 2k computers) I make sure they are all on the same group.
Here's the problem: What if I want to take a laptop that is configured for my employer's DOMAIN and access the shared folders on my HOME computer (that's in a group)?
I can't make too many changes to the laptop, because I don't want to mess up the configuration and not be able to use the computer at work.
AI Summary
23 Comments
ok so I got this working. it was so easy once you guys said to just use the ip. on the client laptop, I just mapped a drive to //192.x.x.x/C$ and clicked the "connect as different user" and entered the user name and password of the main user on the "server" box. all cool. was able to browse folders and play streaming audio.
Problem: everytime the laptop reboots (and is connected to the home network) it asks for the password to connect to the network drives. (it claims it changed or something) anyone know whats going on?
i get sort of a related problem like this every once in a while, instead of trying to figure out why win2k gives me such garbage, i create an account on server (the one you are mapping a drive to) that has the same exact username and password on the client. The client automatically tries your currently logged in uname and pw when accessing restricted shares. The other way around this is to allow Guest no password access (security risk without a firewall/router)
pee on it
that never works at my house...stupid B vitamins
yeah instead of logging into the domain (option in the logon screen), logon locally to the computer, then as iwz said: \\ip_or_name\ and it will list your shares. enjoy
You're saying I can't login to the domain on the laptop and then search for the share? I have to login to the *(this computer)* option to do this?
Because I think I remember I couldn't login to *(this computer)* for some reason (it's not my laptop). only logging into the domain worked.
Im assuming you want to take a notebook home to access your home network and the client shares on that network...
If the laptop is setup for DOMAIN, and there is no primary domain server, there's no way you can login to that machine because authentication is coming from a server (the domain controller).
But logging into "this computer" will bypass the domain and use your notebook as a regular workstation (as if you were part of just a workgroup).
I can login to my laptop with the "Log on to:" value set to the DOMAIN when its not connected to anything.
Authentication is not coming from a server in this case, unless by some magical phenomenon.
That's interesting I was lead to believe that usually for a DOMAIN, the only way to access the DOMAIN's resources would be resolved through a domain controller (since local authentication would make no sense at that point), so I thought most would setup a domain with server authentication.
Well, regardless, if you hook that notebook to the network at home, you'll probably see errors concerning not able to connect to DOMAIN for certain things, BUT you can still browse a local workgroup, and access machine shares.
FYI
Directly accessing by IP bypasses all that workgroup nonsense. Workgroups can cause some trouble in domains, you might not see workgroups because some administrators disable that service that announces workgroup and client information because it kills a domain (especially 98 clients, I've had one bring down a server and domain every 2 hours) (LAN master me thinks its called).
Which also reminds me, you might have to reconfigure the notebook with the correct subnet static IP or hopefully it fetches an IP from your router (assuming you have one)
the notebook gets a dynamic ip from DHCP of the router.
that all works cool, its just the windows-specific (share) stuff I was having trouble with.
yeah, I'm gonna try the ip way. I wasn't aware you could access share's by ip. so that's cool.
you can also configure the UNC computer name to an IP manually by using the LMHOSTS file (sits next to the HOSTS file). that will let you type in a computer name without it actually having refreshed all the windows networking names yet
yeah, the domain login is cached locally so you can login when not connected to the domain.
they really don't have to be in the same domain or workgroup. if they're not showing up in network neighborhood, just do a Search for Computer.
or in explorer: \\ip.add.rr.ess\share
create a workgroup at home, and just change the workgroups whenever you feel the need son
already did that. didn't work.
thats not hard at all
i did that with my laptop..
however i had it set up with my home network at home..
and just used it as a client in a workgroup when i connected it at work...
"however i had it set up with my home network at home"
most. uninformative. help. ever.