I completely disagree with any kind of IN PLACE UPGRADE from NT4 to W2K, as if something unforeseen were to arise what's your "go to hell plan", meaning that if you botch something you'll need that NT4 machine to fall back on. I just did the swap over myself and found that you have to make 100% sure that all the services are working fully, especially WINS and DNS, in fact I stopped running DNS as a service on the server because I found it was causing me more Nbt issues then it was worth, besides I already has a server running DNS perfectly fine. I am positive that it's not a defect in MS' networking model, rather it's more of a security issue, specifically with NetBIOS and not allowing users to just view the Network Neighborhood, but only map a drive. I did a lot of research on this (K.B.) and asked this list how to allow them to view the Network Neighborhood, but after giving more in-depth thought on the subject found it was better that I only give the RRAS users access to only what they need access to.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:Dflorea@;privateconsulting.com] Sent: Wednesday, November 06, 2002 10:26 AM To: NT 2000 Discussions Subject: RE: Dialup Users What is your DNS/WINS/Hosts file configuration? I doubt this is a defect in MS' networking model, almost assuredly a name resolution issue. Can you upgrade your NT4 box in place to W2K? I think you'd find life a little easier. -----Original Message----- From: Adam Smith [mailto:adam.smith@;sageautomation.com] Sent: Tuesday, November 05, 2002 3:26 PM To: NT 2000 Discussions Subject: Dialup Users We have a Windows NT 4.0 PDC which is also our main file server. We also have a Windows 2000 server which is serving RAS. When users dial up and authenticate using RAS, they all try and connect to our main file server by putting '\\server' (Don't blame me -- I didn't name it =)) into their Location bar in Windows Explorer. This is not an issue, as it is a perfectly valid way of browsing network shares. Unfortunately majority of the time, these users can either NOT resolve the name 'server' or they can only see one or two shares on that server. Today for example, one user rang me while dialled up saying he could only see the "Data" share when he should have been presented with at least four shares. He was attempting to access a share called "Resources." I told the user to map a drive manually, with "net use Z: \\server\resources." The map was unsuccessful, as the specified share could not be seen. Running "Net View" displayed only the "Data" share. I then instructed the user to do a "Net View \\192.168.0.2," and the remote user was presented with *ALL* the shares he should have seen. He then had to map a drive to the IP address of the box, rather than its NetBIOS name. All I could think was "What a joke." I've seen this so, so many times, and I find it totally rediculous. To me, this proves that if I were to write up an OSI Checklist I'd get the following: DEAD Application DEAD-ISH? Presentation :) Session :) Transport :) Network :) Data Link :) Physical if all the rest are working, it *HAS* to be a fault of the Microsoft Networking model. What else could it be? -- Adam Smith Information Technology Officer SAGE Automation Ltd. [EMAIL PROTECTED] http://www.sageautomation.com Phone: (08) 8276 0703 Fax: (08) 8276 0799 Mobile: 0414 895 273 ------ You are subscribed as [EMAIL PROTECTED] Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe send a blank email to %%email.unsub%% ------ You are subscribed as [EMAIL PROTECTED] Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe send a blank email to %%email.unsub%% ------ You are subscribed as [email protected] Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe send a blank email to [EMAIL PROTECTED]
