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

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' ? :D

[NooNoo]

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

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

[confus-ed]

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

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

[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

[Kineda]

Hey did you already run the nertwork setup wizard on both pc's? I ran into a lot of problems networking 98 and xp because of this, xp usually can see the 98 but 98 won't see xp, turns out xp uses updated network software, when you make the network setup disk in xp it will update the system files on the 98 box making it compatible with the xp network file system. Run the setup on both, dchp should work fine, and the network setup wizard also sets up the ics!!! hope this helps let me know!!!!

[Prince Abaddon]

Actually, I ran both wizards stright from the cd od XP and made the floppy during the setup. But no luck. I even tried installing every protocol, service, client things there were on both computers and still no luck.It dosen't seem that anyone else had this kind of problem.

[Kineda]

Well if you are still having issues, i think you should start smaller, start with the physical pieces, maybe the nic(s) are bad? Try new nic(s) which brand are you using, maybe new nic drivers? Make sure those are working properly then work on the rest. Let me know how the troubleshooting goes on the nics.....

[Prince Abaddon]

XP Machine (Computerzero) (192.168.0.1):
NIC
intergrated NIC by intel --> Home Network
Sohoware(somethign like that) --> internet (ICS on)

Protocols
TCP/IP
(Previously Installed)
Netbieu
IPX/SPX

98 Machine (Solaris) (192.168.0.2):
NIC
D-Link --> Home Network

Protocols
TCP/IP
(Previously Installed)
Netbieu
IPX/SPX


Workgroup:
MSHOME

Problem:
network disconnects after a certian amount of time has passed

Possible problem:
TCP/IP Protocol

Why?:
1) When IPX/SPX is used for file sharing, computers can comunacate using only that protocol after the network disconnects. When TCP/IP is used for all resources, the entire network fails after a certian amount of time.

2) When same setup is used on an XP --> XP network, it is flawless. As soon as any other operating system is used, the same exact problem returns (not tested with win 2000)

This is my proposal to this problem that has annoyed me for about 5 months with no existing answer anywhere.

[Prince Abaddon]

Originally posted by Kineda
Well if you are still having issues, i think you should start smaller, start with the physical pieces, maybe the nic(s) are bad? Try new nic(s) which brand are you using, maybe new nic drivers? Make sure those are working properly then work on the rest. Let me know how the troubleshooting goes on the nics.....

I have tested all hardware to be workign and operational. Took all m hardware to some friends' house for testign on his network. Everythign worked fine. All drivers are the latest right off of the manufacturer's sites. as for the cabling, I used one of thoes cable testers from my school and tried it on my friend's p2p network (his is a win 2000 --> win 2000).Everyting seemed to check out fine. :sad:

[Rellik]

now when you say the network disapears, does the internet still work or do the machines just vanish from the network neighborhood/my network places?

first ping the pc , when succesful then try typing the UNC name of the computer in an explorer window address bar:
\\{computer name}
\\computerzero
\\solaris

for me, some computers occasionally disappear from the Network neighborhood but I can type in their names manually. but ultimately I end up restarting the PC because sometimes I can see the pc but can't use the resources for whatever reason.

[Prince Abaddon]

Originally posted by Rellik
now when you say the network disapears, does the internet still work or do the machines just vanish from the network neighborhood/my network places?

first ping the pc , when succesful then try typing the UNC name of the computer in an explorer window address bar:
\\{computer name}
\\computerzero
\\solaris

for me, some computers occasionally disappear from the Network neighborhood but I can type in their names manually. but ultimately I end up restarting the PC because sometimes I can see the pc but can't use the resources for whatever reason.

What I mean by disapear is that nothing will work. Internet, file sharing. But the thing is, ping will work no matther what happens. I just can't ping outside of the network, meaning other internet machines.

As for using explorer to get on the network, it just says the machine is not found or a message along that line. I couldn't even find machines (using "find computer"). Only the ocmputers can see themselves.