4

I'm working on upgrading the network at my office... Right now we have two subnets, one for our workstations (on a wireless network) and one for our servers (mapped to static IP addresses).

We're having trouble with folder sharing, etc. due to Netbios barfing on our dual-subnet layout. Is there a way around this? Should I just hook up our workstations to a wirless access point, without the subnet?

Something else to note, I will be setting up a domain controller shortly and putting all of the workstations and servers on the domain. Will this take the place of Netbios (not sure if I know what I'm talking about) in my network?

Any help is appreciated... Thanks for your feedback!

Improve this question

2 Answers 2

Reset to default
5

I believe this behavior is by design as NetBIOS works with broadcast packets. Setting up a WINS server when you set up the domain controller (and enabling the Computer Browser Service if it is Win2k8) and pointing clients to that WINS server should resolve this (assuming you have routing set up correctly).

WINS doesn't replace NetBIOS, but it provides a central point for NetBIOS name resolution that can work across subnets.

Improve this answer
5
  • 1
    Yep WINS is what you want.
    – Tatas
    Jul 29, 2009 at 2:05
  • 1
    +1 for WINS in this scenario. Like it or not, we still find the need for WINS out there in real life.
    – Evan Anderson
    Jul 29, 2009 at 2:13
  • @Evan, upvote for pointing out the ugly truth of WINS (see serverfault.com/questions/14785/… for a completely bizarre explanation by someone else about how it is "no longer needed". I countered that it was and got downvotes, go figure)
    – Avery Payne
    Jul 29, 2009 at 4:56
  • Thanks for the great feedback everyone. Very informative. Now, will a WINS server allow me to do file and printer sharing across these subnets?
    – Matt McCormick
    Jul 29, 2009 at 12:44
  • @mb...yes, providing routing and everything else is working, WINS will let you access servers for file and printer sharing across the subnets.
    – Adam Brand
    Jul 29, 2009 at 14:42
0

Another option; you mention AD is coming. You could run AD-integrated MS-DNS and use DNS for the name resolution. Make sure all workstations use the same DNS suffix for short names to work, otherwise have to use FQDN e.g. machine.company.com. DNS may be directionally better and easier to understand than "old" WINS.

I am assuming that routing is working.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .