what does this mean?

[Prince Abaddon]

If the network cabling is twisted-pair (RJ-45), you must use a hub or concentrator. Windows 98 does not support direct connections of RJ-45 cable between computers. This check isolates possible cabling or connector problems that may not be clearly visible.

You can't use a crossover cable in a 98 network?

[drewmaztech]

I think they are referring to a straight-through cable, not a crossover. I've used crossover connections before between two 98 systems. Just be sure you have each system configured properly.

[Prince Abaddon]

so has anyone evey tried connecting two diffrent OS, say XP or 98 together?

[NooNoo]

yes prince, no problem at all.

[Stalemate]

Make sure you're using the same protocol (TCP/IP) and that both machines are in the same "workgroup".

Avoid using blank asswords in WinXP and all should be fine.

[Prince Abaddon]

Originally posted by a d e p t

Avoid using blank asswords in WinXP and all should be fine.

lol

anyways, i think both my computers hate each other. Tell me what you think:

XP:
ip: 192.168.0.1
S.Mask: 255.255.255.0
Protocols: TCP/IP
No firewall

98:
ip: auto-assign - curently 192.168.0.78
S.Mask: 255.255.255.0
Protocols: TCP/IP

XP is ICS host - connects to internet properly, don't think we need to mess with thoes settings

98 connects through XP for about 5-30 mins, then everything is gone. there is absolutly no documents regarding this issue. Both systems have up to date updates.

on the xp machine though, when I look into the error message program in admin tools, I see somehtign about DHCP not ehough memory? and the time stamp usually indicates that it happened just before 98 disconnects.

[SpongeBob]

hmmm

Turn off DHCP... give 98 a static ip?

[Prince Abaddon]

Source: Ipnathlp
Event ID: 32003
The Network Address Translator (NAT) was unable to request an operation of the kernel-mode translation module. This may indicate misconfiguration, insufficient resources, or an internal error.

[NooNoo]

Prince set a static for the 98 machine. 192.168.0.2, set the gate way as 192.168.0.1

[confus-ed]

Originally posted by NooNoo
Prince set a static for the 98 machine. 192.168.0.2, set the gate way as 192.168.0.1

Translation: use static IPs at both ends .... or is that 'clarification' ?

[NooNoo]

Originally posted by confus-ed
Translation: use static IPs at both ends .... or is that 'clarification' ?

The XP box being an ics host is a static ip already.

[confus-ed]

Sorry I read the problem ... & only the last answer.... ... more 'stimulants' required....

Usually I get the communication between PC's going first then worry about ICS.... my bad

[Prince Abaddon]

You know what? I don't think there is a solution to this problem... no matter what I try, nothing works. It's either the sitiation gets worst or this is the best it'll get.

As for the static ip idea, that was how it was set up when I first built this network. It shouldn't be the wireing either, I've tried others. Currently, it is a Belkin category 5e crossover patch cable. If it even matters.

[gazzak]

Just my 2 pennires worth....

What happens when you try to ping x.x.x.x -t, is it stable, do you get inconsistencies. I had a customer where this sort of thing was happening, not exactly the same but similar. We ran a never ending ping, (-t), twisted the cabling, wobbled the end of the cable etc. and could get it to fail quite regularly.

Also, have you considered installing netbeui on both boxes? Nothing to lose from what I can see!

[Prince Abaddon]

ping x.x.x.x -t - well, I kinda get in the times as <10ms - 1ms... if you consider that incondistant.

You should also note, when I disconnect, I can still ping within the network, but not outside or any www.google.ca pings