One computer not seeing itself.

[RedBeard]

Ok 2 computers networked useing a Cross Over Cable. Computer A sees B, Computer A can acess B, Computer A can acess the pringter on B. Now then Computer B cannot see A, its not even seeing itself. Have checked and rechecked the settngs, they are identical in each computer, win98. What have I missed.

[goinpostal]

I am lucky I didn't make the wrong choice on the poll.......WHEW

[NooNoo]

What windows versions are we talking here?

If its 2k/xp its probably permissions.

[cabal]

You have probably checked this already, but are both networks working properly in device manager, using the correct driver? I had a system with a realtek nic that insisted on using the software driver, said it was working but did wierd things on the network. the nic worked worked fine in a another pc, but for some reason windows wouldn't set it up right. I put in a diffrent brand and it worked fine.

[RedBeard]

Both OS are win98

[imaeditedbysowulo]

Do you have file and printer sharing enabled on the one that can't be seen? Is anything being shared from that computer, such as your hard drive?

[NooNoo]

Redbeard - try the following

Open a dos box and type:

ping 127.0.0.1 on the machine that doesn't see itself

Does it time out? If it does the network card is not installed correctly

If it doesn't, then start, run, winipcfg on the machine that is working, find out the ip address of the one that is working, go back to the one that doesn't and ping the ip.

If you do not get a reply then the network protocols have not installed properly.

What network protocols have you installed?
The network properties should read something like

Client for ms networks
Network adapter
Tcp/ip
File and printer sharing

Thats all that is needed. There may be a dialup adapter there too.

If you have ipx/spx installed on either machine, this maybe the cause of the problem. Netbeui can cause similar problems depending on what else is installed.

[HBmaster]

Uninstall and install again NICs and protocols.


Son windows does not do the same thing two times.

[Rellik]

Are you using Static IP's?
IE:
192.168.0.1 <--Workstation 1
192.168.0.2 <--Workstation 2

you can set these manually in network properties, by double clicking the TCP/IP for the NIC

One thing that might work would be to set up one of the Machines with Internet connecion sharing, that way it will act as a DHCP server for the other machine

[WebHead]

Did you try browsing the network from the command prompt using "c:\net view"? Also, from the browse list window (network neighborhood) try manually entering the comp name you wish to access from the address bar "\\computername". Sometimes that'll make it magically work. Also, as mentioned above, be sure to check sys properties to be sure there's no hardware errors. Older 3com cards on Win98 sometimes need a complete reboot in order to make the card work. It's a common bug in those NIC's.