Networking HELL...

[GrimReefer]

I have a Netgear hub and a NIC in each comp. I can ping my client machine from my host but I cant ping the host from the client. What could the problem be?

edit: ICS also wont work properly and the comps cant see each other in network neighborhood. The only way I can access the other comp remotely is if I go into the adress bar in network neighborhood and type in the route to the comp for example \\slug or \\thunder.

 

[fergiboy]

Give more info: What are the ips of each comp. What workgroup are they in.

 

[warlord]

what protocols do yo have installed? what OS are you using? did you assign all IP's or are you using DHCP? is every comp in the same workgroup?

we're going to need this info before we can begin to help you.

 

[Ladi]

OS's wouldn't hurt either...nor would what network protocols are installed (TCP/IP, IPX, NetBEUI, etc.)...

~Ladi

 

[fergiboy]

help me mother

 

[GrimReefer]

98 SE

TCP/IP, NETBEUI, and IPX are on both. On my comp with the USB DSL modem, NDISWAN is also there. Both have WINS Resolution disabled. Both are in the same workgroup. Under the NIC's TCP/IP DNS is disabled but its enabled on the other comp. The only adapter on the other comp is the NIC. No dialup. I assigned the IPs for the NICs. 192.168.0.1 on this one and 192.168.0.45 on the other one. SyGate setup the IP on the client machine automatically.

edit: both are in workgroup "sessions"

 

[fergiboy]

so you can access the internet throught both machines?

 

[GrimReefer]

no thats my problem. I can't access the net through my other comp. It wont even ping my host machine.

 

[fergiboy]

what operating systems are you using

 

[GrimReefer]

Windows 98 Second Edition

 

[GrimReefer]

why do I get a 10043 error code in dos when I try to ping the host from the client?

 

[spidey07]

error like that running a simple PING is normally a screwed up IP stack. Sometimes can be difficult to fix.

Try uninstalling all network protocols, reboot, the uninstall network card, reboot, install NIC, reboot, install TCP/IP.

give it a shot. Like I said, it sounds like you have different versions of winsock files on the client machine.

cheers!