xp to 98se. node type unknown

[Guest]

i cant network my xp machine to my 98se machine. i am told i have no access and talk to my administrator. i have tried a lot of the solutions on this site. when i typed ipconfig/all on the xp machine, the node type is unknown. how do i change this to point to point?

 

[Ron Lowe]

i cant network my xp machine to my 98se machine. i am told i have no

access and talk to my administrator. i have tried a lot of the solutions on
this site. when i typed ipconfig/all on the xp machine, the node type is
unknown. how do i change this to point to point?


Unknown is normal. Leave it like that.
P-to-P will cause name resolution to fail on your network.

You need to go through more specific faultfinding.

First, have the machines got valid, compatable IP addresses?
( ipconfig /all to check )
Do you know where these IP adresses came from?
I'd assign the addreses in the following order of preference:
-> Use a broadband router to assign IP addresses automatically.
-> If you are using Internet Connection Sharing, let the ICS host
( XP ) assign addresses to the 98 box.
The XP box will get 192.168.0.1, the 98 box will get 192.168.0.x.
->If there's no Internet connection sharing or router,
then manually assign IP addresses.
XP: 192.168.0.1 mask 255.255.255.0
98: 192.168.0.1 mask 255.255.255.0


Then, can they ping each other by IP address?
-> Ensure firewalls are disabled on the LAN connection.

Then, can they ping each other by name?
-> Ensure Netbios-over-tcp/ip is enabled;
-> Ensure Ensure only one protocol ( tcp/ip ) is in use.
-> re-check all firewalls are disabled or removed.

Then, try to map a network drive.
-> Ensure simple file sharing is enabled on XP.
Then un-share and re-share the folders.

Post back with detailled answers to how you got on with
those steps, and it's likely someone can help.

List any errors exactly as they appear, it makes a difference.

 

[Guest]

QoS packet scheduler a, file an printer sharing, tcp/ip and client for microsoft networks are all enabeled on xp computer. client for mirosoft networks, microsoft family logon, file and printer sharing and tcp/ip are on the 98se pc. net bios is enabeled. i have given my xp machine an ip of 150.0.0.1 and the 98se machine has 150.0.0.2 and both have an subnet mask of 255.255.0.0 .im still cannot ping from either. i could not map a network drive. i unshared and shared all shared folders and drives. still no joy. im nearly totally sure that the all my hardware is ok. please tell me if you need any more details for a diagnosis

 

[Ron Lowe]

QoS packet scheduler a, file an printer sharing, tcp/ip and client for

microsoft networks are all enabeled on xp computer. client for mirosoft
networks, microsoft family logon, file and printer sharing and tcp/ip are on
the 98se pc. net bios is enabeled. i have given my xp machine an ip of
150.0.0.1 and the 98se machine has 150.0.0.2 and both have an subnet mask of
255.255.0.0 .im still cannot ping from either. i could not map a network
drive. i unshared and shared all shared folders and drives. still no joy. im
nearly totally sure that the all my hardware is ok. please tell me if you
need any more details for a diagnosis


You need to get the machines to ping each other by
IP address before anything else will work.

Those are not good IP addresses to use.
Use 192.168.0.1 and 192.168.0.2, mask 255.255.255.0

Can each machne ping it's own IP address?

Can each machine ping 127.0.0.1?

If the pings fail, what is the exact error message:
a timeout, or destination unreachable, or what?

post the output of an ipconfig /all on each machine for us to see.

How are the 2 machines physically connected:
via a hub, or directly with a network cable?

Are the 'link' lights illuminated on each network card?

 

[Guest]

i gave each machine the new addresses. each machine can ping itself.each machine can ping 127.0.0.1. the ip config of the xp machine looks like this
Windows IP Configuratio
--------------------------------------------------------------------------------
Host Name . . . . . . . . . . . . : fintanslapto
Primary Dns Suffix . . . . . . .
Node Type . . . . . . . . . . . . : Unknow
IP Routing Enabled. . . . . . . . : N
WINS Proxy Enabled. . . . . . . . : N

Ethernet adapter Local Area Connection 2

Connection-specific DNS Suffix .
Description . . . . . . . . . . . : Broadcom 440x 10/100 In
rolle
Physical Address. . . . . . . . . : 00-0B-DB-1A-62-E
Dhcp Enabled. . . . . . . . . . . : N
IP Address. . . . . . . . . . . . : 192.168.0.
Subnet Mask . . . . . . . . . . . : 255.255.255.
Default Gateway . . . . . . . . .
----------------------------------------------------------------------------------
the ipconfig/all of the win98 machine is like this

DHCP Enabled. . . . . . . . : Ye
IP Address. . . . . . . . . : 0.0.0.
Subnet Mask . . . . . . . . : 0.0.0.
Default Gateway . . . . . .
DHCP Server . . . . . . . . : 255.255.255.25
Primary WINS Server . . . .
Secondary WINS Server . . .
Lease Obtained. . . . . . .
Lease Expires . . . . . . .

1 Ethernet adapter

Description . . . . . . . . : Intel 82557-based Integrated Fast Etherne

Physical Address. . . . . . : 00-08-C7-F9-E3-E
DHCP Enabled. . . . . . . . : N
IP Address. . . . . . . . . : 192.168.0.
Subnet Mask . . . . . . . . : 255.255.255.
Default Gateway . . . . . .
Primary WINS Server . . . .
Secondary WINS Server . . .
Lease Obtained. . . . . . .
Lease Expires . . . . . . .

 

