gmichels
asked on
NetBIOS through VPN
The fine folks in my office would like to be able to use their Network Neighborhood at home through the VPN tunnel to browse the network here at the office. They can, at this point, search for a computer by name and it will appear however we cannot seem to be able to get the office domain to appear in Network Neighborhood.
Can anyone help?
Thanks!
Can anyone help?
Thanks!
Les Moore
As long as they can resolve netbios names, simply changing their local workgroup name to match the office LAN workgroup/domain -should- allow them to browse the network through network neighborhood....
ASKER
Most of our folks have home networks, some in workgroups, others in domains. Shouldn't the other workgroups appear in the network neighborhood? Do we need to set up a trust between the domains? Can that be done through a VPN (I tried but the other PDC could not be located)?
Thanks for any help, again.
I'll have someone at the office try changing thier home workgroup.
Thanks for any help, again.
I'll have someone at the office try changing thier home workgroup.
ASKER
I got my answer and it works:
If you have machines which are configured for WINS, and others which are not, the ones which are configured for WINS will fall back to only resolving local names because the hosts which do not have WINS will promote themselves to the local master-browser, which overrides WINS. You would need to have _ALL_ machines on your LAN configured for WINS for this to work over the VPN. I set up ALL the machines at home to use WINS and it works.
Now, the points are yours if you can tell me this. I KNOW it's a common issue but I forget what the "fix" is and the search engine here needs some work.
I go to the machine on the office domain through Network Neighborhood and I get the share problem of need a password for
\\machine\IPC$
I am logged onto my local machine as my office user and password. Do you know the fix?
Thanks.
If you have machines which are configured for WINS, and others which are not, the ones which are configured for WINS will fall back to only resolving local names because the hosts which do not have WINS will promote themselves to the local master-browser, which overrides WINS. You would need to have _ALL_ machines on your LAN configured for WINS for this to work over the VPN. I set up ALL the machines at home to use WINS and it works.
Now, the points are yours if you can tell me this. I KNOW it's a common issue but I forget what the "fix" is and the search engine here needs some work.
I go to the machine on the office domain through Network Neighborhood and I get the share problem of need a password for
\\machine\IPC$
I am logged onto my local machine as my office user and password. Do you know the fix?
Thanks.
On your office domain, enable the "Guest" account. Otherwise, you will have to log into the domain on your remote PC.
ASKER
Sorry. We do not want to enable Guest.
I managed to do it, though. I set up the home box to join the office domain and it did so through the VPN connection. Once that was in place, I could access the shares. Also, I can access home domain through Network Neighborhood just as before from my Win2K box. I don't know if I am supposed to or not but since the accounts were set up before joining the office domain, it's plausible (I have a SID in each place with the same username/password).
I managed to do it, though. I set up the home box to join the office domain and it did so through the VPN connection. Once that was in place, I could access the shares. Also, I can access home domain through Network Neighborhood just as before from my Win2K box. I don't know if I am supposed to or not but since the accounts were set up before joining the office domain, it's plausible (I have a SID in each place with the same username/password).
ASKER
postnote:
I have found that on my W98 boxes on the home LAN, I can access shares on both the office LAN and the home LAN through the VPN if I log into the office domain. If I log into the local domain, the office shares become inaccessible. This helps to keep the kids out of the office LAN! They would need an office username and password, of course.
I have found that on my W98 boxes on the home LAN, I can access shares on both the office LAN and the home LAN through the VPN if I log into the office domain. If I log into the local domain, the office shares become inaccessible. This helps to keep the kids out of the office LAN! They would need an office username and password, of course.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks.
I found that out and that's why I set up the WINS at home for all the machines. I guess the master browser takes precidence over WINS on a LAN. I found that any LANs that connect via VPN need to set up WINS if the remote office uses WINS if they want to access via Network Neighborhood. .
I still have one problem with a home user via VPN. He has Unix boxes and Macs on his home LAN as well...only one PC. He's got his PC set up to use WINS but still his NN doesn't work. Would the Macs or Unix boxes do anything to prevent his NN access? Do they get involved in this master browser/WINS situation?
I am waiting the results of a test - take all the other boxes off the LAN and let me know if the W2K box shows the NN at that point. At least then I'll know for sure.
I found that out and that's why I set up the WINS at home for all the machines. I guess the master browser takes precidence over WINS on a LAN. I found that any LANs that connect via VPN need to set up WINS if the remote office uses WINS if they want to access via Network Neighborhood. .
I still have one problem with a home user via VPN. He has Unix boxes and Macs on his home LAN as well...only one PC. He's got his PC set up to use WINS but still his NN doesn't work. Would the Macs or Unix boxes do anything to prevent his NN access? Do they get involved in this master browser/WINS situation?
I am waiting the results of a test - take all the other boxes off the LAN and let me know if the W2K box shows the NN at that point. At least then I'll know for sure.
ASKER
Closing the question.
Situations resolved
Situations resolved