Can ping address # but not PC name

[J Browne]

Recently changed my home network: removed a Win95 OSR2 and added a new win98 (not SE but have the disk for upgrading) to a net of two older Win98 that have been connected via a hub and working great for the last 9 months.

The new Win98 (400 Celeron) and one of the older Win98 (300 K6) appear to function correctly through TCP/IP. The last PC (450 PII) can ping the address number correctly of the other two but it can not ping the PC's name. I plan to use the 450 PII for printer sharing, internet dial-up sharing, and a data storage server as it has 20Gb hard, zip, and CD-RW (I love this machine!)

The net is set up with address 192.168.0.10 for the 450 PII and .11 and .12 for the other two PCs. Mask is set at 255.255.255.0. Got Realtek 8029 in the older machines with drivers loaded with the latest drivers from 4/99 (will now go check to see if a newer version is available). The new Win98 has a newer LinkSys10/100 card. (Not sure of the model right now)

I have tried w/ and w/o NETBeui and every other combo I can think of and am at wits end.

TIA

[Duuude]

Sounds like a simple name resolution issue, though I'm not sure why the names wouldn't be getting resolved via broadcast. Since you have a small network, a LMHOSTS file would not be too difficult to manage and will, likely, solve the problem.

[prc01]

Add your host name and IP address to the HOSTS file. There is a HOSTS.SAM file on the system (a sample file). File Manager and Network Neighborhood typically use NetBIOS to resolve names and addresses. TCP/IP does not use NetBIOS. (-Something to do with Unix compatibility...) The end result is NetBIOS can resolve names using broadcasts, as long as it doesn't cross a router. But TCP/IP needs another type of name resolution. The HOSTS file is one method. LMHOSTS is used when NetBIOS crosses a router. There is a LMHOSTS.SAM file on the system also.

[This message has been edited by prc01 (edited 10-14-99).]

[Mango1]

Presuming all was well before you installed the new PC with Win98 and also that you never created a HOSTS and LMHOSTS file, then I'm guessing you are using DNS. Is one of the PCs on your network serving as a server? If so, check to see if DNS is being used and if so, you'll need to establish the new association between the computer name and IP Address there.

[J Browne]

Originally I was using DNS with the problem PC as the server. I have since disabled DNS and went the HOST/ LMHOST route with still no luck (other than bad).

I am now planning to completely remove the NIC and all setups on the problem computer and to start fresh figuring something is hashed somewhere between drivers, registry, etc. If this fails, I'm not sure what else is left.

Thanks for the support so far and will let you know what finally fixes it. This problem hasn't seen a lot of attention the last few weeks due to other committments.

[osane]

I think the problem is your ip address scheme. You are super netting a class C address to a call B address but still using a class C subnet mask. Try using 192.168.1.10, 192.168.1.11, and 192.168.1.12 with a subnet mask of 255.255.255.0. I believe this should work.

[This message has been edited by osane (edited 10-19-99).]

[ul2m8*Barbie]

It's a problem with your DNS server - double check the DNS address then try to ping your DNS server's IP address. Also check your WINS server config.
You may want to run 'ipconfig /all' from command prompt and make sure all the addresses are correct. If you're using DHCP make sure you have an IP address and the lease has not expired.
Good luck.

[ul2m8*Barbie]

I don't know if this may relate to your problem but I just ran into this the other day. Could not access network resource using a name but could using the IP. Ended up there was a win.com file in the root folder of the boot drive. Just deleted it and then everything worked fine. Never ran across anything like that before but thought I'd throw it out to you.

[J Browne]

Tried osane's tip of 192.168.1.10, etc. No cigar.
I have two copies of win.com, one in c:\windows as you would expect and MacAfee had one in a backup file. (luv yur handle bar-b)

I should have a little more time to work on it this weekend and will post with what I learn.