Networking 2 WIN98SE machines 3

[SlykFX]

I have two pcs both are running win98se that i am trying to network

i have gone through many networking articles but have not found a solution to my problem

in network neighbourhood ::
:: on my main machine (called "Main&quot I can only see the "Main" computer icon when i click into 'entire network' i cannot see any workgroups
:: but on my other machine (called "Bash&quot I can see the "bash" computer icon and in 'entire network' i can see he workgroup (called "HomeNet&quot

Both pcs are in the same work group (ive checked a dozen times)
the two IPs are :: Main : 192.168.1.1 & Bash : 192.168.1.2
i have tried changing the IPs to a few others but no difference

as far as i can tell all setting and drivers are correct, i changed them to whatever the walkthrough says but still no avail.

i have tried re-installing windows on both machines and have uninstalled all network componants and re-installed (on both machines)

can anyone offer any suggestions for me to try.

thanks in advance
I can't be bothered to have a sig!

 

[ski]

Try here for a possible solution:

http://www.wown.com/

 

[SESaskDFC]

Howdy:

What are you using for a subnet mask (255.255.255.0) ??

Have you installed the NetBeui protocol on both??

Have you enabled file and printer sharing and then shared at least one folder or file on each system??

Murray

 

[wolluf]

Can you ping one from the other?
Have you installed file & printer sharing?
Have you shared at least one resource (drive, folder, printer) on both machines?
Are the NICs working? Both compatible speeds (eg, not a 10mbs in one and 100mbs in the other).
How are they connected (if by a CAT5 cable, it needs to be crossover, not straight through).

http://www.wown.com

is a good site for networking help & instructions

 

[cyberdyne]

hey ! related to this query !

I am also facing same problem ping and everything is working fine. but can't see machine. then i enabled sharing. after that i could see the machines. My question is
" Why it is a must to enable sharing files/printer to see a machine in network ? "
Cause if I enable sharing there is chance of spreading of virus on whole network, in case 1 pc is infected. and otherside files are needed from other pc too. so what should be solution to this ? From:
Apoorva Gala
You can mail me at apoo1972@rediffmail.com

 

[wolluf]

You don't need to enable sharing to SEE a machine - you need to enable it to BE seen.

 

[doggammit76]

cyberdyne

I have abt a hundred Win98 Machines under my care and I set it all to file share with each other. One way to limiting viruses spreading is to assign passwords to the share. I used a generic password for the share so that everyone wouldnt have any problems sharing files.

Of course, the best defence against viruses is still an updated anti-virus software and user education.

Just my two cents worth. Information is free....dont hog it!

 

[SlykFX]

i cant ping either comp from the other

the subnet mask has been 255.255.255.0 and 255.255.0.0 (on advice that didnt make any differnce)

both cards are identical (bought at the same time)

now heres a nice twist
if i change the workgroup that "main" is in then i can see the new workgroup from "bash" but cannot enter it I can't be bothered to have a sig!

 

[Win98User]

Hi, If you list the protocols, services etc. that you have installed on both machines, it might go some way to helping you find a solution.

Also, I notice you didn't answer one of wolluf's questions;
"How are they connected (if by a CAT5 cable, it needs to be crossover, not straight through)."

BTW, Do you happen to have a Firewall such as ZoneAlarm installed on one or both of your machines?

Regards.

 

[SlykFX]

anf file and print are enabled on both and do have resources shared I can't be bothered to have a sig!

 

[cdogg]

Very stange indeed! If all other suggestions don't help, try installing the NetBEUI protocol on both pc's and reboot.

That might be a quicker fix.

It would also help to know how the two pc's are connected (i.e. through a hub, router, crossover cable, etc). ~cdogg

"The secret to creativity is knowing how to hide your sources."
- A. Einstein

 

[SlykFX]

they are connected by a cat5 UTP crossover cable

ive tried using netBEUI but there was no change

black ice is on the "main" computer and no firewall is on the other yet
i have tried disabling blackice but there was no difference in the outcome I can't be bothered to have a sig!

 

[Win98User]

Is your Primary Network Logon, in the network settings, set to "Client for Microsoft Networks"?

 

[cdogg]

In a peer-to-peer network, "Client for MS Networks" isn't necessarily required just to share files and see the other pc. You can try enabling it, but I doubt it will make a difference. I have "Windows Logon" enabled on my home network, and it works fine. Plus, I don't get the annoying login prompt each time I boot up.

Take a look at the properties of the TCP/IP protocol. Check your WINS and DNS tabs on both pc's. Make sure they're pretty much identical (of course having different IP addresses).


~cdogg

"The secret to creativity is knowing how to hide your sources."
- A. Einstein

 

[wolluf]

cdogg - you may not need client for microsoft networks as main logon - BUT it does need to be installed for networking to work - just thought I'd clarify that.

SlykFx - I think its likely you've just misconfigured something - suggestion - go to site ski & I recommended (

http://www.wown.com)

- take a note of all steps needed, remove network devices in device manager on both machines, and start again.

And/or - swap NICs between machines and see if anything changes (I'd also buy another one - they're very cheap, and try combinations).

 

[cdogg]

Thanks wolluf, I was referring to the LOGON selection, not the actual component. Having the Windows Logon instead of Client for MS Networks won't hurt your ability see other pc's or share files (on a P2P network)

Just to reinterate:
You DEFINITELY need to have the Client for MS Networks component installed for a network environment, in case anyone else misunderstood... ~cdogg

"The secret to creativity is knowing how to hide your sources."
- A. Einstein

 

[SlykFX]

Computer Main ::
Client for Microsoft Networks
100/10M Ethernet PCI Adapter
Connexant AccessRunner USB ADSL WAN Adapter
Dial-Up Adapter
NDISWAN -> Connexant AccessRunner USB ADSL WAN Adapter
TCP/IP -> 100/10M Ethernet PCI Adapter
TCP/IP -> Dial-Up Adapter
File and print Sharing for Microsoft Networks

Computer Bash ::
Client for Microsoft Networks
100/10M Ethernet PCI Adapter
Dial-Up Adapter
TCP/IP -> 100/10M Ethernet PCI Adapter
TCP/IP -> Dial-Up Adapter
File and print Sharing for Microsoft Networks

The setting for the relevant protocols and aadpters are listed in my post above

on both computers
100/10M Ethernet PCI Adapter
Dial-Up Adapter
TCP/IP -> 100/10M Ethernet PCI Adapter
TCP/IP -> Dial-Up Adapter
are identical (except for the IP address in "TCP/IP -> 100/10M Ethernet PCI Adapter" and "100/10M Ethernet PCI Adapter&quot
as a side note, i used the same driver disk for both machines so i doubt it is the drivers. I can't be bothered to have a sig!

 

[Win98User]

Going back to one of your earlier posts; Did you try altering the Workgroup of both machines to a different/new name?

Also, did you have NetBEUI (I would have installed anyway)installed whilst the firewall was disabled?

Have you tried the "FIND COMPUTER" function to find bash from Main?

Also, does the boot sequence make any difference to the result. ie. Boot Main first and then Bash then try booting Bash first and then Main.

Just doing a bit of brainstorming here.

Regards.

 

[allenEd]

Remove both network adaptors in Device manager, reboot, DONT let MS load the driver, Just cancel it. Load them manually That will clear the TCP/IP stack, The do all the above recomendations. Use TCP/IP, as using NetB will be admitiing defeat.

(Works every time)

Allen.

 

[roamer1]

I am sure that there are better network guys than me in here. but the very first thing I would do is pitch the crossover cable in the can and go buy a hub and two straight through patch cables. I have never been able to get that crossover crap to work reliably PLUG IT ALL IN, START UP THE BOXES ASSIGN THE IPs. RESTART AND YOU ARE ALL DONE. And way more stable too.