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 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 ============================================= This email has been content filtered and subject to spam filtering. If you consider this email is unsolicited please forward the email to [EMAIL PROTECTED] and request that the sender's domain be blocked from sending any further emails. ============================================= Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=58309&t=58255 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
