Networking Problem with Windows 95

I am getting ticked off that I can't remember how to do this myself, but here is the situation.
I have a Windows NT 4.0 domain with about sixty users or so. I have a Windows 95 machine that uses dial-up-networking to connect. My dial-up-networking password will work and I'll connect, but when I try to log on to the server it says that no Domain server was available to validate your password. I have tried using different accounts and none of them will log in. I had this working yesterday, but I can't figure out what happened to change this. The other thing is that I had another Windows95 machine that failed to log in this morning, same error, but it wasn't through a dial-up. These machines are obtaining all networking information from the server, and my settings are okay as far as that's concerned. I just can't figure this out. Help!!!!

By any chance are you running a firewall that may be blocking the network requests?

Is it perhaps not logging on?..Do you get a logon box, or does it just blow right on into windows?

Weich, I've run into that with 95 "B". If you're using IP, can you ping yourself? If not:

Take note of the IP address and remove TCP/IP.

restart in Dos Mode and CD to \Windows\ws2bakup. run ws2bakup.bat

It's normal to see an error on the very last line. restart windows, add TCP/IP and the address, reboot and you should be ok.

If you can ping, nevermind, I'm clueless.

Our firewall will allow this.

Yes, I am logging into Windows, and it doesn't matter either way.

Yes I can ping myself.

My Dial-up completes, but my network logon fails. Everything is server assigned, but for some reason when I connect it gives me an IP address of 10.0.0.31 and a gateway of 10.0.0.31. Why is that? I tried assigning an IP address but that doesn't help either. I ran all the updates for DUN and RAS, but it didn't help.

Check your gateway settings on the server.

Make sure you have IP forwarding enabled on the RAS server. You should also be running WINS if you aren't already.

Quote:

---

Originally posted by weich:
Yes, I am logging into Windows, and it doesn't matter either way.

---

Actually, yes, it does.

Anyhow, can you ping the server?

No, I can't ping the server. When I log onto the network and run winipcfg it tells me that my IP address and gateway are both 10.0.0.31.

As far as Logging on to Windows is concerned, all I care about immediately is being able to ping our server. If I do not log onto windows then 1) it won't save my password, and 2) I won't log into the domain. If I am missing some important part to my logic, please correct me. I have a feeling that the problem lies somewhere in the fact that my IP and gateway both come up as 10.0.0.31, why is that? If I can get a regular network address and correct gateway I am sure the server will validate.

Does it tell you that even if you specify an IP?

Yes, I assigned an IP address in both DUN settings and under the TCP/IP protocol. I assigned everything and ipconfig still says that I have an IP of 10.0.0.31 and a gateway of 10.0.0.31.

Have you tried removing and re-installing the TCP/IP protocal as mentioned above?

Also, how about a different modem?

I have already uninstalled and reinstalled TCP/IP. In fact, I have already reinstalled Windows. Unfortunately I don't have any additional modems to put in here. I have tried different modem drivers too. Right now it is set on Standard Modem.

THIS IS DRIVING ME INSANE!!!!!!!!

I installed the second update for Winsock. It updates the protocol stack for TCP/IP. It still doesn't work. I hate Win95, I hate it.

I would try a different modem, I know you said you don't have one, but maybe you could track one down somewere?...It's worth a shot!