• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

XP can't resolve computer names?

Ok, here at work, we're all in a windows environment all joined to a domain. Each computer has it's computer name, and in theory, should be accessible by it. ie, COMPUTER-A (IP 10.1.1.2) can be accessed via \\COMPUTER-A or \\10.1.1.2

However, it seems as though, at random, I won't be able to use the name, only the IP. Basically I'll lose my networked drives as well.

Right now, I can't replicate this at all. In a given week, it might happen 2-7 times during the workday. If I do ipconfig /registerdns, all things come back to full functionality. Just flushing the DNS didn't seem to work.

Anyone have any ideas on where to start? I get an event id 3019 in event view, and have applied the patch, and tried setting the network card to the propper speed but the same results come up.

I appreciate the help,
Linh
 
Several source entries for 3019. What's your source on the events? Better yet, just go to eventid.net and enter it in yourself.

Assumably it is a dns issue. If this happens on more than one workstation then troubleshoot the DNS server, not the client machines.
 
blasted subscriptions! but i'll look into it.. the mcafee note scares me... it's what caused some problems w/ our ghost server.

it was the MRxSmb error... but I used the MS solution to make an attempt w/ no luck. I'm not sure if it's more client side or server side... the probably is so sparatic mainly because certain units tend to access things over the network. I'm also not too sure what to look for on the server end.

It's for roughly ~100 users. I'm fairly certain it affects everyone, but only a certain few people every say anything.
 
Originally posted by: petey117
correct me if i am wrong, but UNC names ( \\computer) work over wins or netbeui not dns?
UNC names within the same subnet are resolved by NetBIOS. Across a routed environment, if there's no DNS server, WINS provides the name resolution.

NetBEUI is an older Microsoft networking protocol and has nothing to do with it. NetBEUI and NetBIOS are confusingly similar names.
 
actually it you want to get technical, netbios runs on netbeui.

MS bastardized netbios to make netbeui, but if you look at the protocol decodes you still see netbios wrapped in a netbeui header.
 
Here's what an MS MVP said about NetBIOS/ NetBEUI.

"NetBIOS (Network Basic Input/Output System) is a Session-Level interface
originally developed by Sytek, Inc., for IBMs Broadband and Token-Ring
networks. Microsoft developed a compatible interface for MS-Net, then for
LAN Manager, then for the MS Networking used by WFW, WinNT and Win95. Once
a NetBIOS session is established between two hosts, then they can exchange
data such as NetBIOS requests or SMB messages.
.....
.....
NetBEUI (NetBIOS Extended User Interface) was first introduced by IBM in
1985. It is a protocol written to the NetBIOS interface for use on small,
departmental LANS of 10 to 200 workstations. Microsoft has supported
NetBEUI in all networking products since MS-Net in the mid 1980's. NBF
(NetBEUI Frame) is the NetBEUI implementation used in WindowsNT."

 
Originally posted by: spidey07
btw, welcome to the networking forum!
Thanks. I used to hang out in the FatWallet Computer Forum, but I'm thinking of going elsewhere for a change of scenery. 🙂

 
Originally posted by: RebateMonger
Originally posted by: spidey07
btw, welcome to the networking forum!
Thanks. I used to hang out in the FatWallet Computer Forum, but I'm thinking of going elsewhere for a change of scenery. 🙂

well there are a lot of networking pros here.
 
Back
Top