Network between Win98 and XP doesn't work.

I receintly upgraded one of my PC's to XP. I had a network before upgrading using a USB connection. After upgrading I installed a hub with cables, used the wizards, check all connections and setting and even tried installing NetBEUI on the XP machine. All I can get when checking for network is the workgroup and a computer (itself). Can not share files nor the internet.
Any help?
Thanks

 

How are you trying to "share" the internet?

Please do ipconfig /all > ipsettings.txt and post the contents of ipsettings.txt to this thread.

Do you have a hub or do you have a switch?

 

By using the wizard to set up a network connection that connects to the net thru the "internet connection" network.
I ran the ipconfig /all > ipsettings.txt, but the screen flashed to fast for me to see it and I don't know where to find it. How do I get the text?
I have a SOHOWare 5 port hub. I get a power light, two lights showing the ports used with two very fast flashing light above the port lights. If I disconnect a cable I get a message on the XP machine stating that a "cable has been disconnected. "

 

Also I just noticed that I am unable to connect to any ftp site using CuteFTP. Have not changed any setting except having to do with networking. Any idea how to allow CuteFTP to access ftp sites?
Thanks

 

Search your PC for the file ipsettings.txt. It is wherever your path was set when you had the command window open.

And yup - it does flash too fast to read but you have a copy stored in that file.

If you ever have to pipe (direct) the results of a command to a file, maybe giving the full path you want would be easier. So, c:\ipsettings.txt would have put the file in C:\

 

Sorry 'bout this. I must have done something wrong. I went to start and then run. I put in "ipsetting /all>c:\ipsetting.txt" and then OK. I have run the search for the file but can not find it on ANY hard drive. Can I run the command from some other place?
Thanks

 

start~run~cmd and do it from the command window.

And make sure you have proper spaces in the command so that you have

ipconfig /all > c:\somefile.txt

with spaces after ipconfig and after /all and after >

 

I have followed your instructions to the letter (and space) but still can not find the file. I have tried caps, mixed forms with caps and without, extra spaces, less spaces, changing drives, file name, extensions and other "stuff" and still can not get it to work.
Is there a way to uninstall XP and go back to 98 but sill have the programs work without having to reinstall them?
Thanks

 

No way I know of to revert.

As for the elusive IP config data, try it the old fashioned way.

start~run~cmd
ipconfig /all

and write down the info from the screen.

 

OK. This is what I got.
Windows IP Configuration



Host Name . . . . . . . . . . . . : Connie

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : No

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



Ethernet adapter Local Area Connection:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : SiS 900-Based PCI Fast Ethernet Adapter

Physical Address. . . . . . . . . : 19-02-16-08-39-00

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

Autoconfiguration Enabled . . . . : Yes

Autoconfiguration IP Address. . . : 169.254.101.82

Subnet Mask . . . . . . . . . . . : 255.255.0.0

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


Rest of config follows next message.

 

Second half of config.

Ethernet adapter Local Area Connection 2:
Connection-specific DNS Suffix . : fireserve.net
Description . . . . . . . . . . . : FireServe Wireless Internet PCI
Physical Address. . . . . . . . . : 00-40-36-01-01-32
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 207.109.249.136
Subnet Mask . . . . . . . . . . . : 255.255.255.192
Default Gateway . . . . . . . . . : 207.109.249.129
DHCP Server . . . . . . . . . . . : 207.109.249.8
DNS Servers . . . . . . . . . . . : 207.109.249.2
207.109.249.3
Lease Obtained. . . . . . . . . . : Thursday, November 21, 2002 1:43:14 PM
Lease Expires . . . . . . . . . . : Thursday, November 21, 2002 7:43:14 PM

 

The first one you posted (169.254.101.82 / 255.255.0.0) is an XP box that can't find the network and a DHCP server on that connection but is set to autoload IP and netmask. The values are ones that will load so the PC will boot but are completely bogus. And BTW - XP doesn't mention it is having a problem but just starts up "normally" with an IP in that series and the class B subnet mask.

It usually means the NIC is fine but there is a problem with it getting a good IP address. Having crossover cable where you need straight thru of vice versa will do this but there can be other causes and I think in your case there is.
- set to automatically get IP address, etc. assigned (as yours is) but no working DHCP server it can see. The ISP one won't be available to this connection so you would need something local.
- the cable or internet/LAN device the cable connects into is bad.
- Or else there is no cable plugged in to that connection at all.

Connection 2 should work OK because with a subnet mask of 255.255.255.192, you have chunks of 64 contiguous addresses and 62 of them can be assigned to PCs. 207.109.249.136 for the PC is in the same subnet as 207.109.249.129 for the gateway so it will work. Hopefully there is a router in the area somewhere though (at the ISP) since their DHCP and DNS addresses are in a different subnet. But I'd guess it is finding the ISP & probably the internet on that connection.

If these connection#1 values are from a PC that is supposed to be connecting any others (ICS or something) to the internet, they won't be working nor will others on the LAN see it.

And I'm really not familiar with wireless and for sure don't know the name of your ISP but having the connection#2 NIC showing as a FireServe Wireless .... brand of card, I wonder if the DNS Suffix of FireServe.net is real or bogus.

Anyway, if you get the connection#1 to pick up a "real" IP address and subnet mask, you might have better luck. Or if it is on your internal LAN, if you assign it an address and netmask that will work with your LAN (usually a 192.168.0.x or 192.168.1.x / 255.255.255.0)