PC to PC using ethernet cards
#1
Feeling a bit thick, but is this possible?
Have a Windows 98 machine that I'm trying to link up to a Windows 2000 machine with a new ethernet card installed in each. Both have recognised the cards etc but they're not talking, how do I get them to do it? Direct connect in 98 appears quite different from the connection wizard in 2000.
Basically wishing to transfer 20 Gb plus of data from one to the other and get the sharing the NTL internet access.
Help!
thanks in advance
Gordo
Have a Windows 98 machine that I'm trying to link up to a Windows 2000 machine with a new ethernet card installed in each. Both have recognised the cards etc but they're not talking, how do I get them to do it? Direct connect in 98 appears quite different from the connection wizard in 2000.
Basically wishing to transfer 20 Gb plus of data from one to the other and get the sharing the NTL internet access.
Help!
thanks in advance
Gordo
#2
Scooby Regular
First thing you'll need is a cross-over cable if you want to link them directly. Alternatively, you could use a couple of standard cables and a Hub/Switch.
You then need to give both NIC's and IP address:-
PC with NTL connection - 192.168.0.1 (255.255.255.0 for the mask)
2nd PC - 192.168.0.2 (255.255.255.0)
The you should be able to type PING 192.168.0.1 from the 2nd PC. If you get a reply, then it's working.
You then need to add file/printer sharing on them so you can transfer files.
W2K has security and Win98 doesn't, so if you try to connect from the 98 PC to the 2000 one, you'll need to authenticate with a username and password.
Best thing to do is logon to the Win98 as a user that you already have on the 2000 box (set the same password on the 98 PC to make it easier).
Stefan
You then need to give both NIC's and IP address:-
PC with NTL connection - 192.168.0.1 (255.255.255.0 for the mask)
2nd PC - 192.168.0.2 (255.255.255.0)
The you should be able to type PING 192.168.0.1 from the 2nd PC. If you get a reply, then it's working.
You then need to add file/printer sharing on them so you can transfer files.
W2K has security and Win98 doesn't, so if you try to connect from the 98 PC to the 2000 one, you'll need to authenticate with a username and password.
Best thing to do is logon to the Win98 as a user that you already have on the 2000 box (set the same password on the 98 PC to make it easier).
Stefan
#3
Scooby Regular
#5
Scooby Regular
Watch out for 98, it has a habit of not giving you a login prompt and just logging you on as a user.
If you allow it to do this and try to connect to the 2000 box, it will automatically try to use the 98 username and password that you've logged on as.
It that username and password isn't right, then you'll get errors trying to connect to shared folders.
Either enable the logon prompt and make sure you login as a valid 2000 user or re-create the same username/password combo on 2000 with rights to the shared files.
Stefan
If you allow it to do this and try to connect to the 2000 box, it will automatically try to use the 98 username and password that you've logged on as.
It that username and password isn't right, then you'll get errors trying to connect to shared folders.
Either enable the logon prompt and make sure you login as a valid 2000 user or re-create the same username/password combo on 2000 with rights to the shared files.
Stefan
#6
Scooby Regular
Sorry,
When you add TCP/IP it will prompt you to use a DHCP server or to specify the address manually.
You choose the manual method and the dialog will ask for the IP address and the network mask. I think it might even set it to 255.255.255.0 by default when you set the IP address.
Stefan
When you add TCP/IP it will prompt you to use a DHCP server or to specify the address manually.
You choose the manual method and the dialog will ask for the IP address and the network mask. I think it might even set it to 255.255.255.0 by default when you set the IP address.
Stefan
#7
just install NetBEUI on both PC and they should be able to see [1] each other using a cross over cable.
if using NetBEUI, you can leave your TCP/IP setting as "obtain IP automatically". you will need to setup ICS (internet connection share) [2] on one of the PC (will be the host PC) to share your internet connection.
[1] provided you have shared the HDD, just map it on one of the PC to the other.
[2] comes free with windows 98se, me, w2k and XP.
if using NetBEUI, you can leave your TCP/IP setting as "obtain IP automatically". you will need to setup ICS (internet connection share) [2] on one of the PC (will be the host PC) to share your internet connection.
[1] provided you have shared the HDD, just map it on one of the PC to the other.
[2] comes free with windows 98se, me, w2k and XP.
Trending Topics
#8
IPX is often the easiest to use in this situation, as (a) it's a flat addressing structure (not hierarchical, like TCP/IP) and (b) the network address is automatically assigned (it's a function of the MAC address of the adapter): therefore, not much to set up.
Incidentally, IPX is the most efficient routable protocol.
Incidentally, IPX is the most efficient routable protocol.
#9
Scooby Regular
Carl,
That's becuase it broadcasts itself every bl00dy 30secs with RIP and SAP packets
Gordo needs IP to use his NTL broadband connection on the 2nd PC and everyones using it now, so he might as well get used to configuring it.
Stefan
That's becuase it broadcasts itself every bl00dy 30secs with RIP and SAP packets
Gordo needs IP to use his NTL broadband connection on the 2nd PC and everyones using it now, so he might as well get used to configuring it.
Stefan
#10
This is becoming entertaining now! just wish I understood all of it - will endeavour to get the bloody things talking to each other this evening and will report back......
cheers
Gordo
cheers
Gordo
#11
well, IMHO, i think my method is the easiest (no need to fart about with IP, MAC, etc). just install TCP/IP on both PCs and set them as "obtain IP automatically" and also install NetBEUI. NetBEUI will enable both PCs to "connect" each other and the TCP/IP to carry the internet traffic. the host PC which is connected to NTL need ICS install and the 2nd PC should be able to "connect" to the internet as well when connected via a cross over cable.
easy solution
easy solution
#12
Scooby Regular
suba,
What's giving out the IP address? Is it ICS or soemthing else?
IIRC, ICS will set your LAN card to 192.168.0.1 (static IP), but I didn't know if it acts as a DHCP server
Stefan
What's giving out the IP address? Is it ICS or soemthing else?
IIRC, ICS will set your LAN card to 192.168.0.1 (static IP), but I didn't know if it acts as a DHCP server
Stefan
#15
Scooby Regular
Still don't see the point though with two only PC's
One benefit is not having to specify a DNS server (would be the ICS gateway) when using DHCP as it would automatically hand out these settings.
Stefan
One benefit is not having to specify a DNS server (would be the ICS gateway) when using DHCP as it would automatically hand out these settings.
Stefan
#16
I'm prepared to be proved wrong but neither Win2K Pro or Win98 support IP forwarding ? - It needs NT,2K or XP server ?
Therefore you need ICS (or some proxy software, or an external firewall/route, or ....) to enable Box B to see the Internet via Box A ?
Deano
Therefore you need ICS (or some proxy software, or an external firewall/route, or ....) to enable Box B to see the Internet via Box A ?
Deano
#17
ICS wont enable you to "connect" PC A to PC B or vice versa for file sharing, etc, hence the need to use NetBEUI to connect both PCs. but if only for internet sharing, then IP is enuf.
ICS does act like a DHCP/NAT, so setting your IP to "obtain IP automatically" is enuf on the client PC, therefore no need to set a static IP.
ICS does act like a DHCP/NAT, so setting your IP to "obtain IP automatically" is enuf on the client PC, therefore no need to set a static IP.
#18
Scooby Regular
Ok, so Gordon installs ICS on the W2K box, which gives him IP and a static address of 192.168.0.1 on his LAN card.
If he then installs File and Print sharing (local LAN connection only), then he can transfer files using TCP/IP. He doesn't need to add NetBeui as NetBios will run over IP (by default).
He then adds IP to his 98 PC and File/Print sharing if he wants to share files on that PC too. If you add IP, then by default it uses DHCP, so no further config is required.
All that's left is the authentication from 98 to W2K.
That sound about right? Don't think I've done anything else when configuring it before.
Stefan
If he then installs File and Print sharing (local LAN connection only), then he can transfer files using TCP/IP. He doesn't need to add NetBeui as NetBios will run over IP (by default).
He then adds IP to his 98 PC and File/Print sharing if he wants to share files on that PC too. If you add IP, then by default it uses DHCP, so no further config is required.
All that's left is the authentication from 98 to W2K.
That sound about right? Don't think I've done anything else when configuring it before.
Stefan
#19
Mr Smith, you can enable IP forwarding in Win2k, hint : HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Tcpip\Parameters
IPEnableRouter = 1
You need at least SP2 build 41719 under Win2K.
H
IPEnableRouter = 1
You need at least SP2 build 41719 under Win2K.
H
#20
Stefan
Sounds good to me. As per your earlier post, auth can be a pain.
H - Nobody likes a smart-*** Anyway IP forwarding on anything without a cisco label = "work of the devil"
Deano
Sounds good to me. As per your earlier post, auth can be a pain.
H - Nobody likes a smart-*** Anyway IP forwarding on anything without a cisco label = "work of the devil"
Deano
#21
Lads do you mind if i put in my pence worth & join the fun.
I have bt openworld adsl using an alcatel (adsl) usb modem.
This is connected to my '98 pc.
also has the following installed & configured ;
An ethernet card (on RJ45)
tcp/ip
client for microsoft networks
internet connection sharing
file & print sharing enabled
dial-up adator for adsl modem
tcp/ip properties for internet connection sharing
set to "obtain ip automatically"
tcp/ip properties for ethernet card;
ip add 192.168.0.1
sub mask 255.255.255.0
i also have both pc's in a workgroup, and a gateway
installed.ip add of 192.168.0.1
win 2k pc
has ethernet card
network connection given, "obtain ip automatically"
installed a gateway 192.168.0.1
put it in same workgroup as '98 pc.
connect 2 pc's by mini hub
dont forget to share out folders !!!
and remember the 98 pc will only see files on partition formatted in FAT varieties NOT NTFS.
and they both browse luvly
I have bt openworld adsl using an alcatel (adsl) usb modem.
This is connected to my '98 pc.
also has the following installed & configured ;
An ethernet card (on RJ45)
tcp/ip
client for microsoft networks
internet connection sharing
file & print sharing enabled
dial-up adator for adsl modem
tcp/ip properties for internet connection sharing
set to "obtain ip automatically"
tcp/ip properties for ethernet card;
ip add 192.168.0.1
sub mask 255.255.255.0
i also have both pc's in a workgroup, and a gateway
installed.ip add of 192.168.0.1
win 2k pc
has ethernet card
network connection given, "obtain ip automatically"
installed a gateway 192.168.0.1
put it in same workgroup as '98 pc.
connect 2 pc's by mini hub
dont forget to share out folders !!!
and remember the 98 pc will only see files on partition formatted in FAT varieties NOT NTFS.
and they both browse luvly
Thread
Thread Starter
Forum
Replies
Last Post
Mattybr5@MB Developments
Full Cars Breaking For Spares
28
28 December 2015 11:07 PM
Mattybr5@MB Developments
Full Cars Breaking For Spares
12
18 November 2015 07:03 AM