-
Quote:
Originally posted here by Tedob1
if the ME is NTFS the 95 box wont be able to access any files.
Not exactly true..
Of course, as was corrected in the thread you meant XP (since ME doesn't support NTFS).
Still, if it was XP, it wouldn't be a problem: accessing share isn't like mounting the drive locally...
The only thing you might have to do in that case would be to make sure that the XP machine as an account for each user that needs access (as you would in a NT/W2k/XP peer to peer (no domain) network)...
The user trying to access the shared drive would be then be able to connect directly if using the same credentials (login/pass) on his machine or would have to re-enter his credentials when prompted....
Ammo
-
A suggestion if I may...
For more security, you can get a cheapo computer (a 486 even) and set up Linux or FreeBSD as a gateway server with the NAT daemon and as many firewall rules and security settings as you want... That way, your windows boxes can share all they want and you won't have to worry about anyone outside of your local net taking advantage of your sharing access.
Another route (and quicker if you are not familiar with *NIX at all), is to get a router (a hardware firewall/NAT box)... You can get a decent one for around $60, I believe (I don't know about that price for sure, but it's what I seem to remember).
I wouldn't trust a windows box connected directly to the internet if I had sharing turned on. That's just a scary thought to me.
The following links will be of interest to you:
http://www.practicallynetworked.com/
http://www.internet-sharing.com/
I hope that helps, man... Have phun and do play it safe! :)
Rev
-
Thank you guys. I read something in a book about a parallel file transfer cable for connecting 2 computers. Would a parallel file transfer cable allow my other computer to connect to the internet? Cause a file transfer cable is only about $12.
-
No. That would be difficult.
-
Depending on the OS's you are going to use, you are best off getting the Linksys 4 port cable/dsl router w/4 port switch and built in firewall. (About $130) Install a network card in each PC and then connect them to your Linksys via Cat5. The Linksys will allow you to share files w/internet access and will offer a firewall against the world. That way you're not exposing a system w/file & printer sharing to the Internet.
The Linksys box is easy to config and will allow for 2 more systems should you decide to do so. Setting up with a crossover cable between systems will limit expandability.
A parallel cable will allow direct file transfer, but internet access will not be allowed. And I would avoid using anything like Internet connection sharing in WIN98 and such. Try to go the hardware solution if at all possible, may be more expensive initially, but the security investment is worth the extra $$$.
-
I am A Network Administrator ask me anything
-
OK... please define a Tokether.
-
For those who are curious, a Tokether is simply a NT box that has both Ethernet and Tokenring cards, and routing enabled. It acts kind of like a bridge to allow a tokenring network to talk to a ethernet network. IT people swore up and down that you cant make a tokenring talk ethernet. you can. :) and thus we named it a Tokether. :)
-
Ryan> Those parallel transfer cables suck ass. You get almost no speed out of them. It would be quicker to put everything on a cd and walk it to the other computer. If you really want to go cheap, you don't even need a hub. Just use a cat5 crossover cable. If you don't have one and can't find one, the are pretty simple to make. Just get a lenght of cat5 wire equal to the distance between your computers. On one end, wire one pair to pin 1&2, and one pair to 3&6. On the other end, reverse the wiring. Although according to standards, the colors matter, they really don't and you don't even need the other 4 pins. You can actually use phone wire as long as you have RJ-45 (8 pin) connectors.
wiring
1------3
2------6
3------1
6------2
-
average> I just did a google search and only found 6 links with the word tokether. And they are all misspellings of the word together.
Bridging tonken ring and ethernet is nothing new. We had it running at the college I attended back in the late 80s on a test network. I will still swear up and down that you can't make a tokenring talk ethernet though. You are running it through a bridge. The tokenring and the ethernet are not talking directly to eachother. The NT/*nix/novell box is translating.
I don't speak dutch, but if I have a traslater I can communicate with someone who only speaks dutch. That doesn't mean that I am now bilingual.
