DNS and SEGMENTED LAN: this ?? for advanced users/MCSE's

Ok here is today's problem. In my test enviroment I have:

Unit 1:
Domain Controller (windows 2000)
named: testlan
FQDN:segment.test.lan
with 3 network cards
card 1: 192.168.0.1
card 2: 192.168.15.1
card 3: 192.168.20.1
running DHCP with 3 scopes. 1 scope for each segement Works

Unit 2:
Fileserver (windows 2000)
1 network card
card 1: 192.168.0.10


Unit 3:
Laptop (Windows ME)
DHCP (192.168.15.xxx scope)


Unit 4:
Laptop (Windows 98SE)
DHCP (192.168.20.xxx scope)


I have a share on the fileserver called HOME. The fileserver is named Fileserver.

I tried to map a drive on unit 3 and 4 to \\fileserver\home : failed
I tried to map a drive on unit 3 and 4 to \\192.168.0.10\home : Success
I created a share on the DC in an OU called global. I shared the folder Home on fileserver.

I tried to map a drive on unit 3 and 4 to \\testlan\home : success

==============================================

Now for my problem. I need to know how to map a drive to:
\\fileserver\home

Every time I try it fails. Now here is the stipulation. No lmhost files on the laptops. I already know I can add an entry in the lmhost file on the laptop assiging 192.168.0.10 to filerserver. I need to get it to work in DNS. I need the laptops to connect directly to the fileserver with out using the IP.

I know that ideally I want to map to \\testlan\home allowing the DC to handle all the security. I can do this and it works fine. I have been told that I might need a DNS entry for the fileserver. If this is my solution, how do I add it. Do I make a new host ( tried this and was unable to map to \\fileserver\home )? Do I add an Alias? Or is my solution something completely different.

Now Part 2:

Do I have to do something special in 98SE and ME? I have the user on the dc set to map h:\\testlan\home but when he logs in the drive is not mapped for him. Do I have to install something to make this feature work?


Thanks

Tek

 

Tekguy - first a general question. Why the stipulation at the beginning that this question was only for specific types of folks? I would expect you to be happy with an answer from anyone who could.

Now to the question(s) you asked.

Are you using class C masking? If so, how is your routing set up?

I suspect maybe a routing issue since a user on the DC will tend to be dealing with only one of the 3 NICs unless you have done some fancy footwork and if he were using a NIC on one subnet, not surprising he couldn't map by name to a device on another subnet.

I assume (but gotta ask anyway) that your static IPs are outside the scope or excluded from assignment.

 

1. Win9x and NT systems won't be able to map NetBIOS acrossed subnets without WINS
2. Win9x and NT systems won't use DNS to resolve NetBIOS Names

Install WINS and put the WINS server in your DHCP scope and reboot your clients and test it again.

 

welll

Newt: basic users wont have the knowledge to answer this question... but all input is welcome.

all IP are using 255.255.255.0, this has to be this way.

statics are outside of dhcp scopes
scope 1 192.168.0.20 - 192.168.0.254
scope 2 192.168.15.50 - 192.168.15.254
scope 3 192.168.20.100 - 192.168.20.254

routing is working fine. I can map directly to the IP, what I want is to be able to map directly to netbios name.


Bursley:

I tried that, it did not work. I will give a second try to see if I missed something...


Tek

 

got it to work with wins

I added wins and added a static wins listing and was able to map to the \\fileserver\home

Now to see if I can map to a share from one client to another.


Tek

 

I'm assuming that you are successfully passing the FQDN and the DNS server (probably Unit 1) via DHCP to units 3 & 4? If so, are you letting DHCP dynamically update the DNS? Do have a forward zone for segment.test.lan and reverse zones for 192.168.0.x, 192.168.15.x, and 192.168.20.X? Once all the DNS stuff is setup, go to Unit 2 and attempt name resolution for each of the hosts.

C:> nslookup HOSTNAME

You should get a response for each host. If not, you need to make sure your DNS is working. Once DNS is working, you need to make sure the clients can resolve the netbios names. This shouldn't be a problem on Units 1 or 2, but on the ME machines, you're probably gonna have to check off the box that says something like enable DNS for WINS resolution....

Anyway, then you can check netbios resolutions like this...

C:\ nbtstat -a NETBIOS_NAME

The lowercase "a" is critical here. An uppercase "A" would need an IP address instead of a NETBIOS_NAME (cool if you know a computer's name and need to know it's IP address!).

Let me know how it goes!

 

Try to stay away from WINS if you can.....its days are numbered!! DNS is your friend!!

 

Tekguy - I doubt a "basic user" would touch this thread with a touching machine.

I know that you should have been using 255.255.255.0 but you would be amazed what some folks can do so I always ask. Subnetting w/o routers or trying to route a flat segment have both showed up on here (with the old bbs before the great crash).

You might want to take a look at Best Practice Methods for Windows 2000 Domain Controller Setup (Q216899) and make sure there isn't some simple "got ya" that you missed. I have torn my hair out several times and then wondered how I could have missed something so simple.

One that is fairly common (from that article) is

but there are others.

 

I wiped it all

I am starting from fresh, so far I have not been able to reproduce my previous success. I am trying to make this work, at this point, using a regular work groups and wins. This would more closely approxiamate the network as it is currently is. Future plans for our network are Domain and all the bells and whistles. That is why I am testing all types of solutions and making stipulations and trying different things or expanding on things.

I am the most knowledgable windows person on our staff. I am try to get prepared for future events also put a feather im my cap at raise time...


Tek

 

everything still works except

the zoned DHCP

Before if you were plugged into the switch attached to 192.168.10.1 you would get a DHCP address of 192.168.10.xxx
If you were plugged into the switch on 192.168.11.1 you would get and IP of 192.168.11.xxx etc etc etc

Now no matter where you plug in get 192.168.10.20 (scope starts at 20 and goes up)

I have not added rras, static routes, dns, wins, or anything else.

This is a fresh install with only DHCP configured.

I am trying to get this all reporducable every time I do it with different 192.168.xxx.xxx schema's




Tek