Another Windows funny

[The_Unbeliever]

Hi guys

Maybe somebody have seen something like this :

On a windows network, you can open an explorer window, and type in \\computername to get a list of shares for that specific computer.

When we do it, we get an "access denied" error message.

However, when we do browse by IP address, eg \\12.12.12.12 the shares for that particular PC is displayed and we can access the shares properly.

Even on the command line, if you use net use x: \\computername\shares, you get kicked out with an "access denied" error message, but using net use x: \\12.12.12.12\shares is successful.

Same PC, same IP address. Funny and weird. I've also tried in adding this particular PC to the hosts file, but no luck.

I've checked, there are no duplicate names on the network either.

Bleh. Interesting one... I'm going off to do some serious Googling...

Oh, this is the same with Windows Firewall disabled or enabled... so it isn't the firewall either...

 

[ant1b0dy]

I've had problems accessing shares on other PCs if the system dates are different. Might be worth checking out...

 

[Compl33t]

Do you have the NetBIOS protocol installed?

Feck. Do modern Windows PCs still use NetBIOS computer names on a local network? I'm not so sure now. We've had similiar problems.

Check if all the PCs have the same workgroup, unique names, etc.

Or are they part of a domain?

(damnit, I'm grabbing at straws today. Maybe I should just keep my mouth shut and save myself from embarassment. )

 

[bboy]

10 bucks says 1 is xp pro and 1 is home

 

[supersunbird]

You know what I do on all PC's on a network? I install the netBEUI protocol.

Its somewhere on the Windows XP CD in a folder like added features or something and then a Microsoft folder I think, its not a security hazard since its not routable over the net. You copy two files from the folder to 2 Windows subdirectories, one of which (c:/windows/inf) is normally hidden.

You can then install that protocol for that local area connection on both PC's and you will have success in having them chat to each other.

I have had no problems with this technique, but use my advice at your own risk (not that I think there is any risk).

 

[gkm]

For both PC's do the following:
- Open the LAN connection properties.
- Select TCP/IP
- Select Properties, then Advanced
- Select the WINS tab
- Select "Enable NetBios over TCP/IP", rather than the funny default involving DHCP.

I have seen doing that sometimes help.

 

[The_Unbeliever]

Thanks for your advice...

Will login to site and check it tonight and see if I can kick some windoze butt...

Did a Google, and a Microsoft KnowledgeBase search, and both pointed to PDC/Browse Master settings... gah.

Will post back what happened for all and sundry to see...

 

[werner]

I cant access a NAS device at work via name only IF the date and time on my work pc is a couple hours out...as mentioned above, try that first.

 

[The_Unbeliever]

Date and time was waaaay out... when first we checked the PC, it was a day ahead. Who or what changed it, nobody can tell. So we'll be installing a NTPTime utility.

At first it won't browse, but when I logged in later on, the browsing was working. So something got all pear-shaped here.

But still interesting that you could browse by IP addy and not by computername...

Anyway, thanks for your help, it is regarded.

 

[Nickste]

You checked that the pc doesn't have 2 network cards? Could be denying access on the network card that is used for \\computername, while the ip address is bound to a network card that allows access.

Prolly not tho