ryoko

Have you checked the protocol settings? First check that you don't have any extra protocols installed on the winME computer. Also if you have more than one protocol installed, there may be a way to select the "preferred" protocol. I know if you connect to Novell, then you can chose which protocol has priority on NT and win2k machines. I don't remember if MS added this to winME. Look in the networking properties for that setting. Finally, look at what you are using for name resolution. Neteui, DNS, hosts file, lmhosts, wins, etc. The one that works best depends on your particular network. -RY

Here is something quick to try, Make a new account. Do not give it a password. Explicitly give all the required access to the shares/printers. Now have the win9x machine log in under this login. See if it works. If it does check the password and permission settings for the real account. If not, make sure they use the same workgroup. This is easiest to set on the win9x machine. Set the Client for microsoft networking to log into the <workgroup name> domain. With the same workgroup settings you should have no problems. It sounds like you have synchronized passwords for him which is good.(wouldn't work if you didn't) Create a share on your win2k machine and give "everyone" change permission. See if the other computer can access that. I find getting file shares working easier than printers. I also found that one time the user password on an nt workstation expired, and hence the people connecting would get a similar problem. Check that that has not occurred. -RY

Hello, First I would not reccommend setting everyone to full control. This is just bad practice. Set the permission to change for the everyone group. This prevents anyone except admins from changing the permissions. Also remember that if no access is selected in the permissions, it does not matter what you do, anyone within that criteria will be denyed access to the share. For example if everyone is set to no access, but user bob has full control then bob will not have access. I think the best thing you can do is to turn on the auditing for that directory. Log everything relevant so you can get all the needed information. When you find the problem, then turn off the auditing so you do not flood your security logs. Hope this helps, RY

How can I allow users to install applications in Win 2000 pro? Anything that requires registry editing will be blocked except for admins. I am using Nt4.0 domain controlers, with Win 2000 workstations. If upper management wants to install an application, I need to allow them to do so without giving domain admin rights and still not making them do anything elaborate. Any advice would be greatly appreciated. I looked at the policy editor on the workstation, but nothing there seemed to do the trick. Am I missing something trivial? I can't believe others are not in the same situation. Thank you, RY

Thanks Clutch, It seems like I am having the same problems as you did with your laptop. I appreciate the reply though. I have been giving local administrative rights to the users, but was hoping there would be a better option. -RY

For several weeks now my firewall has been going crazy from port scanning and DOS attacks from one computer. The hacker's ISP has not taken action even though I have sent several requests to them. Can anyone offer some advice on my next step? I am using a software firewall for a home pc, and I set it to block all traffic to and from this person. I would like the ability to change my ip address, but if I release my IP through winipcfg I still get the same one back the next time I log on. If I wait for my ISP's dhcp lease to expire (after about 4 days) I will get a new IP and a few days of peace before this person starts again. Thank you for taking the time to read this and for any advice you might give. -RY

Jim's reply is exactly correct on what to do, however I would like to add that you can also install the latest ipx client from Novell. It is 2000 compatible and offers some nice features if you connect to novell servers. If you don't connect to a Novell server, then stick with the microsoft client. -RY

Have you tried WINS? It it easy to configure, and will help with name resolution.

The NT4 resource kit has a utility that detects if a particular service has failed, and then e-mails you. I would like to monitor the actual exchange e-mail services in a similar way. Does anyone know of a util that will send an alert to specific users (admins) when a service fails? Thank you, RY

Are your servers in an NT/Novell environment? I found that when using the client32 from novell in a mixed NT/novell environment, browsing can become extremely slow. The microsoft IPX client does not have this problem. If you do use client32, try changing the network access order to have tcp/ip first, then novell. This will speed up browsing the WinNT servers.

I am trying to set up NT Workstations so that the user can have the rights to modify anything on the local machine (install apps, edit registry, change drivers,etc.) like an administrator can. I do not want them to have admin rights on the network. Unless they log into the local machine as opposed to logging into the domain, I have not been able to implement this. Any ideas? Thanks in advance.

I need to set up a machine with 2 proxy settings. It is a laptop that will either connect to the lan using our firewall in the proxy settings of the internet browser, or it will be connected to another network which does not use the proxy settings. I would like this to be transparent to the user, however the best solution I found was to use 2 browsers (IE and Netscape) for the different proxy settings. I tried using hardware profiles, but this provided more problems. Any ideas would be appreciated. Thanks, RY

I have tried something like that. I made them an admin on the local machine, and instead of logging into the domain they log into the local machine. if their password and username are the same, they can access the network resources as users but the local machine as "local admins". the problem is the network login script does not run in this manner. I had to set a script on each individual machine to run and access the system's loginscrips. I really do not like this solution, but it seems like the only way to accomplish what I need. Thank you anyway for the help.