Networking XP & 98 Properly

Just recently we installed a new Comp on our network.XP pro machine.
We are running a peer-to-peer setup.
We have DSL with syslink router.
O.K. from the XP machine we can put new files into folders but we cannot put updated files in that is over write old with new. Nor can we edit or delete files on 98 machines.
O.K. so I read a Microsoft XP book and it says that because we are running and internet XP throws a psuedo firewall on every machine because every machine is file transfering through TCP/IP.
O.K. so it suggests that I set all the machines to IPX/SPX for file and print sharing and disable that feature for TCP/IP.
I do that an XP doesn't even see 98 machines.
I saw CLIffh answer to post on 1-10-02 and thought well I must be on right track but what next?
Where am I going wrong?

 

1. Turn off IPX/SPX

2. Turn off the XP firewall

3. Enable file & printer sharing on your PCs

4. Start logging on the 98 PCs with a username and password. You can use the same one on each or a different one on each. The XP machine demands to know exactly WHO wants to so what.

5. On the XP machine, add to your users (right-click my computer~manage~users & groups~users) the exact username and password you are using on each 98 PC. Exact because this feature is case sensitive.

6. Share at least one folder on each PC you want to be "seen" on the network.

7. Quit starting sentences with "OK" when it obviously isn't OK.

8. Buy a different XP book.

9. You said "O.K. from the XP machine we can put new files into folders but we cannot put updated files in that is over write old with new. Nor can we edit or delete files on 98 machines. " Did you mean from the local PC you can't do this stuff or over the network? Or did you mean something else altogether and if so, what?

10. If you think you got some answers from a post from 1-10-02 by CLIffh that may have a bearing on the problem, please post a link.

11. If you really hate computers as your user name says, quit messing with them. Not worth the aggravation.

 

Thanks for some of the answers Newt.
I'm trying to keep it civil NEWT.
The book is Microsofts own book on XP. You're saying Microsoft doesn "t know how to network. If I turn off the firewall I'm potentially open to the internet. I don't want that.
Put pillows on the floor so you will have a safe landing next time you fall out of bed!

 

Hi Newt!!

What about me, hooking up Windows XP and Windows 2000? Can't do that for some reason.

Know how to turn the firewall off on XP (just got this 2 days ago, trying to figure it out!). I use zone alarm so I don't need this firewall, it's causing problems already!! (maybe this is why it cannot detect the other Win2000 comp?!?!)



Thanks!!

Crysti

 

From Uncle Bill.

 

Gracias! I figured it out right before you posted! Heeeee!!! I should say the FIREWALL part, still don't know about the other part, getting these computers together!!

 

IetaHsretupmoC - LOL, you don't need to keep it civil on my account. But it was probably a good idea anyway.

If the "syslink" you are using is really a LinkSys router/switch with NAT (which is likely) then it has a built-in firewall between your LAN and the internet and the additional one on the XP PC will just add confusion/complexity without protecting you very much. You have additional insulation/protection from NAT.

Microsoft books on networking are usually pretty good. Not the best by any means but good. O'Reily pubs are normally much better. However, you list your experience as "beginner" and I thought it probable you had a book that assumed knowledge you did not have. Therefore the "buy another book" recommendation.

You can do exactly what you are trying (unsuccessfully) now without IPX/SPX and it does add more complexity. Maybe OK once everything else is working but IMO not a great idea to make things more complicated than necessary while trying to troubleshoot problems. After everything is working, by all means add IPX/SPX, NetBeui, PAN, LANE, sneakernet, and any other networking protocol that strikes your fancy. Your switch can certainly handle the extra network traffic without taking a performance hit. Even if some of your NICs are 10mbs, you still won't see hits unless you add lots more clients to the network.

Beginning sentences/paragraphs with "OK" when describing problems: maybe just a quirk of mine and maybe based on age but it is mis-applied verbiage that adds nothing and does jangle me a bit. Possibly also some of the other old fuds who spend a bit of time on here helping out. So it's a "no gain & maybe a loss" situation for you and hardly seems worth doing.

If your handle expressed your opinion (I hate computers), then I still say you should consider not doing computers - at least the setup parts. I hate working on automobiles and plumbing. So I don't. I pay folks who like doing it and are good at it. If necessary I'll work overtime at something I do like to get the $$ needed to pay for things I don't like. Life is way too short to spend time doing things you hate if there is any alternative and for setting up a home network, there are alternatives.

If you are still having problems, I still think it would be a good idea to post a translation of the section I said I didn't understand. It may be important and as originally stated, is to vague and open to several interpretations.

Or if you'd prefer, I can happily butt out of this thread altogether. Just post your wishes.

 

Well said. The formula for the handle wasn't difficult to decipher, but you made a slight error. S/B, "I Hate Computers" (case sensitive)

 

OK! NEWT TIME TO GO FISHING OK! hee hee hee!!!!

Mike

 

True. With firewall enabled inbound traffic is compared to sender's communication so as to verify the communication began with the sender. Full duplex communication mode will deny incoming data unless it is properly identified. Half duplex transmission is not acceptable! However, an entry in Services will allow passage and is the exception.

"We have DSL with syslink router. " NetBEUI is nonroutable. which means it can only be used on simple networks where routing is not used. This protocol cannot be transmitted from on unit to another and this may explain why XP doesn't see 98 machine.

This may give you some insight as to whether or not you are on the right track.

 

Gosh you all have fun over here! Why cain't we have fun like this in other threads? LOL!

So let me get in on it too!

Mr. I Hate Computers

There are a lot of people that know more about networking than Microsoft!

In your senario XP does not and cannot "throw" any kind of firewall on other computers!

It could if you had it set as the ICS ( "Internet connection sharing ") station "and" all other computers were setup to go thru it!

It could if the internet was connected stright to the XP machine thru a second network card and shared from there!

There are even a couple more ways to do it!

But not in your description of your setup!

Follow Newt's advice! Cleanup you protcols! Get your users set up!

Then if things don't work we will be closer to your real problem!

Mike

 

One more thing!

NEWT!!!!!!!!!!

How do I get one of your "Secret Decoder Rings "!!??

LOL! lol! Lol! loL! LOL! lol! Lol! loL! LOL! lol! Lol! loL! LOL! lol! Lol! loL! LOL! lol! Lol! loL!

 

Mike - it came to me in the middle of an all-night fishing session. After a couple hours of no action and even the skeeters have gone to bed, lots of time to think about most anything.

 

Where you on pillows?