Problem accessing network computer by name
 

Hi,
I am having very weird issues accessing some of the computers in our workgroup. Some of the computers can’t see other computers in the workgroup. The strange part is that they can ping by IP and by Name. Using run \\ComputerName wont find them but run \\ComputerIP will work fine.

The computers that can’t be reached don’t have any problem from there end and can be reached by most of the other computers.

We recently “upgraded” the DNS/DHCP/WINS server from Linux to Windows server2003.

Any Ideas?

Re: Problem accessing network computer by name
 

i get this problam on my home network sometimes (no DNS or wins, all machine are xp home with workgroups) i dont know why it happens.

Re: Problem accessing network computer by name
 

hey daywraith,

since you have server2003, have you considered running a domain rather than a workgroup?

I feel certain this would solve your problems. If you need help setting it up, let us know and myself or someone else on here will walk you through it step by step.

Re: Problem accessing network computer by name
 

Maybe he has the dreaded xp home...

Re: Problem accessing network computer by name
 

Hi, I had the same exact problem myself earlier today...Three machines on a workgroup that could ping eachother, but could not see eachother by name...after an hour of going through the network setup wizard several times on each computer, I tried something different...
I went to the properties page for the network connection and installed the following protocol:
"NWLink IPX/SPX/NetBIOS Compatible Transport Protocol"
After I installed that, everything immediately started working correctly...
(All three machines were XP Home...)
Hope this helps!
-Eric

Re: Problem accessing network computer by name
 

Thanks for the replies,

To: Duki
I would like to try setting up a domain (for the experience if nothing else) but I would have a very hard uphill battle to get it approved. The company I work for is a research institution with a large number of highly skilled and fiercely independent tec savvy employees. About 50%+ have masters/doctorates in technology related fields. Previously there was no network admin, people just got round the cooler and came up with a solution. There are a lot of weird user requirements, to be honest I don't know what a lot of the devices plugged into my network do, GPS devices, acoustic/electromagnetic scanners, custom built electronics etc.

While I haven’t had a lot to do with domains/active directory I think they generally work best with in homogenous environments don’t they?

To ft3ssqeek:
Thanks for the tip I will look into it. Could you ping by name? This is the part that is kind of confuses me. I think it will give me the clue to fixing the problem I just don't know enough about how the windows master browser, WINS, DNS and NetBIOS work.

P.S The computers are XP Pro machines.

Re: Problem accessing network computer by name
 

To be honest, I did not attempt to ping by name, but I did do an nslookup on the ip addresses and it returned the correct name, so I'm assuming that had I tried to ping by name I would have been succesful...(shrug)

Re: Problem accessing network computer by name
 

IPX/SPX has nothing to do with this :)
anyhow, if you upgrade the network to a domain, this problem will be easily solved. another way, if you have static IP addresses, is to write a hosts file, and spread it among the workstations. that way no dhcp, dns or wins is needed. but it is quite a strain to manage such a system if you make frequent changes.

Re: Problem accessing network computer by name
 

I will start looking into upgrading the network to a domain. I don't think I will be able to get enough support to push it through but it will be interesting. Does anyone have any good guides to upgrading to a domain?

I have been examining DNS records and there is something weird going on. The reverse lookup seems to be full populated, I did notice that there was a double entry, two computers had 192.168.2.85 how could this occur?

The forward lookup is nearly empty. The static entry's I configured are there and maybe 10 other machines. Not sure why 10 DHCP machines are there while the other 100 or so aren't. The DNS is configured to lookup the WINS server if it can't find an entry.

The WINS server contains entries for both the computers in the DNS and the missing DHCP machines.

Anymore help would be greatly appreciated.

Re: Problem accessing network computer by name
 

well, promoting to domain is very simple, just run dcpromo and follow the wizard. but first, remove the dhcp, dns and wins services, dcpromo will set those up for you during the domain setup, and fit them to the domain