Win XP Home/Direct cable connect win98SE

Hi, Phelmich,
You can ping each way, so it sounds like the firewall is indeed irrelevant.

I saw that you told Newt that you have logons with PWDs now, but you didn't say if you added the XP user to the 98 Users group with the same PWD. I don't know if that is exactly necessary since it's the machine that is a member of the workgroup, not the user. Still, I'd give it a shot.

Ever wonder how people can hack networks when it takes this much effort to get them to run right? Maybe taking things apart is easier than building them.

How about BrowseMaster collisions? I don't think Newt put much stock in that when he helped me with my problem, and I don't know what types of problems result from them. I wouldn't hurt to try disabling it on the XP machine (it runs as a service I think.)

Good luck, I'll be checking in later to see how this gets resolved. ~Paul (pleblanc)

 

A minor detail but you said, "run Netbui over TCP/IP" is checked but grayed out ". It really reads NetBIOS over TCP/IP. Not critical in this instance but FWIW, NetBeui is a full network protocol (soup-to-nuts thing for moving network packets around) while NetBIOS (Network Basic Input Output System) is only an API that augments the DOS BIOS by adding special functions for local area networks.

And pleblanc13's suggestion to only allow one PC to act as master browser is a good one. Since it is very simple to disable browser service on XP, that's probably the way to go.

I get the feeling this is a single setting somewhere that isn't right. More information needed at this point so please do and post the following - and note that when you send the results of a command to a file, you will not see the results on your screen. The contents of each text file you create needs to be posted here with some way to identify which machine did what to whom:

1. Ping each PC from the other by IP address but add the -a switch to see if they are aware of the PC name of the other machine. Ex:

Ping -a 192.168.0.2 > c:\pingit.txt which should give you something like this (from my network so use your own addresses)

Ping -a 172.29.8.253
Pinging cabpdc.cab.pmu.com [172.29.8.253] with 32 bytes of data:
Reply from 172.29.8.253: bytes=32 time<1ms TTL=128
...... (more stuff)

2. Post the IP configuration information. Done differently on the two systems and only from XP can you do it the easy way. With 98 you'll have to send it to a nice GUI screen and then type all the information to post here. Note the ALL.

On the XP system, start~run~cmd then
ipconfig /all > c:\XP-info.txt.

On the 98 system, start~run~winipcfg then click the button for details and copy all the information.

3. The contents of your hosts files and their locations (which gotta be different on 98 & XP to work). BTW - with hosts files on the machines, you don't need the LMHosts since they'll never be seen or used.

4. The PC names and workgroup name. Since NetBeui doesn't use IP at all and relies totally on the PC name & workgroup name, the fact that loading that didn't cure you makes me think there may be a problem with the names.

 

Hi Newt and Pleblanc,

Thanks a lot for your efforts to try to help me !
The good news is that my problem is solved at last, though I am still puzzled.

After I posted my initial question here I read a few more guides and walkthoughs on the Net, and had indeed made sure that the 98 user ID/pw was added to the Users and Groups on XP. That didnt help. (though it might have still been blocking me now if I hadn't).
I basically tried everything possible with TCP/IP and NetBios and Netbui that I could think of and couldn't make it work.
I never did paste the ipconfig info here, precisely because it wasn't easy to copy/paste out of the 98 GUI, and I'd have to move the xp.out file from XP via a floppy to this 98 box (which I use to post this message) since only that has Internet access.

Anyway. In the end it turns out I needed a darn *Novell* protocol (IPX/SPX) to make my *Microsoft* OS's talk to each other.
When I added Netbios to XP I noticed it automatically added IPX, so as a long shot I also added IPX to the 98 box, and voila ! it worked.
My network properties are a bit of a jumble now I think after the various attempts, and later I'll try to slowly remove previous efforts one by one (eg Hosts file, delete netbios etc) and see if the connection holds up.

Thanks for your help, I now move to Phase 2, trying to give both machines Internet access

 

Hmmmmm

That only proves that something is not right.

IPX/SPX is an excellent protocol developed by and mainly used by Novell. It should not be your last and only resort.

Are you sure that somewhere you have not removed "Client for Microsoft networks" or have "Client for Novell networks" installed instead, or set to Primary network logon?

If it works and you are tired of this process, then forget it.

But it may bite you later!

If you wish to continue this for a short time more then at least get us the ping results that Newt requested on each computer.

Mike

 

It works!

Ok guys,

Have had great success today. Switched the PC locations and the Dell (XP) is now my main machine. Making 98 have internet access through ICS on XP was a breeze. My network (file shares) is still intact, presumably due to IPX.

As requested here is the output of ipconfig on the XP box, I'll try to post additional details later if possible.



Windows IP Configuration



Host Name . . . . . . . . . . . . : Dell

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : Yes

WINS Proxy Enabled. . . . . . . . : No



Ethernet adapter Internet NIC:



Connection-specific DNS Suffix . : arnhem.chello.nl

Description . . . . . . . . . . . : 3Com EtherLink XL 10/100 PCI TX NIC (3C905B-TX)

Physical Address. . . . . . . . . : 00-50-DA-44-6D-07

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 62.194.139.117

Subnet Mask . . . . . . . . . . . : 255.255.254.0

Default Gateway . . . . . . . . . : 62.194.138.1

DHCP Server . . . . . . . . . . . : 212.142.28.180

DNS Servers . . . . . . . . . . . : 212.142.28.66

212.142.28.67

Lease Obtained. . . . . . . . . . : Sunday, June 01, 2003 9:13:18 AM

Lease Expires . . . . . . . . . . : Saturday, June 07, 2003 10:30:42 PM



Ethernet adapter Home LAN:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connection

Physical Address. . . . . . . . . : 00-07-E9-E9-7A-DF

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 192.168.0.1

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . :

Here are the ping results from XP to 98 :



Pinging Dragon.mshome.net [192.168.0.149] with 32 bytes of data:



Reply from 192.168.0.149: bytes=32 time<1ms TTL=128

Reply from 192.168.0.149: bytes=32 time<1ms TTL=128

Reply from 192.168.0.149: bytes=32 time<1ms TTL=128

Reply from 192.168.0.149: bytes=32 time<1ms TTL=128



Ping statistics for 192.168.0.149:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

note that 98 now gets the.149 address rather than .2 due to DHCP via ICS on XP.
An odd thing is that it calls the 98 box dragon.mshome while I chose my own workgroup name (ultima)....

 

You shouldn't need any DNS settings on the 98 PC or the internal LAN NIC on XP. That's probably where the dragon.mshome.net is coming from. Remove all those entries on both PCs.

And try stopping DNS service on the XP machine. I'm not completely positive with ICS but I don't think you need it running. Your internet NIC should still pick up the needed values from the ISPs DHCP server. But if it messes anything up, you can always start it again.

And while you are gathering more stuff to post here, add in, from both PCs (and you can send these to a text file to avoid typing the results to post)

nbtstat -n
nbtstat -r
nbtstat -a <remote pc name> and if that fails
nbtstat -A <remote pc ip address>

 

Newt, I don't get it - I don't get how IPX could have had any effect on phelmich's setup. Isn't IPX a protocol that just makes Novell and MS networks talk to each other?

He had finally created a User ID/PWD for the 98 user but he might have not rebooted at that time. Then he might have added IPX and rebooted, and gotten the results he got from the step before adding IPX.

It's hard to imagine the problem suddenly disappearing because of IPX. ~Paul

 

I know its weird...but rest assured I did reboot after each step, in fact the adding of IPX didnt happen until a day or so after trying the adding of the 98 User/PW to XP.

I will try to post the other stuff Newt requested soon.