This shouldn't be so hard. Anyone care to check my figures?
This is a discussion about This shouldn't be so hard. Anyone care to check my figures? in the Windows Networking category; I'm tired (just played 36 holes) & don't know if I'm doing something blatantly wrong. Both machines see each other fine thru Network Neighborhood. I can't get Comp B onto the 'Net. No firewall has been implemented yet.
I'm tired (just played 36 holes) & don't know if I'm doing something blatantly wrong. Both machines see each other fine thru Network Neighborhood. I can't get Comp B onto the 'Net. No firewall has been implemented yet. Could someone please look over this & lemme know what's wrong?
Me need sleepy.....
Comp A
NT4 SP6
NIC 1: WAN
DHCP (directly connected to shaw cable modem)
IP Forwarding enabled
DNS = Both Shaw Cable DNS server ip's
NIC 2: LAN to Comp B via cross-over cable
192.168.0.1
255.255.255.0
(blank gateway)
IP Forwarding enabled (I guess NT4 does this automatically for both NICS)
DNS = Tried empty & tried both Shaw Cable DNS server ip's
Comp B
192.168.0.3
255.255.255.0
192.168.0.1
DNS = Both Shaw Cable DNS server ip's
Me need sleepy.....
Comp A
NT4 SP6
NIC 1: WAN
DHCP (directly connected to shaw cable modem)
IP Forwarding enabled
DNS = Both Shaw Cable DNS server ip's
NIC 2: LAN to Comp B via cross-over cable
192.168.0.1
255.255.255.0
(blank gateway)
IP Forwarding enabled (I guess NT4 does this automatically for both NICS)
DNS = Tried empty & tried both Shaw Cable DNS server ip's
Comp B
192.168.0.3
255.255.255.0
192.168.0.1
DNS = Both Shaw Cable DNS server ip's
Participate in our website and join the conversation
This subject has been archived. New comments and votes cannot be submitted.
Jul 18
Jul 19
0
2 minutes
Responses to this topic
Try this to get IP routing kicked off:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q230082
And then this for some routing basics in NT:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q140859
The "IPEnableRouter" bit is the same across the NT platforms from 3.1 on up from what I can tell, and you're going to need that to be able to ping across both NICs on from the client.
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q230082
And then this for some routing basics in NT:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q140859
The "IPEnableRouter" bit is the same across the NT platforms from 3.1 on up from what I can tell, and you're going to need that to be able to ping across both NICs on from the client.
Quote:
Comp B
192.168.0.3
255.255.255.0
192.168.0.1
DNS = Both Shaw Cable DNS server ip's
Try setting the DNS for Comp B to Comp A's IP address (192.168.0.1) instead.
Comp B
192.168.0.3
255.255.255.0
192.168.0.1
DNS = Both Shaw Cable DNS server ip's
Try setting the DNS for Comp B to Comp A's IP address (192.168.0.1) instead.
OP
Thx to all for your help. It is much appreciated. Unfortunately, when I woke this morning I just reversed the machines so the 2K pc is connected to the 'Net, & the NT4 box goes thru it instead. I guess doing this made a little more sense, since the NT4 box was "struggling" on a P133 with 32MB of shared memory. Plus, the load of doing ICS (I installed Sygate ICS/Firewall on it last night) was too much for it.
I didn't get to read your replies until today, after I was done swapping NIC's from 1 machine to the other.
The amount of help one finds on these boards is truly amazing. Alec & Clutch, you're always one of the first to lend a hand. The info/links you posted are most helpful. I will keep them for reference. Xiven, I never thought of trying that, thanks for the suggestion.
Thanks fellas
I didn't get to read your replies until today, after I was done swapping NIC's from 1 machine to the other.
The amount of help one finds on these boards is truly amazing. Alec & Clutch, you're always one of the first to lend a hand. The info/links you posted are most helpful. I will keep them for reference. Xiven, I never thought of trying that, thanks for the suggestion.
Thanks fellas
