One Way Netowrk!

[red12049]

HELP!!! I have a very simple network (2 comps, hub, RJ45, WIN98SE). One
system sees itself and the other computer, and all resources on that
computer (Barbara) are accessible, including printer. The Barabara system
cannot even see itself in Network neighborhood, even though sharing etc.
is working. Login is set to Windows, so there should be no "user"
problems.... Any suggestions? I am about to lose my mind! Thanks in
advance for any help....

[MadMax]

Do both systems have a shared drive?
Does Barbara have tcp/ip protocal installed?

[red12049]

Originally posted by MadMax Do both systems have a shared drive? Does Barbara have tcp/ip protocal installed?

Both systems have client for MS networks, tcp/ip and netbeui installed, as well as file and printer sharing. No passwords, sharing set 5o full access. "John" can see itself and Barbara in network neighborhood, and can access files and printer on "Barbara". Barbara cannot see itself or "John", and cannot access anything on the network. Thanks for the reply.

[MadMax]

On Barabara right click Network Neighborhood, then choose Properties.
Double click on your adaptor card. Click on Bindings tab. Are tcp/ip and netbeui boxes checked?

Also check for hardware conflicts
Start, Programs, Accessories, System Tools, System Information
(on left side)Hardware Resources, Conflicts & Sharing.

Is the NIC in the slot next to AGP? If so, you might want to move it to another open slot.

[red12049]

The 2 systems are close to each other, so it was easy for me to check, and they are set up identically, property sheet for property sheet..... no hardare conflicts either, since "John" can read and access "Barbara"....

[Floppyman]

Hi,

I have a very similar setup to yours, two pc's using win98se connected with a crossover cable. Assuming everything is setup correctly, i.e., the NIC's on both pc's, the hub is working, and file and printer sharing is installed on both computers, and there is no firewall blocking access to "John", here's what you're gonna have to do:

First, login should be set to client for microsoft networks. Second, go to your network settings in Control Panel, and go to the identification tab. Make sure (on both computers), that they are in the same workgroup. Reboot, and you should be set. If you want to be able to see both computers through network neighborhood on both computers, both will have to be in the same workgroup and have file and printer sharing installed. If one doesn't have file and printersharing installed, I've found that it will not be shown under network neighborhood. Even though file and printersharing is not installed on one sytem, it can still share the resources of another, though it obviously can't share its own.

Hope this helps.

This leads me to a question though: In network neighbordhood, do you only see the pc's in your own workgroup, and then when you click on entire network you see all the pc's (that is if you had like 2 workgroups of pc's in your house)?

[HAL9000]

Open a DOS window, from C:\WINDOWS, delete the *.PWL files

del *.pwl

For now, set your login to client for MS networks.

Click on your TCP/IP, then bindings, UNCHECK client for MS networks AND file and printer sharing. This will separate your internet connection from your network and close the IDENT port providing a bit more security.

Reboot
Do NOT enter a password, leave it blank.

You should now be able to see both and access both provided that;

1) You have the same workgroup name
2) File and printer sharing is installed
3) TCP/IP is installed for Internet, NETBEUI for your network
4) You have shared your drives, printer(s), etc.

Once all is up and running, you can switch to a Windows Logon so that you don't get the logon window on boot.

[Floppyman]

4) You have shared your drives, printer(s), etc.

Hey Hal,

I've found that you don't necessarily need to share something to see the computer, you can even double click on it, it will just be empty, as far as I know you just need to have file and printer sharing installed, and the other steps you mentioned. If everything's setup correctly and I've deleted all .pwl files I can just use a regular windows logon right?


EDIT: Just tried it, works like a charm, no more logon screen, thanks for the tip.

[HAL9000]

Yea, I know, but I figured I would throw that in just to make sure that everything will go as he is looking for. Yes, you can use the Windows Logon afterwards as well, I was just describing how to clean everything up so hopefully everything will go well for him.