If it ain't useful for Norm...

Post #603 by static 7/1/01 8:00:24 AM Reply	If it ain't useful for Norm... ... then it will be useful to me. I'll go a-hunting. DNS could well be to blame since the DNS it points to has no knowledge of the local PCs. Wade "All around me are nothing but fakes Come with me on the biggest fake of all!"
Post #630 by pwhysall 7/1/01 6:37:47 PM Reply	Name Resolution In a native W2K network DNS is the ONLY method of name resolution; NetBIOS is there strictly for backwards compatibility with NT4 and 9x. In a mixed network, you're likely to be using WINS and DNS together. So check out the WINS server - occasionally WINS records can get messed up, and need tombstoning off the server, especially if a hostname has changed IP and somehow neglected to tell the WINS server about it. The other thing to check on a W2K DNS server is that it is configured to allow dynamic updates. If you're paranoid, turn on secure updates - that will only allow authenticated workstations to update the DNS server. -- Peter Shill For Hire
Post #636 by static 7/2/01 1:47:15 AM Reply	Eh... I dunno about Norm, but my network has precisely one (1) W2k machine. The server is RedHat 6.2. The other workstation is RH 7.1 the laptop is WinMe, and the other two PCs are both Windows 95. It's looking like something not quite square in my Win2k networking. I'll go rummaging and try a few things. (And DNS update is already turned off.) Wade. "All around me are nothing but fakes Come with me on the biggest fake of all!"
Post #638 by pwhysall 7/2/01 3:20:08 AM Reply	You're going to be wanting... ...to get your NetBIOS naming working. Those Win95 boxen mean that that's the way name resolution is going to work. Things to check : all boxes have NetBIOS bound to the same protocol (I suspect that as you've got a Linux box in the mix that this will be TCP/IP) and they're all in the same workgroup/domain. -- Peter Shill For Hire

Welcome to IWETHEY!