TCP not happenin' but NetBeui workin' fine.

[Faust]

this is on my "server".

long story short, it's been running it's normal 1-week-between-reboots schedule, but now i get no WAN or LAN TCP/IP traffic. NetBeui (what NetBIOS is bound to) works just fine.

have been running (if memory serves) a Netgear 310(?) series NIC (it's an Intel chipset) which is pretty ample.

my first thought was "OK, the stack is hosed", and i restored the whole (win2k AS) from a core drive image (that i know is clean) and again, NetBeui works fine (can browse other systems on the tiny home LAN), but TCP traffic ain't happenin'. local and WAN pings time out.

my personal/fun system works great. no probs with anything, and it's IP is in the middle of my small IP block.

the systems have public/static IPs, BTW.

my two thoughts are..... 1) someting is wrong with the NIC, and 2) there is something on one of my data drives that is mucking things up.... as in a malicious trojan or virus.




any ideas? thanks for the help, guys.

[YeOldeStonecat]

Double check your bindings under advanced settings?

I'm sure the NIC is fine, as if NetBEUI is running, your NIC is runnng.

History of the server? Any old "hosts" or "lmhosts" files sitting around?

WINS running correctly? DNS also running correctly?

Event Viewer showing issues?

Another computer on the network that you can ping by IP and resolve?

[Faust]

thanks for the help so far, YoSC.

yep, i checked my bindings. no lmhosts listed exept the one on the boot drive. ping requests time out (to server from a working machine on the LAN). my ISPs DNS is working fine for all other comps.

the whole perplexing thing to me is that fact that i reinstalled the whole O/S and core settings/apps/software to the c: drive from a known-to-be-good drive image that i have used many times before. this is why i think it may be something hokey on one of the data drives.

i think i am going to dump everything onto the jumbo IDE storage drive in the server, diable the IDE controller, low-level format all the SCSI drives, then re-mount the drive image and see what happens.


this is pretty wierd.

[Ken]

Your work station can see it, but you can't ping it...?
You have doubled checked TCP properties...
(It is still early, need more coffee... ;) )

[Faust]

yeah, the workstation can see it through NetBeui, won't respond to anything TCP/IP.

i just finished moving data and low-level formatting. going to partition and remount the drive image and such tomorrow night. i am done for the "evening".


thanks for droppin' by, Ken :) . don't see you around as much anymore.

[YeOldeStonecat]

Event Viewer...hit the event viewer.

May wanna just yank all networking components, reboot twice, then add them again from scratch.

[JackMDS]

This is a common story, usually some thing set off, and it impossible to find in the many settings involved TCP/IP.

Run a Registry cleaning program, and try to optimize the TCP/IP settings.

Such activities refresh the TCP/IP settings, and may inadvertently correct the problem.

[Faust]

sorry, guys. forgot about this one.


just as a matter of record, i did find the culprit. it was a software firewall i had included with the "core install" drive image (why i originally named it "core install" if it had anything except the OS/drivers and configs is beyond me).

the version of the firewall was too outdated (by a few weeks. couple months at most) and for some reason it disables all TCP traffic if not updated. all i had to do is uninstall it (*slaps forehead*).

oh, well. looks as if recommendations and common sense will finally get the better of me (to ditch software firewalls for good).

thanks for the help, fellas. i do appreciate it :) .