• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 148
  • Last Modified:

Win98Se Networking

After a period of around 60 days my PC cannot access any MSnetwork (Win2k server and other 9x workgrouped PC resources after a reboot. (Can still see netware servers). Can still access Intranet resources eg. IIS and external internet resources through DUN. One possible clue could be when trying to access a dial up connection the win2k logon screen appears and needs to be cancelled, although I suspect this is due to log on to network is specified in DU connection. Furthermore all other PCs can see the one with the fault. If you try to log in to the server you get an authentication error logging in with correct username. If you log in with an incorrect username you get an invalid user message.
Any ideas?
Rob
0
roballison
Asked:
roballison
  • 8
  • 6
  • 3
  • +1
1 Solution
 
winbeartxCommented:
If you are able to log in as a different valid user, then I would suspect a corrupt PWL file. You can safely delete or rename PWL files in your WINDOWS directory as long as you know all your passwords.
0
 
dew_associatesCommented:
winbeartx, your are new to this site, and with that, welcome. However, unlike Newsgroups and Usenets, we observe a protocol or policy at this site with which you should become familiar. Experts do not post proposed answers that are incomplete or that are speculative, nor do they post proposed answers that incorporate the comments of others that have preceded you. By doing so, you block the question from the view of another expert who may have a solution to the problem. Since questioners can accept comments as answers, it is beneficial to the questioner that speculative answers be posted as comments, especially when the issue involves further troubleshooting. Hopefully you will cooperate with us in the future.
Dennis
0
 
winbeartxCommented:
Thanks, that was the first question I posted a response to and I realized after reading a little further what I had done. I didn't realize I could withdraw my answer and make it a comment.
0
Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

 
dew_associatesCommented:
Not a problem...Welcome!
0
 
roballisonAuthor Commented:
It is not a case of a corrupted pwl file.
0
 
dew_associatesCommented:
Roballison, what login errors are coming up in the Win98 box, and are you seeing any errors noted on the W2K server from this?
0
 
roballisonAuthor Commented:
Windows logon error. The domain password you supplied is not correct, or access to your logon server has been denied. The above occurs if you supply correct user name and password. If you supply an incorrect user name get the user name could not be found message as you would expect. I do not think the problem is necessarily Win2k as the PC is unable to find any Win9x pc on the network that has file and print sharing activated (even itself). P.S. There are no errors relating to the failed logon on the Win2k server.
Cheers
Rob
0
 
dew_associatesCommented:
Rob, are there other Win98 boxes on this LAN that are not having this same problem?

Have you tried to log on to the domain as administrator, start the User Manager for Domains and from the policies menu, choose User rights and select "Access this Computer From Network." If not. click Add and select the Everyone Group.
0
 
winbeartxCommented:
Have you tried installing NetBEUI? I know it sounds a little ridiculous, but sometimes that works.
0
 
roballisonAuthor Commented:
winbeartix. tried installing netbeui (no jot). Dew Associates. All other 9x boxes can see each other and can log into server. The box that cannot log in cannot even see itself.
0
 
dew_associatesCommented:
Rob, this will seem a bit extreme, but in the end it will save you allot of time searching for possible reasons.

1. Boot the system into Safemode.

2. Go into device manager and expand each area.

3. Remove the NIC devices including dialup networking.

4. Go through all other areas in device manager and look for duplicate or multiples of the same or similar devices. Check all areas and if you find any duplicates etc, clean that particular area out. Now close device manager.

5. Now go into the Networking area via control panel and remove all of the protocols, adapters etc. Remove networking completely. Close the network area.

6. Now go into add/remove programs, windows setup and uninstall dialup networking as well as other networking installs. Close control panel.

7. Shut the system down and remove the NIC. Note which slot that the NIC was in.

8. Boot the system into a command prompt only using the F8 key. Change directories to \Windows\Command. Now type SCANREG/FIX and touch enter.

9. Now shut the system down. Now you have a couple of options depending on the system and your resources. I would replace the NIC and put it into a different slot if one is available. If your using PCI NIC's, often there is a conflict between two devices on the PCI bus do to IRQ sharing that Windows cannot resolve. With that, you may want to follow my advice above, or at least check the motherboard manual to see which slots are shared and try and find a clean one.

10. Now reboot normally with the new NIC and reinstall dialup networking as well as your other networking components and set the box up for your LAN.

Let me know how you make out.
0
 
roballisonAuthor Commented:
Thanks for all your help. Have done some more research myself. The problem is to be Win2k RC2 related. If you boot PC's without the Win2k server being present they can all see each other. Boot the Win2k server and any PC that is set to logon to the NT domain cannot access any Microsoft Network resources. If you untick the logon to NT domain in client for microsoft network properties you can then see all resources, although browsing the win2k server can be patchy. Have looked through microsoft win2k newsgroups and this is a verry common problem with no solution posted as yet (apart from using WINS instead of DNS).
0
 
dew_associatesCommented:
What you might want to try is to make one Win98 box a master browser. Win2K will back it a backup master browser when it sees the procedure call.
0
 
roballisonAuthor Commented:
The problem is a Windows 2000 upgrade problem particular only to the beta 3 to RC2 upgrade path so I have been told. If you reinstall windows 2000 server all other clients on the network behave as expected. Many thanks for your help and suggestions.
0
 
dew_associatesCommented:
So I take it that the reinstall resolved it?
0
 
roballisonAuthor Commented:
This question has a deletion request Pending
0
 
ianBCommented:
This question has been undeleted.  The points for this question were originally 150 but have been reduced to 0
0
 
ianBCommented:
Adjusted points from 0 to 150
0
 
ianBCommented:
roballison,

You need to give feedback to the experts regarding answers they give. I think it is a bit unfair to delete the question and not give any experts points for helping you here. Espicially since it appears their suggestions helped you.

Ian
Community SUpport @ Experts Exchange

0
 
dew_associatesCommented:
roballison, I've left this open a sufficient length of time for you, and refer to my above comments as the answer. We have Win2K RC3 as well as RTM working without a problem.
0

Featured Post

2018 Annual Membership Survey

Here at Experts Exchange, we strive to give members the best experience. Help us improve the site by taking this survey today! (Bonus: Be entered to win a great tech prize for participating!)

  • 8
  • 6
  • 3
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now