I'm trying to connect a desktop running Windows 2000 to our newer desktop running XP via a crossover cable. After giving the new one IP address and subnet mask of 192.168.0.1, 255.255.255.0 and the older one 192.168.0.2, 255.255.255.0 they appear to be connected. Previous attempts at running the Network Setup Wizard didn't connect them. On the older one in My Network Places I can now see some of the files on the newer one but not the other way around. When I try to access Internet Explorer via the new connection it brings up "Page cannot be displayed". I went back in to the Network Setup Wizard on the newer one and changed the setup to indicate it as the gateway and the other one as the client. The instructions that I had said that I should now go to the client machine and indicate that it connects thru the other computer but I can't find where to do that. The only wizard I seem to have is a network identification wizard and I'm afraid if I run that again I'll just create another connection icon. HELP, please.
Networking Problem
- Thread starter snuffbox
- Start date
Samstoned
Posts: 1,009 +0
if you are trying to use for internet access you must enable ICS check under the firewal settings
set the nics to dynamic and try again
and more if that does not work
disable simple file sharing
I think the subnet mask is wrong
try 192.168.1.1 and 192.168.1.2 with subnet 255.255.255.0
or try subnet 255.255.0.0 with your ip address's
xp wants to be the server you got netbios enabled
and your primary wan access is with a another nic or what?
set the nics to dynamic and try again
and more if that does not work
disable simple file sharing
I think the subnet mask is wrong
try 192.168.1.1 and 192.168.1.2 with subnet 255.255.255.0
or try subnet 255.255.0.0 with your ip address's
xp wants to be the server you got netbios enabled
and your primary wan access is with a another nic or what?
D
DelJo63
for the net 192.168.0.x the subnet would be 255.255.255.0Samstoned said:
the issue here is that ICS enables the OS to perform routing from the NIC
attached to the Internet to that which is configured as the ICS nic.
Without this routing, you get exactly the users symptoms,
ping and file/print sharing will work but the downstream system has no Internet access.
btw: use only NetBios over TCP/ip and do not add the protocol itself to the stack -- unnecessary
YosefM
Posts: 23 +0
Snuffbox,
If you're simply trying to setup 2 computers to talk to each other, you're nearly there. You do need to set the same workgroup on both machines to be able see each other.
crossover cables are EVIL - dont use them. They interpose themselves into situations where they cause all sorts of mischief. Use normal cables and a hub or switch. I promise, you'll thank yourself for spending the extra $ or 10.
If you are attempting to share an internet connection, do yourself a favor, and get a router. For 2 PCs you wont even need the hub or switch mentioned above. Even MS discourages using ICS, calling it the method of last resort. Take their hint and dont use it. Just find the cheapest name-brand router on the shelf & it should work for most purposes - no fancy stuff unless you're doing fancy stuff The vast majority of modern consumer routers set themselves up with almost no intervention from us mere humans.
Once both machines have internet access, you'll want to set up the workgroup:
XP - right-click My Computer->Properties, Computer Name tab. If you need to change the workgroup name, click Change.
Win2K - right-click My Computer->Properties, Network Identification tab. If you need to change workgroup name, click Network ID, follow the wizard to join a workgroup, the name is not case sensitive.
Reboot is required.
open Windows explorer, turn on file sharing, share something.
Reboot both machines, wait a few minutes. Open windows explorer again, expand My Network Places in the folder view, expand Entire Network, expand Microsoft Windows Network, expand your workgroup - both computers should be visible. Expand the other PC, its shares should be visible.
If you're simply trying to setup 2 computers to talk to each other, you're nearly there. You do need to set the same workgroup on both machines to be able see each other.
crossover cables are EVIL - dont use them. They interpose themselves into situations where they cause all sorts of mischief. Use normal cables and a hub or switch. I promise, you'll thank yourself for spending the extra $ or 10.
If you are attempting to share an internet connection, do yourself a favor, and get a router. For 2 PCs you wont even need the hub or switch mentioned above. Even MS discourages using ICS, calling it the method of last resort. Take their hint and dont use it. Just find the cheapest name-brand router on the shelf & it should work for most purposes - no fancy stuff unless you're doing fancy stuff
The vast majority of modern consumer routers set themselves up with almost no intervention from us mere humans.Once both machines have internet access, you'll want to set up the workgroup:
XP - right-click My Computer->Properties, Computer Name tab. If you need to change the workgroup name, click Change.
Win2K - right-click My Computer->Properties, Network Identification tab. If you need to change workgroup name, click Network ID, follow the wizard to join a workgroup, the name is not case sensitive.
Reboot is required.
open Windows explorer, turn on file sharing, share something.
Reboot both machines, wait a few minutes. Open windows explorer again, expand My Network Places in the folder view, expand Entire Network, expand Microsoft Windows Network, expand your workgroup - both computers should be visible. Expand the other PC, its shares should be visible.
D
DelJo63
this is correct -- it covers the ENTIRE non-routable 192.168.x.x class C subnet.Samstoned said:
However, if the only two router addresses are 192.168.0.1 and 192.168.1.1,
you can reduce traffic that is useless by restricting the data allowed via a
tighter subnet mask, eg 255.255.254.0 (255 -1 = 240 and the one extra BIT
is for the 1.1 router
if you had four routers, the submask would be 252
four in binary is x'100' or three bits from 255 = 252
There may nasty parochial firmware that ASSUMES class C addresses should
not span more than 255 addresses and therefore will not accept 255.255.252.0
In that case, just move to the class B address range 172.16.0.0
best wishes
Latest posts
-
Resident Evil 9 returns to Raccoon City, coming next February
- fadingfool replied
