Re: I seems Confused.....Peer-to-to TCP/IP Network [7:58255]
Hi Mark and All! This is to thank everyone who responded or think through my question but could not response. I have been able to resolve the problem. Actually, I install Checkpoint NG on the Windows NT 4.0 system for my home lab but had not being using it. So I completely forgot that its security modules still loads in the services. So it drops all traffics. Thanks once again. Regards. Godswill - Original Message - From: Mark W. Odette II To: Sent: Friday, November 29, 2002 2:03 PM Subject: RE: I seems Confused.Peer-to-to TCP/IP Network [7:58255] Oletu- What you are trying to do is not impossible. Many of us do this all the time to migrate data from one machine to another without burdening the Hub-based LAN or if the computer is all by itself and is being upgraded. Case in point is the situation where a Win9x/Pentium 166Mhz workstation is being replaced with a Windows XP/Pentium III 1.8Ghz workstation... NetBEUI isn't a protocol option on XP, as it isn't supported anymore- So, it's TCP/IP or IPX! Configuration of each computer is correct; the fact that you can operate with success running NetBEUI says that your physical layer is also solid, i.e., NIC's and Cross-over cable. Next thing to do is (for informational purposes) to 'route print' or a 'netstat -r' at the command line to determine the TCP/IP stack has proper routing information. Optionally issue the 'nbtstat -c' or 'nbtstat -r' to see if you are getting any netbios caching... After collecting this information, I would remove the TCP/IP protocol, reboot, reinstall TCP/IP protocol, install most recent SP for OS, and test again... If that doesn't resolve the problem, then seek out replacement drivers for the NIC(s). This pretty much addresses every possibility of failure between two Windows-based computers that are directly connected to each other with a cross-over cable. ... One other thought- You wouldn't have some kind of personal firewall installed/previously installed on either one of these computers by chance, would you!?!?! I have seen all kinds of crazy stuff occur on MS boxes that had had any of the different flavors of Personal Firewalls installed, which usually required complete removal of the TCP/IP protocol, and then sifting through the networking portion of the registry to recover the machine. The alternative was to reinstall the OS from scratch. The firewalls in question were the Norton Personal Firewall, the Network Associates Desktop Firewall, BlackIce, and one other I can't recall the name of. Just some extra info to chew on for possibility. Good luck, and let us know what you find... -Mark -Original Message- From: Godswill Oletu [mailto:[EMAIL PROTECTED]] Sent: Friday, November 29, 2002 12:04 PM To: Mark W. Odette II; [EMAIL PROTECTED] Subject: Re: I seems Confused.Peer-to-to TCP/IP Network [7:58255] Hi Mark, I have done all that. The crossover cable is okay. NeTBEUI is working fine. I can see both computers through Network Neigbourhood; copy files from one computer to the other. Everthing about NetBEUI is kool. I have alos edited the hosts/lmhost files on each computer (this only help to resolve the IP Address to the netbios name.) IP addresses are Computer A=192.168.0.1/255.255.255.0 and Computer B=192.168.0.2/255.255.255.0 On Computer A, I can ping 192.168.0.1, localhost and 127.0.0.1 and it will response fine. On Computer B, I can also ping 192.168.0.2, localhost and 127.0.0.1 and it will response fine. (TCP/IP stack seems perfectly installed)!!! But I cannot ping A from B, neither can I ping B from A. This is the dumbest thing I have ever done and it is messing me up. Or is it impossible? - Original Message - From: Mark W. Odette II To: Sent: Thursday, November 28, 2002 8:22 PM Subject: RE: I seems Confused.Peer-to-to TCP/IP Network [7:58255] Check your subnet masks for each computer. Either specify Computer B as the default gateway for Computer A and vice-versa, or don't specify a default gateway at all. After that, you have to configure the lmhosts/hosts files if you want to resolve machine names between each other (quickly). Verify that your cross-over cable is good, or plug each computer into a hub/switch. It's that simple. Cheers! -Mark -Original Message- From: Godswill Oletu [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 28, 2002 6:26 PM To: [EMAIL PROTECTED] Subject: I seems Confused.Peer-to-to TCP/IP Network [7:58255] Hi all, Where are mine going wrong? Has anyone implemented a Peer-to-Peer network involving just two computers with ONLY TCP/IP Protocol? I have been trying to do it but keeping failing. NetBEUI is working fine, I can transfer files in between both computers. But TCP/IP protocolis not working across. Am trying to connect a Window NT to Windows 98 Machine. I used the normal cross
RE: I seems Confused.....Peer-to-to TCP/IP Network [7:58255]
That is really funny. -Original Message- From: Godswill Oletu [mailto:[EMAIL PROTECTED]] Sent: 03 December 2002 14:50 To: [EMAIL PROTECTED] Subject: Re: I seems Confused.Peer-to-to TCP/IP Network [7:58255] Hi Mark and All! This is to thank everyone who responded or think through my question but could not response. I have been able to resolve the problem. Actually, I install Checkpoint NG on the Windows NT 4.0 system for my home lab but had not being using it. So I completely forgot that its security modules still loads in the services. So it drops all traffics. Thanks once again. Regards. Godswill - Original Message - From: Mark W. Odette II To: Sent: Friday, November 29, 2002 2:03 PM Subject: RE: I seems Confused.Peer-to-to TCP/IP Network [7:58255] Oletu- What you are trying to do is not impossible. Many of us do this all the time to migrate data from one machine to another without burdening the Hub-based LAN or if the computer is all by itself and is being upgraded. Case in point is the situation where a Win9x/Pentium 166Mhz workstation is being replaced with a Windows XP/Pentium III 1.8Ghz workstation... NetBEUI isn't a protocol option on XP, as it isn't supported anymore- So, it's TCP/IP or IPX! Configuration of each computer is correct; the fact that you can operate with success running NetBEUI says that your physical layer is also solid, i.e., NIC's and Cross-over cable. Next thing to do is (for informational purposes) to 'route print' or a 'netstat -r' at the command line to determine the TCP/IP stack has proper routing information. Optionally issue the 'nbtstat -c' or 'nbtstat -r' to see if you are getting any netbios caching... After collecting this information, I would remove the TCP/IP protocol, reboot, reinstall TCP/IP protocol, install most recent SP for OS, and test again... If that doesn't resolve the problem, then seek out replacement drivers for the NIC(s). This pretty much addresses every possibility of failure between two Windows-based computers that are directly connected to each other with a cross-over cable. ... One other thought- You wouldn't have some kind of personal firewall installed/previously installed on either one of these computers by chance, would you!?!?! I have seen all kinds of crazy stuff occur on MS boxes that had had any of the different flavors of Personal Firewalls installed, which usually required complete removal of the TCP/IP protocol, and then sifting through the networking portion of the registry to recover the machine. The alternative was to reinstall the OS from scratch. The firewalls in question were the Norton Personal Firewall, the Network Associates Desktop Firewall, BlackIce, and one other I can't recall the name of. Just some extra info to chew on for possibility. Good luck, and let us know what you find... -Mark -Original Message- From: Godswill Oletu [mailto:[EMAIL PROTECTED]] Sent: Friday, November 29, 2002 12:04 PM To: Mark W. Odette II; [EMAIL PROTECTED] Subject: Re: I seems Confused.Peer-to-to TCP/IP Network [7:58255] Hi Mark, I have done all that. The crossover cable is okay. NeTBEUI is working fine. I can see both computers through Network Neigbourhood; copy files from one computer to the other. Everthing about NetBEUI is kool. I have alos edited the hosts/lmhost files on each computer (this only help to resolve the IP Address to the netbios name.) IP addresses are Computer A=192.168.0.1/255.255.255.0 and Computer B=192.168.0.2/255.255.255.0 On Computer A, I can ping 192.168.0.1, localhost and 127.0.0.1 and it will response fine. On Computer B, I can also ping 192.168.0.2, localhost and 127.0.0.1 and it will response fine. (TCP/IP stack seems perfectly installed)!!! But I cannot ping A from B, neither can I ping B from A. This is the dumbest thing I have ever done and it is messing me up. Or is it impossible? - Original Message - From: Mark W. Odette II To: Sent: Thursday, November 28, 2002 8:22 PM Subject: RE: I seems Confused.Peer-to-to TCP/IP Network [7:58255] Check your subnet masks for each computer. Either specify Computer B as the default gateway for Computer A and vice-versa, or don't specify a default gateway at all. After that, you have to configure the lmhosts/hosts files if you want to resolve machine names between each other (quickly). Verify that your cross-over cable is good, or plug each computer into a hub/switch. It's that simple. Cheers! -Mark -Original Message- From: Godswill Oletu [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 28, 2002 6:26 PM To: [EMAIL PROTECTED] Subject: I seems Confused.Peer-to-to TCP/IP Network [7:58255] Hi all, Where are mine going wrong? Has anyone implemented a Peer-to-Peer network involving just two computers with ONLY TCP/IP Protocol? I
Re: I seems Confused.....Peer-to-to TCP/IP Network [7:58255]
Hi Mark, I have done all that. The crossover cable is okay. NeTBEUI is working fine. I can see both computers through Network Neigbourhood; copy files from one computer to the other. Everthing about NetBEUI is kool. I have alos edited the hosts/lmhost files on each computer (this only help to resolve the IP Address to the netbios name.) IP addresses are Computer A=192.168.0.1/255.255.255.0 and Computer B=192.168.0.2/255.255.255.0 On Computer A, I can ping 192.168.0.1, localhost and 127.0.0.1 and it will response fine. On Computer B, I can also ping 192.168.0.2, localhost and 127.0.0.1 and it will response fine. (TCP/IP stack seems perfectly installed)!!! But I cannot ping A from B, neither can I ping B from A. This is the dumbest thing I have ever done and it is messing me up. Or is it impossible? - Original Message - From: Mark W. Odette II To: Sent: Thursday, November 28, 2002 8:22 PM Subject: RE: I seems Confused.Peer-to-to TCP/IP Network [7:58255] Check your subnet masks for each computer. Either specify Computer B as the default gateway for Computer A and vice-versa, or don't specify a default gateway at all. After that, you have to configure the lmhosts/hosts files if you want to resolve machine names between each other (quickly). Verify that your cross-over cable is good, or plug each computer into a hub/switch. It's that simple. Cheers! -Mark -Original Message- From: Godswill Oletu [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 28, 2002 6:26 PM To: [EMAIL PROTECTED] Subject: I seems Confused.Peer-to-to TCP/IP Network [7:58255] Hi all, Where are mine going wrong? Has anyone implemented a Peer-to-Peer network involving just two computers with ONLY TCP/IP Protocol? I have been trying to do it but keeping failing. NetBEUI is working fine, I can transfer files in between both computers. But TCP/IP protocolis not working across. Am trying to connect a Window NT to Windows 98 Machine. I used the normal cross over cable (1-3, 2-6, 3-1, 6-2) connection. localhost pings alright, IP-address to each machine can be pinged from that very machine only. Hosts file have been edited and it is resolving fine...but I can ping one machine from the other. I have double checked everything but cannot figure out whats happening. I know I have been implementing peer-to-peer networks but I had not gotten into this kind of scenario.. Any forethought would help, thanks Godswill Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=58293t=58255 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: I seems Confused.....Peer-to-to TCP/IP Network [7:58255]
Oletu- What you are trying to do is not impossible. Many of us do this all the time to migrate data from one machine to another without burdening the Hub-based LAN or if the computer is all by itself and is being upgraded. Case in point is the situation where a Win9x/Pentium 166Mhz workstation is being replaced with a Windows XP/Pentium III 1.8Ghz workstation... NetBEUI isn't a protocol option on XP, as it isn't supported anymore- So, it's TCP/IP or IPX! Configuration of each computer is correct; the fact that you can operate with success running NetBEUI says that your physical layer is also solid, i.e., NIC's and Cross-over cable. Next thing to do is (for informational purposes) to 'route print' or a 'netstat -r' at the command line to determine the TCP/IP stack has proper routing information. Optionally issue the 'nbtstat -c' or 'nbtstat -r' to see if you are getting any netbios caching... After collecting this information, I would remove the TCP/IP protocol, reboot, reinstall TCP/IP protocol, install most recent SP for OS, and test again... If that doesn't resolve the problem, then seek out replacement drivers for the NIC(s). This pretty much addresses every possibility of failure between two Windows-based computers that are directly connected to each other with a cross-over cable. ... One other thought- You wouldn't have some kind of personal firewall installed/previously installed on either one of these computers by chance, would you!?!?! I have seen all kinds of crazy stuff occur on MS boxes that had had any of the different flavors of Personal Firewalls installed, which usually required complete removal of the TCP/IP protocol, and then sifting through the networking portion of the registry to recover the machine. The alternative was to reinstall the OS from scratch. The firewalls in question were the Norton Personal Firewall, the Network Associates Desktop Firewall, BlackIce, and one other I can't recall the name of. Just some extra info to chew on for possibility. Good luck, and let us know what you find... -Mark -Original Message- From: Godswill Oletu [mailto:[EMAIL PROTECTED]] Sent: Friday, November 29, 2002 12:04 PM To: Mark W. Odette II; [EMAIL PROTECTED] Subject: Re: I seems Confused.Peer-to-to TCP/IP Network [7:58255] Hi Mark, I have done all that. The crossover cable is okay. NeTBEUI is working fine. I can see both computers through Network Neigbourhood; copy files from one computer to the other. Everthing about NetBEUI is kool. I have alos edited the hosts/lmhost files on each computer (this only help to resolve the IP Address to the netbios name.) IP addresses are Computer A=192.168.0.1/255.255.255.0 and Computer B=192.168.0.2/255.255.255.0 On Computer A, I can ping 192.168.0.1, localhost and 127.0.0.1 and it will response fine. On Computer B, I can also ping 192.168.0.2, localhost and 127.0.0.1 and it will response fine. (TCP/IP stack seems perfectly installed)!!! But I cannot ping A from B, neither can I ping B from A. This is the dumbest thing I have ever done and it is messing me up. Or is it impossible? - Original Message - From: Mark W. Odette II To: Sent: Thursday, November 28, 2002 8:22 PM Subject: RE: I seems Confused.Peer-to-to TCP/IP Network [7:58255] Check your subnet masks for each computer. Either specify Computer B as the default gateway for Computer A and vice-versa, or don't specify a default gateway at all. After that, you have to configure the lmhosts/hosts files if you want to resolve machine names between each other (quickly). Verify that your cross-over cable is good, or plug each computer into a hub/switch. It's that simple. Cheers! -Mark -Original Message- From: Godswill Oletu [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 28, 2002 6:26 PM To: [EMAIL PROTECTED] Subject: I seems Confused.Peer-to-to TCP/IP Network [7:58255] Hi all, Where are mine going wrong? Has anyone implemented a Peer-to-Peer network involving just two computers with ONLY TCP/IP Protocol? I have been trying to do it but keeping failing. NetBEUI is working fine, I can transfer files in between both computers. But TCP/IP protocolis not working across. Am trying to connect a Window NT to Windows 98 Machine. I used the normal cross over cable (1-3, 2-6, 3-1, 6-2) connection. localhost pings alright, IP-address to each machine can be pinged from that very machine only. Hosts file have been edited and it is resolving fine...but I can ping one machine from the other. I have double checked everything but cannot figure out whats happening. I know I have been implementing peer-to-peer networks but I had not gotten into this kind of scenario.. Any forethought would help, thanks Godswill Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=58296t=58255 -- FAQ, list archives, and subscription info: http://www.groupstudy.com
Re: I seems Confused.....Peer-to-to TCP/IP Network [7:58255]
Hi Mark, Actually before now I had been checking the routing table 'route print' and also the netbios cache. On Computer A with IP address 192.168.0.1, there is a route to network 192.168.0.0 through interface 192.168.0.1 and on Computer B with IP address 192.168.0.2, there is a route to network 192.168.0.0 through interface 192.168.0.1 (seem great!). I will try reinstalling the OS, because I look stupified, however currently am trying it on another computer to see what happens. What I did not mention is that, on both Computer A and B, I have two NICs each. My intention is to implement double NATing. Computer B is connected to the Internet through RJ45 broadband and this connection is working great!. My goal was to NAT this connection to Computer A and then NAT it again from computer A downstream (I have not reached here), I do not think the presense of two NICs in each computer would have any thing to do with thei. Thanks men! Godswill - Original Message - From: Mark W. Odette II To: Sent: Friday, November 29, 2002 2:03 PM Subject: RE: I seems Confused.Peer-to-to TCP/IP Network [7:58255] Oletu- What you are trying to do is not impossible. Many of us do this all the time to migrate data from one machine to another without burdening the Hub-based LAN or if the computer is all by itself and is being upgraded. Case in point is the situation where a Win9x/Pentium 166Mhz workstation is being replaced with a Windows XP/Pentium III 1.8Ghz workstation... NetBEUI isn't a protocol option on XP, as it isn't supported anymore- So, it's TCP/IP or IPX! Configuration of each computer is correct; the fact that you can operate with success running NetBEUI says that your physical layer is also solid, i.e., NIC's and Cross-over cable. Next thing to do is (for informational purposes) to 'route print' or a 'netstat -r' at the command line to determine the TCP/IP stack has proper routing information. Optionally issue the 'nbtstat -c' or 'nbtstat -r' to see if you are getting any netbios caching... After collecting this information, I would remove the TCP/IP protocol, reboot, reinstall TCP/IP protocol, install most recent SP for OS, and test again... If that doesn't resolve the problem, then seek out replacement drivers for the NIC(s). This pretty much addresses every possibility of failure between two Windows-based computers that are directly connected to each other with a cross-over cable. ... One other thought- You wouldn't have some kind of personal firewall installed/previously installed on either one of these computers by chance, would you!?!?! I have seen all kinds of crazy stuff occur on MS boxes that had had any of the different flavors of Personal Firewalls installed, which usually required complete removal of the TCP/IP protocol, and then sifting through the networking portion of the registry to recover the machine. The alternative was to reinstall the OS from scratch. The firewalls in question were the Norton Personal Firewall, the Network Associates Desktop Firewall, BlackIce, and one other I can't recall the name of. Just some extra info to chew on for possibility. Good luck, and let us know what you find... -Mark -Original Message- From: Godswill Oletu [mailto:[EMAIL PROTECTED]] Sent: Friday, November 29, 2002 12:04 PM To: Mark W. Odette II; [EMAIL PROTECTED] Subject: Re: I seems Confused.Peer-to-to TCP/IP Network [7:58255] Hi Mark, I have done all that. The crossover cable is okay. NeTBEUI is working fine. I can see both computers through Network Neigbourhood; copy files from one computer to the other. Everthing about NetBEUI is kool. I have alos edited the hosts/lmhost files on each computer (this only help to resolve the IP Address to the netbios name.) IP addresses are Computer A=192.168.0.1/255.255.255.0 and Computer B=192.168.0.2/255.255.255.0 On Computer A, I can ping 192.168.0.1, localhost and 127.0.0.1 and it will response fine. On Computer B, I can also ping 192.168.0.2, localhost and 127.0.0.1 and it will response fine. (TCP/IP stack seems perfectly installed)!!! But I cannot ping A from B, neither can I ping B from A. This is the dumbest thing I have ever done and it is messing me up. Or is it impossible? - Original Message - From: Mark W. Odette II To: Sent: Thursday, November 28, 2002 8:22 PM Subject: RE: I seems Confused.Peer-to-to TCP/IP Network [7:58255] Check your subnet masks for each computer. Either specify Computer B as the default gateway for Computer A and vice-versa, or don't specify a default gateway at all. After that, you have to configure the lmhosts/hosts files if you want to resolve machine names between each other (quickly). Verify that your cross-over cable is good, or plug each computer into a hub/switch. It's that simple. Cheers! -Mark -Original Message- From: Godswill Oletu [mailto:[EMAIL PROTECTED
Re: I seems Confused.....Peer-to-to TCP/IP Network [7:58255]
Hi Mark, So far... I brought in another Win98 system. TCP/IP and NetBEUI is working great between the two Win98 Systems. I can Ping and do all sorts of things between those two Win98 Systems. Now, same old problem, TCP/IP cannot work between Win98 and WinNT 4.0, only NetBEUI is working so far. I just swap the cable to a Win98 system and it start working. Have you personally implemented a peer to peer network between a WinNT 4.0 and Win98 System? Everything on the WinNT system looks okay, however am determined to fine a logical conclusion to this. What are not getting right now? Regards. Godswill - Original Message - From: Mark W. Odette II To: Sent: Friday, November 29, 2002 2:03 PM Subject: RE: I seems Confused.Peer-to-to TCP/IP Network [7:58255] Oletu- What you are trying to do is not impossible. Many of us do this all the time to migrate data from one machine to another without burdening the Hub-based LAN or if the computer is all by itself and is being upgraded. Case in point is the situation where a Win9x/Pentium 166Mhz workstation is being replaced with a Windows XP/Pentium III 1.8Ghz workstation... NetBEUI isn't a protocol option on XP, as it isn't supported anymore- So, it's TCP/IP or IPX! Configuration of each computer is correct; the fact that you can operate with success running NetBEUI says that your physical layer is also solid, i.e., NIC's and Cross-over cable. Next thing to do is (for informational purposes) to 'route print' or a 'netstat -r' at the command line to determine the TCP/IP stack has proper routing information. Optionally issue the 'nbtstat -c' or 'nbtstat -r' to see if you are getting any netbios caching... After collecting this information, I would remove the TCP/IP protocol, reboot, reinstall TCP/IP protocol, install most recent SP for OS, and test again... If that doesn't resolve the problem, then seek out replacement drivers for the NIC(s). This pretty much addresses every possibility of failure between two Windows-based computers that are directly connected to each other with a cross-over cable. ... One other thought- You wouldn't have some kind of personal firewall installed/previously installed on either one of these computers by chance, would you!?!?! I have seen all kinds of crazy stuff occur on MS boxes that had had any of the different flavors of Personal Firewalls installed, which usually required complete removal of the TCP/IP protocol, and then sifting through the networking portion of the registry to recover the machine. The alternative was to reinstall the OS from scratch. The firewalls in question were the Norton Personal Firewall, the Network Associates Desktop Firewall, BlackIce, and one other I can't recall the name of. Just some extra info to chew on for possibility. Good luck, and let us know what you find... -Mark -Original Message- From: Godswill Oletu [mailto:[EMAIL PROTECTED]] Sent: Friday, November 29, 2002 12:04 PM To: Mark W. Odette II; [EMAIL PROTECTED] Subject: Re: I seems Confused.Peer-to-to TCP/IP Network [7:58255] Hi Mark, I have done all that. The crossover cable is okay. NeTBEUI is working fine. I can see both computers through Network Neigbourhood; copy files from one computer to the other. Everthing about NetBEUI is kool. I have alos edited the hosts/lmhost files on each computer (this only help to resolve the IP Address to the netbios name.) IP addresses are Computer A=192.168.0.1/255.255.255.0 and Computer B=192.168.0.2/255.255.255.0 On Computer A, I can ping 192.168.0.1, localhost and 127.0.0.1 and it will response fine. On Computer B, I can also ping 192.168.0.2, localhost and 127.0.0.1 and it will response fine. (TCP/IP stack seems perfectly installed)!!! But I cannot ping A from B, neither can I ping B from A. This is the dumbest thing I have ever done and it is messing me up. Or is it impossible? - Original Message - From: Mark W. Odette II To: Sent: Thursday, November 28, 2002 8:22 PM Subject: RE: I seems Confused.Peer-to-to TCP/IP Network [7:58255] Check your subnet masks for each computer. Either specify Computer B as the default gateway for Computer A and vice-versa, or don't specify a default gateway at all. After that, you have to configure the lmhosts/hosts files if you want to resolve machine names between each other (quickly). Verify that your cross-over cable is good, or plug each computer into a hub/switch. It's that simple. Cheers! -Mark -Original Message- From: Godswill Oletu [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 28, 2002 6:26 PM To: [EMAIL PROTECTED] Subject: I seems Confused.Peer-to-to TCP/IP Network [7:58255] Hi all, Where are mine going wrong? Has anyone implemented a Peer-to-Peer network involving just two computers with ONLY TCP/IP Protocol? I have been trying to do it but keeping failing. NetBEUI
Re: I seems Confused.....Peer-to-to TCP/IP Network [7:58255]
Followup... WinNT System have Service pack 6 installed. Regards. - Original Message - From: Mark W. Odette II To: Sent: Friday, November 29, 2002 2:03 PM Subject: RE: I seems Confused.Peer-to-to TCP/IP Network [7:58255] Oletu- What you are trying to do is not impossible. Many of us do this all the time to migrate data from one machine to another without burdening the Hub-based LAN or if the computer is all by itself and is being upgraded. Case in point is the situation where a Win9x/Pentium 166Mhz workstation is being replaced with a Windows XP/Pentium III 1.8Ghz workstation... NetBEUI isn't a protocol option on XP, as it isn't supported anymore- So, it's TCP/IP or IPX! Configuration of each computer is correct; the fact that you can operate with success running NetBEUI says that your physical layer is also solid, i.e., NIC's and Cross-over cable. Next thing to do is (for informational purposes) to 'route print' or a 'netstat -r' at the command line to determine the TCP/IP stack has proper routing information. Optionally issue the 'nbtstat -c' or 'nbtstat -r' to see if you are getting any netbios caching... After collecting this information, I would remove the TCP/IP protocol, reboot, reinstall TCP/IP protocol, install most recent SP for OS, and test again... If that doesn't resolve the problem, then seek out replacement drivers for the NIC(s). This pretty much addresses every possibility of failure between two Windows-based computers that are directly connected to each other with a cross-over cable. ... One other thought- You wouldn't have some kind of personal firewall installed/previously installed on either one of these computers by chance, would you!?!?! I have seen all kinds of crazy stuff occur on MS boxes that had had any of the different flavors of Personal Firewalls installed, which usually required complete removal of the TCP/IP protocol, and then sifting through the networking portion of the registry to recover the machine. The alternative was to reinstall the OS from scratch. The firewalls in question were the Norton Personal Firewall, the Network Associates Desktop Firewall, BlackIce, and one other I can't recall the name of. Just some extra info to chew on for possibility. Good luck, and let us know what you find... -Mark -Original Message- From: Godswill Oletu [mailto:[EMAIL PROTECTED]] Sent: Friday, November 29, 2002 12:04 PM To: Mark W. Odette II; [EMAIL PROTECTED] Subject: Re: I seems Confused.Peer-to-to TCP/IP Network [7:58255] Hi Mark, I have done all that. The crossover cable is okay. NeTBEUI is working fine. I can see both computers through Network Neigbourhood; copy files from one computer to the other. Everthing about NetBEUI is kool. I have alos edited the hosts/lmhost files on each computer (this only help to resolve the IP Address to the netbios name.) IP addresses are Computer A=192.168.0.1/255.255.255.0 and Computer B=192.168.0.2/255.255.255.0 On Computer A, I can ping 192.168.0.1, localhost and 127.0.0.1 and it will response fine. On Computer B, I can also ping 192.168.0.2, localhost and 127.0.0.1 and it will response fine. (TCP/IP stack seems perfectly installed)!!! But I cannot ping A from B, neither can I ping B from A. This is the dumbest thing I have ever done and it is messing me up. Or is it impossible? - Original Message - From: Mark W. Odette II To: Sent: Thursday, November 28, 2002 8:22 PM Subject: RE: I seems Confused.Peer-to-to TCP/IP Network [7:58255] Check your subnet masks for each computer. Either specify Computer B as the default gateway for Computer A and vice-versa, or don't specify a default gateway at all. After that, you have to configure the lmhosts/hosts files if you want to resolve machine names between each other (quickly). Verify that your cross-over cable is good, or plug each computer into a hub/switch. It's that simple. Cheers! -Mark -Original Message- From: Godswill Oletu [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 28, 2002 6:26 PM To: [EMAIL PROTECTED] Subject: I seems Confused.Peer-to-to TCP/IP Network [7:58255] Hi all, Where are mine going wrong? Has anyone implemented a Peer-to-Peer network involving just two computers with ONLY TCP/IP Protocol? I have been trying to do it but keeping failing. NetBEUI is working fine, I can transfer files in between both computers. But TCP/IP protocolis not working across. Am trying to connect a Window NT to Windows 98 Machine. I used the normal cross over cable (1-3, 2-6, 3-1, 6-2) connection. localhost pings alright, IP-address to each machine can be pinged from that very machine only. Hosts file have been edited and it is resolving fine...but I can ping one machine from the other. I have double checked everything but cannot figure out whats happening. I know
RE: I seems Confused.....Peer-to-to TCP/IP Network [7:58255]
Can a WIN98 machine act as a router? I have had issue slike this before, and they are normally attributed to dodgy IP stacks, especially on win98 machines. Godswill, can you post the results of a winipcfg on the 98 machine and a ipconfig /all on the nt machine? Do you have IP forwarding enabled on the NT machine? Do you have any internet connection sharing enabled on the 98 machine? The first paragraph of your email below states that you have 192.168.0.1 as the DG on both boxes, is this correct? -Original Message- From: Godswill Oletu [mailto:[EMAIL PROTECTED]] Sent: 29 November 2002 20:43 To: [EMAIL PROTECTED] Subject: Re: I seems Confused.Peer-to-to TCP/IP Network [7:58255] Hi Mark, Actually before now I had been checking the routing table 'route print' and also the netbios cache. On Computer A with IP address 192.168.0.1, there is a route to network 192.168.0.0 through interface 192.168.0.1 and on Computer B with IP address 192.168.0.2, there is a route to network 192.168.0.0 through interface 192.168.0.1 (seem great!). I will try reinstalling the OS, because I look stupified, however currently am trying it on another computer to see what happens. What I did not mention is that, on both Computer A and B, I have two NICs each. My intention is to implement double NATing. Computer B is connected to the Internet through RJ45 broadband and this connection is working great!. My goal was to NAT this connection to Computer A and then NAT it again from computer A downstream (I have not reached here), I do not think the presense of two NICs in each computer would have any thing to do with thei. Thanks men! Godswill - Original Message - From: Mark W. Odette II To: Sent: Friday, November 29, 2002 2:03 PM Subject: RE: I seems Confused.Peer-to-to TCP/IP Network [7:58255] Oletu- What you are trying to do is not impossible. Many of us do this all the time to migrate data from one machine to another without burdening the Hub-based LAN or if the computer is all by itself and is being upgraded. Case in point is the situation where a Win9x/Pentium 166Mhz workstation is being replaced with a Windows XP/Pentium III 1.8Ghz workstation... NetBEUI isn't a protocol option on XP, as it isn't supported anymore- So, it's TCP/IP or IPX! Configuration of each computer is correct; the fact that you can operate with success running NetBEUI says that your physical layer is also solid, i.e., NIC's and Cross-over cable. Next thing to do is (for informational purposes) to 'route print' or a 'netstat -r' at the command line to determine the TCP/IP stack has proper routing information. Optionally issue the 'nbtstat -c' or 'nbtstat -r' to see if you are getting any netbios caching... After collecting this information, I would remove the TCP/IP protocol, reboot, reinstall TCP/IP protocol, install most recent SP for OS, and test again... If that doesn't resolve the problem, then seek out replacement drivers for the NIC(s). This pretty much addresses every possibility of failure between two Windows-based computers that are directly connected to each other with a cross-over cable. ... One other thought- You wouldn't have some kind of personal firewall installed/previously installed on either one of these computers by chance, would you!?!?! I have seen all kinds of crazy stuff occur on MS boxes that had had any of the different flavors of Personal Firewalls installed, which usually required complete removal of the TCP/IP protocol, and then sifting through the networking portion of the registry to recover the machine. The alternative was to reinstall the OS from scratch. The firewalls in question were the Norton Personal Firewall, the Network Associates Desktop Firewall, BlackIce, and one other I can't recall the name of. Just some extra info to chew on for possibility. Good luck, and let us know what you find... -Mark -Original Message- From: Godswill Oletu [mailto:[EMAIL PROTECTED]] Sent: Friday, November 29, 2002 12:04 PM To: Mark W. Odette II; [EMAIL PROTECTED] Subject: Re: I seems Confused.Peer-to-to TCP/IP Network [7:58255] Hi Mark, I have done all that. The crossover cable is okay. NeTBEUI is working fine. I can see both computers through Network Neigbourhood; copy files from one computer to the other. Everthing about NetBEUI is kool. I have alos edited the hosts/lmhost files on each computer (this only help to resolve the IP Address to the netbios name.) IP addresses are Computer A=192.168.0.1/255.255.255.0 and Computer B=192.168.0.2/255.255.255.0 On Computer A, I can ping 192.168.0.1, localhost and 127.0.0.1 and it will response fine. On Computer B, I can also ping 192.168.0.2, localhost and 127.0.0.1 and it will response fine. (TCP/IP stack seems perfectly installed)!!! But I cannot ping A from B, neither can I ping B from A. This is the dumbest thing I have ever done
RE: I seems Confused.....Peer-to-to TCP/IP Network [7:58255]
Does another WINNT system talk to the other one? -Original Message- From: Godswill Oletu [mailto:[EMAIL PROTECTED]] Sent: 29 November 2002 21:45 To: [EMAIL PROTECTED] Subject: Re: I seems Confused.Peer-to-to TCP/IP Network [7:58255] Hi Mark, So far... I brought in another Win98 system. TCP/IP and NetBEUI is working great between the two Win98 Systems. I can Ping and do all sorts of things between those two Win98 Systems. Now, same old problem, TCP/IP cannot work between Win98 and WinNT 4.0, only NetBEUI is working so far. I just swap the cable to a Win98 system and it start working. Have you personally implemented a peer to peer network between a WinNT 4.0 and Win98 System? Everything on the WinNT system looks okay, however am determined to fine a logical conclusion to this. What are not getting right now? Regards. Godswill - Original Message - From: Mark W. Odette II To: Sent: Friday, November 29, 2002 2:03 PM Subject: RE: I seems Confused.Peer-to-to TCP/IP Network [7:58255] Oletu- What you are trying to do is not impossible. Many of us do this all the time to migrate data from one machine to another without burdening the Hub-based LAN or if the computer is all by itself and is being upgraded. Case in point is the situation where a Win9x/Pentium 166Mhz workstation is being replaced with a Windows XP/Pentium III 1.8Ghz workstation... NetBEUI isn't a protocol option on XP, as it isn't supported anymore- So, it's TCP/IP or IPX! Configuration of each computer is correct; the fact that you can operate with success running NetBEUI says that your physical layer is also solid, i.e., NIC's and Cross-over cable. Next thing to do is (for informational purposes) to 'route print' or a 'netstat -r' at the command line to determine the TCP/IP stack has proper routing information. Optionally issue the 'nbtstat -c' or 'nbtstat -r' to see if you are getting any netbios caching... After collecting this information, I would remove the TCP/IP protocol, reboot, reinstall TCP/IP protocol, install most recent SP for OS, and test again... If that doesn't resolve the problem, then seek out replacement drivers for the NIC(s). This pretty much addresses every possibility of failure between two Windows-based computers that are directly connected to each other with a cross-over cable. ... One other thought- You wouldn't have some kind of personal firewall installed/previously installed on either one of these computers by chance, would you!?!?! I have seen all kinds of crazy stuff occur on MS boxes that had had any of the different flavors of Personal Firewalls installed, which usually required complete removal of the TCP/IP protocol, and then sifting through the networking portion of the registry to recover the machine. The alternative was to reinstall the OS from scratch. The firewalls in question were the Norton Personal Firewall, the Network Associates Desktop Firewall, BlackIce, and one other I can't recall the name of. Just some extra info to chew on for possibility. Good luck, and let us know what you find... -Mark -Original Message- From: Godswill Oletu [mailto:[EMAIL PROTECTED]] Sent: Friday, November 29, 2002 12:04 PM To: Mark W. Odette II; [EMAIL PROTECTED] Subject: Re: I seems Confused.Peer-to-to TCP/IP Network [7:58255] Hi Mark, I have done all that. The crossover cable is okay. NeTBEUI is working fine. I can see both computers through Network Neigbourhood; copy files from one computer to the other. Everthing about NetBEUI is kool. I have alos edited the hosts/lmhost files on each computer (this only help to resolve the IP Address to the netbios name.) IP addresses are Computer A=192.168.0.1/255.255.255.0 and Computer B=192.168.0.2/255.255.255.0 On Computer A, I can ping 192.168.0.1, localhost and 127.0.0.1 and it will response fine. On Computer B, I can also ping 192.168.0.2, localhost and 127.0.0.1 and it will response fine. (TCP/IP stack seems perfectly installed)!!! But I cannot ping A from B, neither can I ping B from A. This is the dumbest thing I have ever done and it is messing me up. Or is it impossible? - Original Message - From: Mark W. Odette II To: Sent: Thursday, November 28, 2002 8:22 PM Subject: RE: I seems Confused.Peer-to-to TCP/IP Network [7:58255] Check your subnet masks for each computer. Either specify Computer B as the default gateway for Computer A and vice-versa, or don't specify a default gateway at all. After that, you have to configure the lmhosts/hosts files if you want to resolve machine names between each other (quickly). Verify that your cross-over cable is good, or plug each computer into a hub/switch. It's that simple. Cheers! -Mark -Original Message- From: Godswill Oletu [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 28, 2002 6:26 PM To: [EMAIL
Re: I seems Confused.....Peer-to-to TCP/IP Network [7:58255]
Hi, At this level what am really concern about is being able to Ping the WinNT system (Service Pack 6) from the Win98 System and also the other way round. After this I will be able to to take care of the ICS and NAT issue. I just first want TCP/IP to run between both systems. Here is my TCP/IP config for each System: (Major concern is linking Ethernet adapter F5D50006 in Windows NT with Ethernet adapter 3 in Windows 98 below:) Windows NT IP Configuration Host Name . . . . . . . . . : xbsabga001 DNS Servers . . . . . . . . : Node Type . . . . . . . . . : Broadcast NetBIOS Scope ID. . . . . . : IP Routing Enabled. . . . . : Yes WINS Proxy Enabled. . . . . : No NetBIOS Resolution Uses DNS : No PPP adapter NdisWan5: Description . . . . . . . . : NdisWan5 NdisWan Adapter Physical Address. . . . . . : 00-00-00-00-00-00 DHCP Enabled. . . . . . . . : No IP Address. . . . . . . . . : 0.0.0.0 Subnet Mask . . . . . . . . : 0.0.0.0 Default Gateway . . . . . . : PPP adapter NdisWan4: Description . . . . . . . . : NdisWan4 NdisWan Adapter Physical Address. . . . . . : 00-00-00-00-00-00 DHCP Enabled. . . . . . . . : No IP Address. . . . . . . . . : 0.0.0.0 Subnet Mask . . . . . . . . : 0.0.0.0 Default Gateway . . . . . . : Ethernet adapter AMDPCN1: Description . . . . . . . . : AMDPCN1 AMD PCNET Family Ethernet Adapter Physical Address. . . . . . : 00-80-5F-5C-1D-CC DHCP Enabled. . . . . . . . : No IP Address. . . . . . . . . : 100.100.0.1 Subnet Mask . . . . . . . . : 255.255.0.0 Default Gateway . . . . . . : Ethernet adapter F5D50006: Description . . . . . . . . : F5D50006 F5D5000, PCI Card/Desktop Network PCI Card Physical Address. . . . . . : 00-30-BD-04-82-D6 DHCP Enabled. . . . . . . . : No IP Address. . . . . . . . . : 192.168.0.1 Subnet Mask . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . : (Major concern is linking Ethernet adapter 3, below with Ethernet adapter F5D50006 above) Windows 98 IP Configuration Host Name . . . . . . . . . : ewwax011 DNS Servers . . . . . . . . : n.n.n.n Node Type . . . . . . . . . : Broadcast NetBIOS Scope ID. . . . . . : IP Routing Enabled. . . . . : No WINS Proxy Enabled. . . . . : No NetBIOS Resolution Uses DNS : Yes 0 Ethernet adapter : Description . . . . . . . . : PPP Adapter. Physical Address. . . . . . : 4B-A5-53-64-AA-B0 DHCP Enabled. . . . . . . . : Yes IP Address. . . . . . . . . : n.n.n.n Subnet Mask . . . . . . . . : 255.255.0.0 Default Gateway . . . . . . : n.n.n.n DHCP Server . . . . . . . . : 255.255.255.255 Primary WINS Server . . . . : Secondary WINS Server . . . : Lease Obtained. . . . . . . : 01 01 80 12:00:00 AM Lease Expires . . . . . . . : 01 01 80 12:00:00 AM 1 Ethernet adapter : Description . . . . . . . . : PPP Adapter. Physical Address. . . . . . : 4A-65-B3-5A-B0-0C DHCP Enabled. . . . . . . . : Yes IP Address. . . . . . . . . : 0.0.0.0 Subnet Mask . . . . . . . . : 0.0.0.0 Default Gateway . . . . . . : DHCP Server . . . . . . . . : 255.255.255.255 Primary WINS Server . . . . : Secondary WINS Server . . . : Lease Obtained. . . . . . . : Lease Expires . . . . . . . : 2 Ethernet adapter : Description . . . . . . . . : OVISLINK NWAY NIC Physical Address. . . . . . : 00-4A-54-E1-3B-90 DHCP Enabled. . . . . . . . : Yes IP Address. . . . . . . . . : n.n.n.n Subnet Mask . . . . . . . . : 255.255.240.0 Default Gateway . . . . . . : n.n.n.n DHCP Server . . . . . . . . : n.n.n.n Primary WINS Server . . . . : Secondary WINS Server . . . : Lease Obtained. . . . . . . : 11 29 02 4:07:58 PM Lease Expires . . . . . . . : 11 30 02 1:36:14 AM 3 Ethernet adapter : Description . . . . . . . . : D-Link DFE-530TX+ PCI Adapter Physical Address. . . . . . : 00-02-AD-DE-D5-A9 DHCP Enabled. . . . . . . . : No IP Address. . . . . . . . . : 192.168.0.2 Subnet Mask . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . : Primary WINS Server . . . . : Secondary WINS Server . . . : Lease Obtained. . . . . . . : Lease Expires . . . . . . . : . Thanks man! Regards. Godswill - Original Message - From: Symon Thurlow To: Godswill Oletu ; Sent: Friday, November 29, 2002 5:12 PM Subject: RE: I seems Confused.Peer-to-to TCP/IP Network [7:58255] Can a WIN98 machine act as a router? I have had issue slike this before, and they are normally attributed to dodgy IP stacks, especially on win98 machines. Godswill, can you post the results of a winipcfg on the 98 machine and a ipconfig /all on the nt machine? Do you have IP forwarding enabled on the NT machine? Do you have any internet connection sharing enabled on the 98 machine? The first paragraph of your email below states that you have 192.168.0.1 as the DG on both boxes, is this correct? -Original Message- From: Godswill Oletu [mailto:[EMAIL PROTECTED]] Sent: 29 November 2002 20:43 To: [EMAIL PROTECTED] Subject: Re: I seems Confused.Peer-to-to TCP/IP Network [7:58255] Hi Mark, Actually before
Re: I seems Confused.....Peer-to-to TCP/IP Network [7:58255]
I have just one NT system at home. - Original Message - From: Symon Thurlow To: Sent: Friday, November 29, 2002 5:15 PM Subject: RE: I seems Confused.Peer-to-to TCP/IP Network [7:58255] Does another WINNT system talk to the other one? -Original Message- From: Godswill Oletu [mailto:[EMAIL PROTECTED]] Sent: 29 November 2002 21:45 To: [EMAIL PROTECTED] Subject: Re: I seems Confused.Peer-to-to TCP/IP Network [7:58255] Hi Mark, So far... I brought in another Win98 system. TCP/IP and NetBEUI is working great between the two Win98 Systems. I can Ping and do all sorts of things between those two Win98 Systems. Now, same old problem, TCP/IP cannot work between Win98 and WinNT 4.0, only NetBEUI is working so far. I just swap the cable to a Win98 system and it start working. Have you personally implemented a peer to peer network between a WinNT 4.0 and Win98 System? Everything on the WinNT system looks okay, however am determined to fine a logical conclusion to this. What are not getting right now? Regards. Godswill - Original Message - From: Mark W. Odette II To: Sent: Friday, November 29, 2002 2:03 PM Subject: RE: I seems Confused.Peer-to-to TCP/IP Network [7:58255] Oletu- What you are trying to do is not impossible. Many of us do this all the time to migrate data from one machine to another without burdening the Hub-based LAN or if the computer is all by itself and is being upgraded. Case in point is the situation where a Win9x/Pentium 166Mhz workstation is being replaced with a Windows XP/Pentium III 1.8Ghz workstation... NetBEUI isn't a protocol option on XP, as it isn't supported anymore- So, it's TCP/IP or IPX! Configuration of each computer is correct; the fact that you can operate with success running NetBEUI says that your physical layer is also solid, i.e., NIC's and Cross-over cable. Next thing to do is (for informational purposes) to 'route print' or a 'netstat -r' at the command line to determine the TCP/IP stack has proper routing information. Optionally issue the 'nbtstat -c' or 'nbtstat -r' to see if you are getting any netbios caching... After collecting this information, I would remove the TCP/IP protocol, reboot, reinstall TCP/IP protocol, install most recent SP for OS, and test again... If that doesn't resolve the problem, then seek out replacement drivers for the NIC(s). This pretty much addresses every possibility of failure between two Windows-based computers that are directly connected to each other with a cross-over cable. ... One other thought- You wouldn't have some kind of personal firewall installed/previously installed on either one of these computers by chance, would you!?!?! I have seen all kinds of crazy stuff occur on MS boxes that had had any of the different flavors of Personal Firewalls installed, which usually required complete removal of the TCP/IP protocol, and then sifting through the networking portion of the registry to recover the machine. The alternative was to reinstall the OS from scratch. The firewalls in question were the Norton Personal Firewall, the Network Associates Desktop Firewall, BlackIce, and one other I can't recall the name of. Just some extra info to chew on for possibility. Good luck, and let us know what you find... -Mark -Original Message- From: Godswill Oletu [mailto:[EMAIL PROTECTED]] Sent: Friday, November 29, 2002 12:04 PM To: Mark W. Odette II; [EMAIL PROTECTED] Subject: Re: I seems Confused.Peer-to-to TCP/IP Network [7:58255] Hi Mark, I have done all that. The crossover cable is okay. NeTBEUI is working fine. I can see both computers through Network Neigbourhood; copy files from one computer to the other. Everthing about NetBEUI is kool. I have alos edited the hosts/lmhost files on each computer (this only help to resolve the IP Address to the netbios name.) IP addresses are Computer A=192.168.0.1/255.255.255.0 and Computer B=192.168.0.2/255.255.255.0 On Computer A, I can ping 192.168.0.1, localhost and 127.0.0.1 and it will response fine. On Computer B, I can also ping 192.168.0.2, localhost and 127.0.0.1 and it will response fine. (TCP/IP stack seems perfectly installed)!!! But I cannot ping A from B, neither can I ping B from A. This is the dumbest thing I have ever done and it is messing me up. Or is it impossible? - Original Message - From: Mark W. Odette II To: Sent: Thursday, November 28, 2002 8:22 PM Subject: RE: I seems Confused.Peer-to-to TCP/IP Network [7:58255] Check your subnet masks for each computer. Either specify Computer B as the default gateway for Computer A and vice-versa, or don't specify a default gateway at all. After that, you have to configure the lmhosts/hosts files if you want to resolve machine names between each other
Re: I seems Confused.....Peer-to-to TCP/IP Network [7:58255]
Hi, At this level what am really concern about is being able to Ping the WinNT system (Service Pack 6) from the Win98 System and also the other way round. After this I will be able to to take care of the ICS and NAT issue. I just first want TCP/IP to run between both systems. Here is my TCP/IP config for each System: (Major concern is linking Ethernet adapter F5D50006 in Windows NT with Ethernet adapter 3 in Windows 98 below:) Windows NT IP Configuration Host Name . . . . . . . . . : xbsabga001 DNS Servers . . . . . . . . : Node Type . . . . . . . . . : Broadcast NetBIOS Scope ID. . . . . . : IP Routing Enabled. . . . . : Yes WINS Proxy Enabled. . . . . : No NetBIOS Resolution Uses DNS : No PPP adapter NdisWan5: Description . . . . . . . . : NdisWan5 NdisWan Adapter Physical Address. . . . . . : 00-00-00-00-00-00 DHCP Enabled. . . . . . . . : No IP Address. . . . . . . . . : 0.0.0.0 Subnet Mask . . . . . . . . : 0.0.0.0 Default Gateway . . . . . . : PPP adapter NdisWan4: Description . . . . . . . . : NdisWan4 NdisWan Adapter Physical Address. . . . . . : 00-00-00-00-00-00 DHCP Enabled. . . . . . . . : No IP Address. . . . . . . . . : 0.0.0.0 Subnet Mask . . . . . . . . : 0.0.0.0 Default Gateway . . . . . . : Ethernet adapter AMDPCN1: Description . . . . . . . . : AMDPCN1 AMD PCNET Family Ethernet Adapter Physical Address. . . . . . : 00-80-5F-5C-1D-CC DHCP Enabled. . . . . . . . : No IP Address. . . . . . . . . : 100.100.0.1 Subnet Mask . . . . . . . . : 255.255.0.0 Default Gateway . . . . . . : Ethernet adapter F5D50006: Description . . . . . . . . : F5D50006 F5D5000, PCI Card/Desktop Network PCI Card Physical Address. . . . . . : 00-30-BD-04-82-D6 DHCP Enabled. . . . . . . . : No IP Address. . . . . . . . . : 192.168.0.1 Subnet Mask . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . : (Major concern is linking Ethernet adapter 3, below with Ethernet adapter F5D50006 above) Windows 98 IP Configuration Host Name . . . . . . . . . : ewwax011 DNS Servers . . . . . . . . : n.n.n.n Node Type . . . . . . . . . : Broadcast NetBIOS Scope ID. . . . . . : IP Routing Enabled. . . . . : No WINS Proxy Enabled. . . . . : No NetBIOS Resolution Uses DNS : Yes 0 Ethernet adapter : Description . . . . . . . . : PPP Adapter. Physical Address. . . . . . : 4B-A5-53-64-AA-B0 DHCP Enabled. . . . . . . . : Yes IP Address. . . . . . . . . : n.n.n.n Subnet Mask . . . . . . . . : 255.255.0.0 Default Gateway . . . . . . : n.n.n.n DHCP Server . . . . . . . . : 255.255.255.255 Primary WINS Server . . . . : Secondary WINS Server . . . : Lease Obtained. . . . . . . : 01 01 80 12:00:00 AM Lease Expires . . . . . . . : 01 01 80 12:00:00 AM 1 Ethernet adapter : Description . . . . . . . . : PPP Adapter. Physical Address. . . . . . : 4A-65-B3-5A-B0-0C DHCP Enabled. . . . . . . . : Yes IP Address. . . . . . . . . : 0.0.0.0 Subnet Mask . . . . . . . . : 0.0.0.0 Default Gateway . . . . . . : DHCP Server . . . . . . . . : 255.255.255.255 Primary WINS Server . . . . : Secondary WINS Server . . . : Lease Obtained. . . . . . . : Lease Expires . . . . . . . : 2 Ethernet adapter : Description . . . . . . . . : OVISLINK NWAY NIC Physical Address. . . . . . : 00-4A-54-E1-3B-90 DHCP Enabled. . . . . . . . : Yes IP Address. . . . . . . . . : n.n.n.n Subnet Mask . . . . . . . . : 255.255.240.0 Default Gateway . . . . . . : n.n.n.n DHCP Server . . . . . . . . : n.n.n.n Primary WINS Server . . . . : Secondary WINS Server . . . : Lease Obtained. . . . . . . : 11 29 02 4:07:58 PM Lease Expires . . . . . . . : 11 30 02 1:36:14 AM 3 Ethernet adapter : Description . . . . . . . . : D-Link DFE-530TX+ PCI Adapter Physical Address. . . . . . : 00-02-AD-DE-D5-A9 DHCP Enabled. . . . . . . . : No IP Address. . . . . . . . . : 192.168.0.2 Subnet Mask . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . : Primary WINS Server . . . . : Secondary WINS Server . . . : Lease Obtained. . . . . . . : Lease Expires . . . . . . . : . Thanks man! Regards. Godswill - Original Message - From: Symon Thurlow To: Godswill Oletu ; Sent: Friday, November 29, 2002 5:12 PM Subject: RE: I seems Confused.Peer-to-to TCP/IP Network [7:58255] Can a WIN98 machine act as a router? I have had issue slike this before, and they are normally attributed to dodgy IP stacks, especially on win98 machines. Godswill, can you post the results of a winipcfg on the 98 machine and a ipconfig /all on the nt machine? Do you have IP forwarding enabled on the NT machine? Do you have any internet connection sharing enabled on the 98 machine? The first paragraph of your email below states that you have 192.168.0.1 as the DG on both boxes, is this correct? -Original Message- From: Godswill Oletu [mailto:[EMAIL PROTECTED]] Sent: 29 November 2002 20:43 To: [EMAIL PROTECTED] Subject: Re: I seems Confused.Peer-to-to TCP/IP Network [7:58255] Hi Mark, Actually before
Re: I seems Confused.....Peer-to-to TCP/IP Network [7:58255]
two nics will have a lot to do it Godswill Oletu wrote: Hi Mark, Actually before now I had been checking the routing table 'route print' and also the netbios cache. On Computer A with IP address 192.168.0.1, there is a route to network 192.168.0.0 through interface 192.168.0.1 and on Computer B with IP address 192.168.0.2, there is a route to network 192.168.0.0 through interface 192.168.0.1 (seem great!). I will try reinstalling the OS, because I look stupified, however currently am trying it on another computer to see what happens. What I did not mention is that, on both Computer A and B, I have two NICs each. My intention is to implement double NATing. Computer B is connected to the Internet through RJ45 broadband and this connection is working great!. My goal was to NAT this connection to Computer A and then NAT it again from computer A downstream (I have not reached here), I do not think the presense of two NICs in each computer would have any thing to do with thei. Thanks men! Godswill - Original Message - From: Mark W. Odette II To: Sent: Friday, November 29, 2002 2:03 PM Subject: RE: I seems Confused.Peer-to-to TCP/IP Network [7:58255] Oletu- What you are trying to do is not impossible. Many of us do this all the time to migrate data from one machine to another without burdening the Hub-based LAN or if the computer is all by itself and is being upgraded. Case in point is the situation where a Win9x/Pentium 166Mhz workstation is being replaced with a Windows XP/Pentium III 1.8Ghz workstation... NetBEUI isn't a protocol option on XP, as it isn't supported anymore- So, it's TCP/IP or IPX! Configuration of each computer is correct; the fact that you can operate with success running NetBEUI says that your physical layer is also solid, i.e., NIC's and Cross-over cable. Next thing to do is (for informational purposes) to 'route print' or a 'netstat -r' at the command line to determine the TCP/IP stack has proper routing information. Optionally issue the 'nbtstat -c' or 'nbtstat -r' to see if you are getting any netbios caching... After collecting this information, I would remove the TCP/IP protocol, reboot, reinstall TCP/IP protocol, install most recent SP for OS, and test again... If that doesn't resolve the problem, then seek out replacement drivers for the NIC(s). This pretty much addresses every possibility of failure between two Windows-based computers that are directly connected to each other with a cross-over cable. ... One other thought- You wouldn't have some kind of personal firewall installed/previously installed on either one of these computers by chance, would you!?!?! I have seen all kinds of crazy stuff occur on MS boxes that had had any of the different flavors of Personal Firewalls installed, which usually required complete removal of the TCP/IP protocol, and then sifting through the networking portion of the registry to recover the machine. The alternative was to reinstall the OS from scratch. The firewalls in question were the Norton Personal Firewall, the Network Associates Desktop Firewall, BlackIce, and one other I can't recall the name of. Just some extra info to chew on for possibility. Good luck, and let us know what you find... -Mark -Original Message- From: Godswill Oletu [mailto:[EMAIL PROTECTED]] Sent: Friday, November 29, 2002 12:04 PM To: Mark W. Odette II; [EMAIL PROTECTED] Subject: Re: I seems Confused.Peer-to-to TCP/IP Network [7:58255] Hi Mark, I have done all that. The crossover cable is okay. NeTBEUI is working fine. I can see both computers through Network Neigbourhood; copy files from one computer to the other. Everthing about NetBEUI is kool. I have alos edited the hosts/lmhost files on each computer (this only help to resolve the IP Address to the netbios name.) IP addresses are Computer A=192.168.0.1/255.255.255.0 and Computer B=192.168.0.2/255.255.255.0 On Computer A, I can ping 192.168.0.1, localhost and 127.0.0.1 and it will response fine. On Computer B, I can also ping 192.168.0.2, localhost and 127.0.0.1 and it will response fine. (TCP/IP stack seems perfectly installed)!!! But I cannot ping A from B, neither can I ping B from A. This is the dumbest thing I have ever done and it is messing me up. Or is it impossible? - Original Message - From: Mark W. Odette II To: Sent: Thursday, November 28, 2002 8:22 PM Subject: RE: I seems Confused.Peer-to-to TCP/IP Network [7:58255] Check your subnet masks for each computer. Either specify Computer B as the default gateway for Computer A and vice-versa, or don't specify a default gateway at all. After that, you have to configure the lmhosts/hosts files if you want to resolve machine names between each other (quickly). Verify that your cross-over cable is good, or plug each computer into a hub/switch. It's that simple. Cheers! -Mark -Original Message- From: Godswill Oletu [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 28
RE: I seems Confused.....Peer-to-to TCP/IP Network [7:58255]
Check your subnet masks for each computer. Either specify Computer B as the default gateway for Computer A and vice-versa, or don't specify a default gateway at all. After that, you have to configure the lmhosts/hosts files if you want to resolve machine names between each other (quickly). Verify that your cross-over cable is good, or plug each computer into a hub/switch. It's that simple. Cheers! -Mark -Original Message- From: Godswill Oletu [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 28, 2002 6:26 PM To: [EMAIL PROTECTED] Subject: I seems Confused.Peer-to-to TCP/IP Network [7:58255] Hi all, Where are mine going wrong? Has anyone implemented a Peer-to-Peer network involving just two computers with ONLY TCP/IP Protocol? I have been trying to do it but keeping failing. NetBEUI is working fine, I can transfer files in between both computers. But TCP/IP protocolis not working across. Am trying to connect a Window NT to Windows 98 Machine. I used the normal cross over cable (1-3, 2-6, 3-1, 6-2) connection. localhost pings alright, IP-address to each machine can be pinged from that very machine only. Hosts file have been edited and it is resolving fine...but I can ping one machine from the other. I have double checked everything but cannot figure out whats happening. I know I have been implementing peer-to-peer networks but I had not gotten into this kind of scenario.. Any forethought would help, thanks Godswill Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=58257t=58255 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: I seems Confused.....Peer-to-to TCP/IP Network [7:58255]
What are the IP/Masks that you are using? Is it just hostnames you can't ping by or the IP's themselves just to be clear. Otherwise the only thing I can think of is that some USB network cards don't like to be peer to peer and only work when connected to a switch/hub. John -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Godswill Oletu Sent: Thursday, November 28, 2002 7:26 PM To: [EMAIL PROTECTED] Subject: I seems Confused.Peer-to-to TCP/IP Network [7:58255] Hi all, Where are mine going wrong? Has anyone implemented a Peer-to-Peer network involving just two computers with ONLY TCP/IP Protocol? I have been trying to do it but keeping failing. NetBEUI is working fine, I can transfer files in between both computers. But TCP/IP protocolis not working across. Am trying to connect a Window NT to Windows 98 Machine. I used the normal cross over cable (1-3, 2-6, 3-1, 6-2) connection. localhost pings alright, IP-address to each machine can be pinged from that very machine only. Hosts file have been edited and it is resolving fine...but I can ping one machine from the other. I have double checked everything but cannot figure out whats happening. I know I have been implementing peer-to-peer networks but I had not gotten into this kind of scenario.. Any forethought would help, thanks Godswill Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=58266t=58255 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
