ARRRRRRRRRRGGGHHHH!!!!!!!!!!!

[cautery]

I'm about ready to shoot this machine!

Been trying for 4 hours to get my 4th system back on my LAN to get it cracking again....

No matter what I try, I simply cannot get it to see the other three, or any of the other three to see it...

Fresh NT 4.0 install... same workgroup, unique IP, in the same subnet, setup (as far as my weary eyes can tell) exactly like the other three NT4.0 systems... (except this machine has no modem, hence no RAS)

It's bound to be a software prob, but I can't find it....

Just to be sure, I switched cables and cards out... link light on the hub and card shows a connect... but Network Neighborhood only reflects ITSELF alone...

Any ideas out there? Help! We're losing 400+ blocks a day....

On the brighter side.... I just climbed back into the top 100 on Mika's!

 

[NT4Mike]

What protocol are you using? What OS are you running on the other machines?

-Mike

 

[cautery]

Thanks for the response!

TCP/IP under WinNT 4.0 on all four machines....
Any other details you want, ask away.... I want to get this think crackin' ASAP!

 

[NT4Mike]

Can you ping the other machines?

-Mike

 

[Postman]

hmh, no ip-traffic is getting trough, you tried pinging the other machines?

 

[cautery]

Heh... now this is what's going to make you scratch your head....

NONE of the machines can ping ANY of the others using ping 198.162.1.x in the command prompt window. They time out....

BUT of course the first three machines all see each other just fine....

 

[NT4Mike]

Try recycling the switch or hub. If that doesn't do it, try mapping a drive using the IP......\\198.162.1.x\sharename

What NIC are your using?

-Mike

 

[cautery]

OK, tried pinging again...

I can ping self 127.0.0.1 and either of the other two machines in the original group of three on all three machines.

Going to switch the monitor over and do the "ping thing" with the new machine.....

 

[cautery]

Tried recycling the hub...
Tried direct mapping to the IP/share.... no go.
Using FA310TX NICs on all 4 machines.... good NICs, have used tons of them....

BRB...

 

[Lord Demios]

Hey Clay, sounds like tcp/ip is un-happy. Windows NT will see machines on a network even if TCP/IP is not working. You might have this one machine right, and the other three wrong. I would double check TCP/IP and then make sure each machine has the "I can share stuff on this machine and share my printers" Windows network browser has been known to not show machines that don't have that enabled. If the pings fail, I would say that your TCP/IP setting are not happy.

LD, are you running NT server or WKS?

 

[NT4Mike]

What are the IPs of all the machines?

-Mike

 

[cautery]

Jeez... Check this.... ping exercise on "loner" machine...

Ping 127.0.0.1 - "GO" cool, at least it sees itself....
Ping 198.162.1.3 - "NOGO" hmmm, can ping loopback, but not external IP for self....

Checking IP Properties (for the 9 zillionth time of course)....

I'm such a dumb ass.... I looked directly at (and typed it in) the IP address on this sys like 20 times at least....

Properties shows 192.162.1.3 !!!! HOW could I possibly type it in wrong that many times and not see it ONCE!

Oh well, thanks y'all for the help, and lettin' me vent....

More blocks! Yeah! Only one more idle sys to get cranked up... but I gotta go scrounge a power cord and a CD reader somewhere.... CD motor just quit on this sys last night.... (oldest component I owned... a very old 16x generic).

Later! and thanks again....

 

[NT4Mike]

Been there, done that Clay!!!!

Just wait till we get those 128bit IPv6 addresses...LOL

-Mike

 

[Lord Demios]

I love it when I can't get a machine on the net and it ends up being that I was trying the 198.162.?.?. Or when you do a simple ping test on some host (www.google.com) and you wonder why it keeps failing, then you realize that DNS isn't setup yet, and it can't resolve the IP.

Solution. DHCP servers, and DNS servers.!!!!

LD

 

[BoberFett]

Sorry to interrupt, but the reserved IP block is 192.168.x.x, those others you are using are potentially valid IP addresses.

 

[office boy]

so im not the only one that is always typing 198.162.... :Q
thats nice to know

 

[cautery]

BoberFett, yup, yer right.... Course, my LAN is totally isolated from "the world" so it doesn't matter.....

That IP typo started way back at the beginning of TWC assembly.... and has just hung around.

 

[Viztech]

Gee, I knew there was a reason I started using 10.0.0.x for internal networks....

viz

 

[amok]

Cautery's back! How have you been doing Clay? Been a while since I've seen you poke your head in around here .

 

[cautery]

Hey there Amok! Long time man... Doing much better... Working on some new projects, fixin' up the house (well, supervising the contractors, while THEY fix up the house... ), ang getting all my idle hardware upgraded and back to cracking...

Decide I want to see if I can help the Team "Smash the /." before my birthday on 25 Nov....

 

[Orange Kid]

Clay
Good to see you back. Do take it easy though.
As to the IP-------I seem to tpye 168.192.x.x----- some day I'll get it straight.

 

[amok]

I'm glad you're doing OK. You had us all worried there for a while . Glad to see you back around the boards as well.