Alright, here's the skinny.
I have 3 computers that are networked using a hub. One of the computers, an old 486, was recently removed as I had acquired a k6-2 450. The computer I recieved did not have a nic or a modem, so I removed those from the old computer and placed them in the new one. As this system was used I decided the first thing I should do is blow the system out and install everything from scratch. The install went flawlessly but the computer would not load windows. Eventually I discovered there was an issue with the modem and removing that has allowed me to finish booting.

Now, I've set up the network adapter (an Intel 82595-based card) and entered in the ip information and such from the computer I was replacing. Everything works fine (I can share the internet connection from the other machines just fine, and all the other computers in the house can access the shared resources on the new machine) however, when I open network neighborhood on the new machine I find it to be empty! It doesn't even display itself. When I click entire network I'm told to run the network trouble shooter. I've done a "net diag" session and that passes fine, remember, the other computers can see and access this computer fine. If I try typing in "\\" in the address bar I'm told "The operation being requested was not performed because the user has not logged on to the network. The specified service does not exist."

I can ping the other machines, I can use the internet connections from the other machines, and all of the other machines can see and access the files from this one.

Any suggestions?

Make sure you have Client for Microsoft
Networks installed.

Here is a list of the network "components" I have installed

Client for Microsoft Networks
Microsoft Family Logon
Intel 82595-Based Ethernet
TCP/IP
File and printer sharing for Microsoft Networks

Everything is on it's default settings except the TCP/IP protocal in which I have entered my DNS, Gateway, and IP Address info.

Add the Netbeui protocol,and if that doesn't work add ipx/spx, trust me this will work

add netbeui... windoze needs it

Ok, I tried adding NetBeui and IPS/SPX to no avail (and yes, I added the protocals to both machines.) No, windows does NOT need NetBeui. That's dumb. The more protocals you have running on a given network segment the slower the network is going to run, and I don't care how fast you think netBeui is, it still adds overhead.

I added a modem to the computer and reinstalled DialUp Networking from the Windows Setup tab of Add Remove programs. After I did that it started working again.

The only reason to run NetBeui on the nic is so you can bind file and printer sharing to that and prevent people from the outside world from accessing your shared resources. This is the best solution as Win95 will bind file and printer sharing to ALL tcp/ip devices if you bind it to any one. On Win98, however, it is possible to unbind File and Printer sharing from TCP/IP for the Dial Up Adapter (effectively, the outside world if you don't get internet access through the NIC.) A firewall such as zonealarm will also protect this problem and perhaps plug other security holes.

Right now, here is my setup:
Client for Microsoft Networks
Microsoft Family Logon
Dial-Up Adapter
Intel 82595-Based Ethernet
TCP/IP --> Dial-Up Adapter
TCP/IP --> Intel 82595-Based Ethernet
File and printer sharing for Microsoft
Networks

Not really sure what solved the problem.

Thanks for all of your help.

So now your so smart, why do you ask for help if your going to respon like this.And if you want to browse your network or workgroup through network neighbourhood or my network places whichever, then click on entire network you need to have netbeui installed, next time someone offers some help don't be so picky, just go and research it on your own!!!!!

Look. I'm sorry. I was responding to the unnamed person who told me that "Windoze needs netbuei" because I know many people who run windows with networks. They don't have netbeui and they run just fine. I've never had netbeui on my nework before and it has worked for over a year. Up until when I added this new system.

Stu, your suggestion to add NetBeui and then try ISP/SPX, that was a good suggestion. I wasn't knocking you or anything and I'm sorry if you took offence. It didn't work, but it was a good troubleshooting step. How was I to know it just wasn't just a problem with the way the client for microsoft networking was working with the TCP/IP protocal. Since that didn't help that meant it wasn't protocal specific. I'm not sure why it works now. Something must have changed when I uninstalled dial-up networking, rebooted the computer, and reinstalled it.

I wrote to this forum because I have never encountered anything like this before and it was really throwing me for a loop. I thought one of you might have encountered a similar problem before and be able to offer me some good suggestions. And you guys did and I sincerly appretiate it. I'm sorry I spazzed on the unnamed respondant #4.

Once again, thank you all for helping me out. I'm sure had the problem not strangely corrected itself without explination (what else can you expect from microsoft) we would have figured the problem out. Thanks

I had the same problems I installed IPX/SPX on both My XP And Win98SE machine I also enabled Nebios Over IPX/SPX on my Win98SE Machine It then worked after that.

This is actually caused by either a corrupt TCP/IP stack or an error with the Winsock2 registry key. By removing the dial-up networking adapter, you may have inadvertently rebuilt the corrupt key. Sometimes the easiest way to correct such a problem is to completely remove all of the components (logically, not physically) from the network properties, access the registry and delete the winsock2 registry key, reboot, and reinstall all of the items including the dialup adapter driver and NIC driver clean. Strange but it works in most cases. Just a belated comment for the record. Perhaps someone will benefit out there.