[Ron Lowe]

i gave each machine the new addresses. each machine can ping itself.each

machine can ping 127.0.0.1. the ip config of the xp machine looks like this
:

Windows IP Configuration
-------------------------------------------------------------------------- -------
Host Name . . . . . . . . . . . . : fintanslaptop
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom 440x 10/100 Int
roller
Physical Address. . . . . . . . . : 00-0B-DB-1A-62-E6
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
-------------------------------------------------------------------------- ---------
the ipconfig/all of the win98 machine is like this :

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 . . . . . . . :

1 Ethernet adapter :

Description . . . . . . . . : Intel 82557-based Integrated Fast Ethernet

Physical Address. . . . . . : 00-08-C7-F9-E3-E4
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 . . . . . . . :
-------------------------------------------------------------------------- -----------

lights on back of network cards are flashing. the only abnormality i can

see is on the win 98 machine. i have a campaq network card in device
manager, yet in ipconfig/all, it shows an intel based intergrated network
card.

i am connecting the two computers using a crossover cable. no hubs,

bridges, routers or any other hardware. hope this is the info you asked for.
thank you for taking the time to hemp me

The configs look OK.
The fact that they can ping themselves is good.
Time I think to look lower in the stack.

Are you 100% sure the cable is actually wired as a crossover cable?
Look at both ends, and compare the colours of the individual cores.
If they are in the same order at both ends, it's not a crossover.

It's also possible the crossover cable is causing one or other of the
network cards to fail auto-negotiation.
You could try going into the network card settings on each machine, and
forcing the settings to be the same.
Start with 10Mbit / half duplex.
Then 10Mbit / full duplex.
Then 100Mbit / half duplex
Then 100Mbit / full duplex

You might also try hooking them up via a hub or switch, and using regular
patch cables.

As regards the inconsistent description in '98 Device Manager, I don't think
that's a problem. The fact that it's pinging it's own IP address is good.
If you are concerned, then you can remove the card in device manager,
re-boot, and let it re-detect and install it. Be sure you have the drivers
at hand if you want to do this.

Just a thought:
( clutching-at-straws department. )
On the 98 machine , there's not by any chance _two_ network adapters?
One on-board, and one on a PCI card which you have plugged in?
And if so, do you have the network cable plugged into the right one?

 

[Guest]

success!!! i can connect at half duplex at 10mbps. when i put it up to 100 half duplex , it dies again. i know the cable is a crossover as i used it before with no problems. do you know any reason why it will only work at only 10 half duplex, and any solutions? thank you for all the advice. thanks thanks thanks

 

[Ron Lowe]

success!!! i can connect at half duplex at 10mbps. when i put it up to 100

half duplex , it dies again. i know the cable is a crossover as i used it
before with no problems. do you know any reason why it will only work at
only 10 half duplex, and any solutions? thank you for all the advice. thanks
thanks thanks


Is the cable home made?
Mis-wired cables are a common problem.
The pairs must be used correctly.

Home-made or not,
( I've seen 'professionally made' cables that are wrong! )
The colour codes must be as per this page:

http://www.linksys.com/faqs/default.asp?fqid=20

If they are not, cut the ends and re-terminate the cable.

 

[Guest]

i think the cable is ok, but il get a new one just in case, but just assume the cable is ok. is there anything else that could be wrong?

 

[Guest]

i have found out that i can get the network working at 10mb full duplex. if it will work at full duplex at 10 , would that not indicate that the cable is ok? what would stop it goin the full 100 full duplex?

 

[Ron Lowe]

i have found out that i can get the network working at 10mb full duplex.

if it will work at full duplex at 10 , would that not indicate that the
cable is ok? what would stop it goin the full 100 full duplex?



An incorrectly wired cable will often work OK at 10 Mbit and fail at 100.

Is the cable home-made?
Have you checked the colour coding as per the link I gave?

 

[Guest]

yes, it is a home made cable. i thought it worked at 100 before but i must have been mistaken. i will check the cable when i get in to the back of my pc. thank you for all your help good sir... happy new year...

 

[Ron Lowe]

yes, it is a home made cable. i thought it worked at 100 before but i must

have been mistaken. i will check the cable when i get in to the back of my
pc. thank you for all your help good sir... happy new year...


The most common error is the correct twisted pairs are not being observed.

It's not enough just to connect 1-1, 2-2, 3-3 and 6-6.
You need to look at the twisted pairs inside the cable.

The most common error is to use use one pair for pins 1&2,
another pair for pins 3&4, another pair for pins 5&6, and a pair for 7&8.
The wires sit neatly inside the connectors if you do it this way.

Unfortunately, this will not work.
( Well, sometimes on a short run it will, but probably not at 100 )

pins 1&2 need to be a pair. ( usually the orange pair )
pins 3&6 need to be a pair. ( usually the green pair )

Notice how the green pair is seperated to pins 3 and 6.
This is critical.

This causes the wires to cross over each other inside the plugs, and it
seems a bit ugly. But this is the ONLY way it will work. Look at the
pictures at the bottom of this page, and wire the cable STRICTLY
in accordance with the colour coding:

How to Wire a Network
http://www.linksys.com/faqs/default.asp?fqid=20


The only fix is to chop the ends and re-terminate them correctly.