Windows 2000 & .Net mag had an interesting WMI script that would fire your user's login script after establishing a RAS connection in this month's mag.
------------------------------------------------------ Roger D. Seielstad - MCSE Sr. Systems Administrator Inovis - Formerly Harbinger and Extricity Atlanta, GA > -----Original Message----- > From: Adam Smith [mailto:adam.smith@;sageautomation.com] > Sent: Thursday, November 07, 2002 6:01 PM > To: NT 2000 Discussions > Subject: RE: Dialup Users > > > Some responses to various questions: > > > You don't have any HOSTS or LMHOSTS on any of these clients, > > do you? If the IP works but the UNC name doesn't, it must be > > a name resolution issue somewhere. > > The UNC name resolution works, but it's the visibility of the shares > that's the problem. Users can connect to \\SERVER, but can *only* see > the Data share. When they are looking at the box from an IP > perspective, ie "NET VIEW \\192.168.0.2," they can see all the shares > available. The intention is for the users who are dialing up to have > the same access they would if they were logging in normally. > > What makes viewing the shares via IP any different? Does it > go directly > to the box and query the available shares, and bypass the > Domain Browser > List completely? > > The users computers do not have any HOSTS or LMHOSTS files. > > > What OS are the RAS users using? > > Windows 2000/XP users. > > > On NT based systems the user will actually have to do a > > 'CNTL+ALT+DEL' and choose log on with dial up networking. > > This may be an option -- Most users are used to logging on with cached > credentials and then establishing a dial-up connection. > > > Otherwise they never really get authenticated. At least this > > is what I have seen. > > But -- hold on a moment. The user establishes a dial-up > connection to a > remote network, gets ... partially (?) authenticated? I don't > understand exactly what you mean. A user gets authenticated and that > should be the end of it. > > > Do these users have logon scripts, and > > if so do they run when connecting? What protocols are running > > on the clients? Do they have NetBEUI running? > > TCP/IP is the only protocol running. The users don't have > login scripts > when they are connecting via Dial-Up connection. The login > script WOULD > run if they logged on using dial-up networking, however in these cases > the login script has never been "tuned" to handle dial-up clients and > there are certain portions of the script that could slow them > down (any > included update deployments for example.) If I decided to change this > system I would need to configure the login script to compensate for > Dial-Up users. > > > The problem isn't RAS, it's a problem with browsing and how > > friggin braindead a protocol it is. Read up on the technical > > side of how browsing actually works, and you'll be surprised > > that it works at all. I know I am. > > Here, here! I am glad to see you're in agreement, Roger! I > am aware of > how network browsing works, in regards to the network's Domain Browser > system, and I agree that it's pretty brain dead. I'd agree too, that > it's pretty poor. > > > > -- > Adam Smith, MCSE. > 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 PROTECTED]
