Browsing, WINS, Routing-Not really sure
Steve T
Microsoft has been working on this for 2 weeks and I am no closer to a
solution.
Network Configuration
PDC-
NT Server 4 w/SP4
TCPIP. NetBeui, IPX/SPX, MAC Services
One NIC
172.16.1.22
Class B subnet
Has lmhosts file containing a 1b entry and an entry for my BDC
Also running WINS, DNS and DHCP
In the network properties of TCPIP under the WINS section I list the
PDC (WINS Server) for both Primary and secondary
BDC-
NT Server 4 w/SP4
TCPIP. NetBeui, IPX/SPX, MAC Services
One NIC
192.168.101.10
Class C subnet
Has lmhosts file containing a 1b entry and an entry for my PDC
2 Networks connected via T1
Here's the problem. From The PDCs Network Neighborhood (NN) I can see
all of the shares on the BDC. From the BDCs NN I can see all of the
shares on the PDC. Any workstation or server on my PDCs segment will
see the BDC in their NN but when you double click on it you get the
error "path not found".
When I run BROWMON on my PDC segment it shows my PDC as the Master
Browser (MB) for NetBT_El90x1. In the WINS Manager my 1Bh entry
points to the IP of my PDC.
On the BDC Segment when I run BROWMON it shows my BDC as the MB for
NetBT_E100B1.
But if I ping the BDC from by name from the workstation first, it can
then go into NN and see all of the shares on the BDC.
What is going on? Anyone?
Steve
Stoom...@arn.com
John R Buchan
*I hope someone out there can help solve this strange problem. So far
*Microsoft has been working on this for 2 weeks and I am no closer to a
*solution.
*
*Network Configuration
*
*PDC-
*NT Server 4 w/SP4
*TCPIP. NetBeui, IPX/SPX, MAC Services
*One NIC
*172.16.1.22
*Class B subnet
*Has lmhosts file containing a 1b entry and an entry for my BDC
*Also running WINS, DNS and DHCP
*In the network properties of TCPIP under the WINS section I list the
*PDC (WINS Server) for both Primary and secondary
*
*BDC-
*NT Server 4 w/SP4
*TCPIP. NetBeui, IPX/SPX, MAC Services
*One NIC
*192.168.101.10
*Class C subnet
*Has lmhosts file containing a 1b entry and an entry for my PDC
*
*2 Networks connected via T1
*
*Here's the problem. From The PDCs Network Neighborhood (NN) I can see
*all of the shares on the BDC. From the BDCs NN I can see all of the
*shares on the PDC. Any workstation or server on my PDCs segment will
*see the BDC in their NN but when you double click on it you get the
*error "path not found".
When you double click on a server in the browse list, your client will
attempt to establish a connection with that server. The first thing the
client muse do to establish the connection is to resolve the server's name
to an IP (browse lists do not provide name resolution). If the server is on
a remote subnet (from the client), then you must provide some form of name
resolution (WINS, lmhosts, DNS, hosts).
*
*When I run BROWMON on my PDC segment it shows my PDC as the Master
*Browser (MB) for NetBT_El90x1. In the WINS Manager my 1Bh entry
*points to the IP of my PDC.
*
*On the BDC Segment when I run BROWMON it shows my BDC as the MB for
*NetBT_E100B1.
*
*But if I ping the BDC from by name from the workstation first, it can
*then go into NN and see all of the shares on the BDC.
You keep refering to the client as a workstation. Do you mean the it is
running NT Wks or are you using 'workstation' as a generic term?
What type of name resolution is in place on the client?
If this is an NT Wks, is it configured to "Enable DNS for Windows
resolution"?
*
*What is going on? Anyone?
*
*Steve
*Stoom...@arn.com
John R Buchan Independent Consultant Orlando, Florida USA
MCSE -++- MVP ...................... j.bu...@worldnet.att.net
Steve T
I am providing Name Resolution for my clients. All of my clients use
DHCP. In the DHCP server I have defined the WINS server, along with
the DNS information. I do not have "Enable DNS for Windows
resolution" checked off.
Microsoft had asked me to verify that UDP ports 137, 138 and 139 are
open, and they are. They originally thought that UDP port 139 may
have been the culprit
I keep using client as a generic term. To clarify it, I am currently
dealing with NT4 Workstation with SP4
Steve
John R Buchan
PDC, you say "Has lmhosts file containing a 1b entry and an entry for my
BDC". The 1b entry is used to find a Domain Master Browser (only a DMB will
register this name). Since the PDC is always the DMB for it's domain, there
is no need for a 1b entry on the PDC's lmhosts file. Still, I doubt that a
1b entry in the PDC's lmhosts will do any hard, as long as the IP referred
to by that entry is the PDC's.
On your PDC and BDC, you might want to run 'nbtstat -n' and 'nbtstat -c' to
check your 1b entries. On both machines, the IP associated with the entry
should be the PDC's.
Your description seems to indicate that the client is unable to resolve the
server's name via the normal NetBIOS methods (cache, WINS, broadcast,
lmhosts), but is able to resolve it via either DNS or hosts. Try enabling
the "Enable DNS for Windows resolution" to see if it corrects the problem.
If it does, then you have a problem of some kind in your NetBIOS name
resolution system (most like in your WINS system).
BTW. Is there an entry for your BDC in your WINS database? Is the BDC
configured to use WINS?
I apologize, if I'm going over ground you've already covered, but I don't
have any way to know what you have and haven't already checked.
On Fri, 19 Mar 1999 21:24:56 GMT, stoom...@arn.com (Steve T) wrote:
*John
*
*I am providing Name Resolution for my clients. All of my clients use
*DHCP. In the DHCP server I have defined the WINS server, along with
*the DNS information. I do not have "Enable DNS for Windows
*resolution" checked off.
*
*Microsoft had asked me to verify that UDP ports 137, 138 and 139 are
*open, and they are. They originally thought that UDP port 139 may
*have been the culprit
*
*I keep using client as a generic term. To clarify it, I am currently
*dealing with NT4 Workstation with SP4
*
*Steve
*
*
*On Fri, 19 Mar 1999 03:26:44 GMT,
*j.bu...@remove-this.worldnet.att.net (John R Buchan) wrote:
*
*>On Thu, 18 Mar 1999 21:49:16 GMT, stoom...@arn.com (Steve T) wrote:
*>
*>*I hope someone out there can help solve this strange problem. So far
*>*Microsoft has been working on this for 2 weeks and I am no closer to a
*>*solution.
*>*
*>*Network Configuration
*>*
*>*PDC-
*>*NT Server 4 w/SP4
*>*TCPIP. NetBeui, IPX/SPX, MAC Services
*>*One NIC
*>*172.16.1.22
*>*Class B subnet
*>*Has lmhosts file containing a 1b entry and an entry for my BDC
*>*Also running WINS, DNS and DHCP
*>*In the network properties of TCPIP under the WINS section I list the
*>*PDC (WINS Server) for both Primary and secondary
*>*
*>*BDC-
*>*NT Server 4 w/SP4
*>*TCPIP. NetBeui, IPX/SPX, MAC Services
*>*One NIC
*>*192.168.101.10
*>*Class C subnet
*>*Has lmhosts file containing a 1b entry and an entry for my PDC
*>*
*>*2 Networks connected via T1
*>*
*>*Here's the problem. From The PDCs Network Neighborhood (NN) I can see
*>*all of the shares on the BDC. From the BDCs NN I can see all of the
*>*shares on the PDC. Any workstation or server on my PDCs segment will
*>*see the BDC in their NN but when you double click on it you get the
*>*error "path not found".
*>
*>When you double click on a server in the browse list, your client will
*>attempt to establish a connection with that server. The first thing the
*>client muse do to establish the connection is to resolve the server's
name
*>to an IP (browse lists do not provide name resolution). If the server is
on
*>a remote subnet (from the client), then you must provide some form of
name
*>resolution (WINS, lmhosts, DNS, hosts).
*>
*>*
*>*When I run BROWMON on my PDC segment it shows my PDC as the Master
*>*Browser (MB) for NetBT_El90x1. In the WINS Manager my 1Bh entry
*>*points to the IP of my PDC.
*>*
*>*On the BDC Segment when I run BROWMON it shows my BDC as the MB for
*>*NetBT_E100B1.
*>*
*>*But if I ping the BDC from by name from the workstation first, it can
*>*then go into NN and see all of the shares on the BDC.
*>
*>You keep refering to the client as a workstation. Do you mean the it is
*>running NT Wks or are you using 'workstation' as a generic term?
*>
*>What type of name resolution is in place on the client?
*>
*>If this is an NT Wks, is it configured to "Enable DNS for Windows
*>resolution"?
*>
*>*
*>*What is going on? Anyone?
*>*
*>*Steve
*>*Stoom...@arn.com
*>
*>John R Buchan Independent Consultant Orlando, Florida USA
*>MCSE -++- MVP ...................... j.bu...@worldnet.att.net
Steve T
me.
I did the nbtstat -n and -c on my PDC it shows the 1b entry when I do
both commands (-n and -c)
When I do the nbtstat -n on the BDC I do not see the 1b entry. I do
see it when I do the nbtstat -c
When I rebooted my BDC I did get an event id 3096 "The Windows Domain
Controller For This Domain Could Not Be Located"
On my PDC I turned on Enable DNS for WINS Resolution, but when I went
to Network Neighborhood I still could not get to the shares of my BDC
(I went and turned this option off).
My BDC is in my WINS database as 00h, 03h and 20h
Someone here seems convinced that it is a DNS problem not a WINS or
Browsing issue. I don't agree because from my NTWS I can ping the
BDC by name, once I do that then I can go to Network Neighborhood and
get to all of the shares.
On 19 Mar 1999 22:04:22 GMT, j.bu...@remove-this.worldnet.att.net
Steve T
I did a test today. Just in case there was a problem with my DHCP
installation, I removed my NTWS from using DHCP. I configured
everything manually. I did it once with the WINS server configured
and Once using the DNS For WINS Resolution. Everytime I went to NN
and clicked on my BDC, I could not see the shares. But, again, if I
ping my BDC by name and then go to NN I can see the shares.
John R Buchan
basically fishing around for various possibilities. From the information
you've provided so far, it should be working. Since it's not I've
apparently missed something. <g>
On Mon, 22 Mar 1999 14:52:10 GMT, stoom...@arn.com (Steve T) wrote:
*I did the nbtstat -n and -c on my PDC it shows the 1b entry when I do
*both commands (-n and -c)
*
*When I do the nbtstat -n on the BDC I do not see the 1b entry. I do
*see it when I do the nbtstat -c
This is normal. I assume that the IP associated with the 1B was your PDC's
IP in all cases.
Does the lmhosts file of the BDC also have a #DOM entry pointing to the
PDC? This really shouldn't be necessary, if the BDC is configured to use
the same WINS server as the PDC, but...
*
*When I rebooted my BDC I did get an event id 3096 "The Windows Domain
*Controller For This Domain Could Not Be Located"
*
*On my PDC I turned on Enable DNS for WINS Resolution, but when I went
*to Network Neighborhood I still could not get to the shares of my BDC
*(I went and turned this option off).
*
I assume you mean that you "Enable DNS for Windows resolution" in the NT
client. Exactly how did you try to connect and exactly what happened?
*My BDC is in my WINS database as 00h, 03h and 20h
Assuming that these are dynamic entries (as opposed to static entries that
you manually created), this would seem to indicate that the BDC is
registering with your WINS server. So the BDC should be able to find the
PDC via WINS. The NT client should also be able to find the BDC via WINS.
Strange.
Are the Primary and Secondary WINS settings of all of your machines,
including the WINS server itself, set to the IP of your WINS server?
*
*Someone here seems convinced that it is a DNS problem not a WINS or
*Browsing issue. I don't agree because from my NTWS I can ping the
*BDC by name, once I do that then I can go to Network Neighborhood and
*get to all of the shares.
Since this is an NT client, try connecting from the Run dialog,
substituting the BDC's IP for it's name (e.g. \\192.168.101.10). If that
works properly, wait a while (or reboot) then try connecting from the Run
dialog again, but using the BDC's name this time.
Are there any other machines on the remote subnet that you can attempt
connecting to from the NT client? If so, what happens?
Can machines on the remote subnet connect to the PDC and/or the NT client?
Actually, at this point, I'm more concerned about your BDC being unable to
contact the domain controller.
Exactly when are you getting this error? Is it, when you attempt to log in
or is it recorded in the Event Log during boot?
Is the error consistant or occasional?
What happens, if you try running UserManager for Domains on the BDC?
Is it able to find the PDC?
Does the list of users look correct?
Run Server Manager on the BDC. Does it find your PDC?
If you don't already have a the following entry in the BDC's lmhosts, try
adding it (you will need to run 'nbtstat -R' or reboot after adding it).
Substitute in your PDC and domain names.
172.16.1.22 MyPDC #PRE #DOM:MyDomain
Do you still get the error message?
If so:
Can you ping the PDC from the BDC?
What is the reply time?
From the BDC, try 'nbtstat -A 172.16.1.22'. Do you get a list of names
registered by the PDC?
Have you rebuilt one of the domain controllers recently?
Have you modified any of the default network settings. Specifically, have
you made any alterations via the registry?
I may have already asked this, but did you reapply SP4 on each machine,
after implementing TCP/IP?
*
<snip>
*>On Fri, 19 Mar 1999 21:24:56 GMT, stoom...@arn.com (Steve T) wrote:
*>*I am providing Name Resolution for my clients. All of my clients use
*>*DHCP. In the DHCP server I have defined the WINS server, along with
*>*the DNS information. I do not have "Enable DNS for Windows
*>*resolution" checked off.
*>*
*>*Microsoft had asked me to verify that UDP ports 137, 138 and 139 are
*>*open, and they are. They originally thought that UDP port 139 may
*>*have been the culprit
*>*
*>*I keep using client as a generic term. To clarify it, I am currently
*>*dealing with NT4 Workstation with SP4
*>*
*>*Steve
*>*
*>*
*>*On Fri, 19 Mar 1999 03:26:44 GMT,
*>*j.bu...@remove-this.worldnet.att.net (John R Buchan) wrote:
*>*
*>*>On Thu, 18 Mar 1999 21:49:16 GMT, stoom...@arn.com (Steve T) wrote:
*>*>
*>*>*I hope someone out there can help solve this strange problem. So far
*>*>*Microsoft has been working on this for 2 weeks and I am no closer to a
*>*>*solution.
*>*>*
*>*>*Network Configuration
*>*>*
*>*>*PDC-
*>*>*NT Server 4 w/SP4
*>*>*TCPIP. NetBeui, IPX/SPX, MAC Services
*>*>*One NIC
*>*>*172.16.1.22
*>*>*Class B subnet
*>*>*Has lmhosts file containing a 1b entry and an entry for my BDC
*>*>*Also running WINS, DNS and DHCP
*>*>*In the network properties of TCPIP under the WINS section I list the
*>*>*PDC (WINS Server) for both Primary and secondary
*>*>*
*>*>*BDC-
*>*>*NT Server 4 w/SP4
*>*>*TCPIP. NetBeui, IPX/SPX, MAC Services
*>*>*One NIC
*>*>*192.168.101.10
*>*>*Class C subnet
*>*>*Has lmhosts file containing a 1b entry and an entry for my PDC
*>*>*
*>*>*2 Networks connected via T1
*>*>*
*>*>*Here's the problem. From The PDCs Network Neighborhood (NN) I can see
*>*>*all of the shares on the BDC. From the BDCs NN I can see all of the
*>*>*shares on the PDC. Any workstation or server on my PDCs segment will
*>*>*see the BDC in their NN but when you double click on it you get the
*>*>*error "path not found".
<snip>
*>*>*
*>*>*When I run BROWMON on my PDC segment it shows my PDC as the Master
*>*>*Browser (MB) for NetBT_El90x1. In the WINS Manager my 1Bh entry
*>*>*points to the IP of my PDC.
*>*>*
*>*>*On the BDC Segment when I run BROWMON it shows my BDC as the MB for
*>*>*NetBT_E100B1.
*>*>*
*>*>*But if I ping the BDC from by name from the workstation first, it can
*>*>*then go into NN and see all of the shares on the BDC.
<Snip>
Steve T
with this issue.
I myself have been fishing for quite sometime. In response to your
questions.
1. This is normal. I assume that the IP associated with the 1B was
your PDC's IP in all cases.
* Yes it was
2. Does the lmhosts file of the BDC also have a #DOM entry pointing to
the PDC? This really shouldn't be necessary, if the BDC is configured
to use the same WINS server as the PDC, but..
* yes it does
3. I assume you mean that you "Enable DNS for Windows resolution" in
the NT client. Exactly how did you try to connect and exactly what
happened?
* Yes, that is what I mean. At the PDC I turned the option on and
rebooted the PDC. I then rebooted my NTWS. I then went to Network
Neighborhood (NN) and saw that my BDC was listed. When I double
clicked on it I was told that the Path Was Not Found. And remember,
if I ping by name first, then I can double click on the BDC in NN and
see the shares
4. Assuming that these are dynamic entries (as opposed to static
entries that you manually created), this would seem to indicate that
the BDC is registering with your WINS server. So the BDC should be
able to find the PDC via WINS. The NT client should also be able to
find the BDC via WINS.
* The entries are dynamic. The BDC can see the PDC with no problem
(and vice versa). It's the clients that aren't getting to the BDC.
5. Are the Primary and Secondary WINS settings of all of your
machines, including the WINS server itself, set to the IP of your WINS
server?
* Yes. They are getting the WINS info from the DHCP Server. (In the
DHCP Server I have a 044 entry pointing to my WINS server, which is
also my PDC. And I have a 046 entry that is set to node type 0x8)
6. Since this is an NT client, try connecting from the Run dialog,
substituting the BDC's IP for it's name (e.g. \\192.168.101.10). If
that works properly, wait a while (or reboot) then try connecting from
the Run dialog again, but using the BDC's name this time.
* I tried this and it did not work. I went to Start -> Run and typed
in MyBDC and I got the message "can't find the file....." I also
typed the IP address and got the same response. The Run option is
looking for an executable
7. Can machines on the remote subnet connect to the PDC and/or the NT
client?
* Don't have an answer yet. The clients are MACs (for now). I'm
trying to get an NTWS machine over there that I can use for testing.
8. Actually, at this point, I'm more concerned about your BDC being
unable to
contact the domain controller.
Exactly when are you getting this error? Is it, when you attempt to
log in
or is it recorded in the Event Log during boot?
Is the error consistant or occasional?
What happens, if you try running UserManager for Domains on the BDC?
Is it able to find the PDC?
Does the list of users look correct?
Run Server Manager on the BDC. Does it find your PDC?
* I got this message on boot up. After it is up the BDC can see the
PDC and browse all of its shares. From User Mgr on the BDC I can see
all of my user accounts and they are correct
9. If you don't already have a the following entry in the BDC's
lmhosts, try adding it (you will need to run 'nbtstat -R' or reboot
after adding it). Substitute in your PDC and domain names.
172.16.1.22 MyPDC #PRE #DOM:MyDomain
Do you still get the error message?
If so:
Can you ping the PDC from the BDC?
What is the reply time?
From the BDC, try 'nbtstat -A 172.16.1.22'. Do you get a list of
names registered by the PDC?
* Already has the #PRE and #DOM entry.
When I ping the PDC I get time of <10ms and TTL=126
When I do a nbtstat -A 172.16.1.22 I do get a list of names registered
with the PDC
10. Have you rebuilt one of the domain controllers recently?
* No
11. Have you modified any of the default network settings.
Specifically, have you made any alterations via the registry?
* On the BDC I had but have since put them back to their default. I
had changed the
HKLM\system\CurrentControlSet\Services\Browser\Parameters
IsDomainMaster is currently set to FALSE
MaintainServerList is currently set to AUTO
12. I may have already asked this, but did you reapply SP4 on each
machine, after implementing TCP/IP?
* I did, but I wonder if I should try reapplying it
On 23 Mar 1999 06:00:23 GMT, j.bu...@remove-this.worldnet.att.net
John R Buchan
everything we've discussed so far. You haven't provided your machine names
and domain name, so I'll make them up. Please read over this and verify it.
PDC (MyPDC):
NT Server 4.0 SP4
TCP/IP, NetBEUI, IPX/SPX, Mac Svcs
Server services: WINS, DNS, DHCP
172.16.1.22 (mask 255.255.0.0)
Default Gateway: 172.16.0.0 IP of your T1 device
WINS: Primary = 172.16.1.22, Secondary = 172.16.1.22
lmhosts:
192.168.101.10 MyBDC #PRE #DOM:MyDomain
BDC (MyBDC):
NT Server 4.0 SP4
TCP/IP, NetBEUI, IPX/SPX, Mac Svcs
Server services: WINS, DNS, DHCP
192.168.101.10 (mask 255.255.255.0)
Default Gateway: 192.168.101.0 IP of your T1 device
WINS: Primary = 172.16.1.22, Secondary = 172.16.1.22
lmhosts:
172.16.1.22 MyPDC #PRE #DOM:MyDomain
182.16.1.22 "MyDomain \0x1b" #PRE
Client1:
Nt Wks 4.0 SP4
Member of MyDomain
TCP/IP
DHCP Client:
172.16.1.150 (mask 255.255.0.0) <this is a ficticious IP>
Default Gateway: 172.16.0.0 IP of T1 device
WINS: Primary = 172.16.1.22, Secondary = 172.16.1.22
DNS: 172.16.1.22
Node type: Hybrid
1) These subnets are linked via T1
2) UDP 137, 138, 139 are not being blocked by any router/firewall
3) BDC does register dynamic entries (00, 03, 20) in WINS.
4) Browmon indicates that PDC is the Master Browser on its subnet.
5) Browmon indicates that BDC is the Master Browser on its subnet.
6) 'nbtstat /c' on the BDC shows the correct 1B entry in the cache:
MyDomain <1B> UNIQUE 172.16.1.22 -1
7) Client1 can successfully ping MyBDC.
Problems:
1) During boot, the BDC registers an error in the event log: Event ID 3096
"The windows domain controller for this domain could not be located"
2) Client1 is unable to conect to MyBDC by selecting it from the browse
list. The error is "path not found".
If Client1 pings MyBDC before attempting to connect, it is able to
successfully connect by selecting MyBDC from the browse list.
Notes from prior messages:
>3. I assume you mean that you "Enable DNS for Windows resolution" in
>the NT client. Exactly how did you try to connect and exactly what
>happened?
>
>* Yes, that is what I mean. At the PDC I turned the option on and
>rebooted the PDC. I then rebooted my NTWS. I then went to Network
>Neighborhood (NN) and saw that my BDC was listed. When I double
>clicked on it I was told that the Path Was Not Found. And remember,
>if I ping by name first, then I can double click on the BDC in NN and
>see the shares
I'm not certain we're on the same wave length here. I meant for you to
enable "Enable DNS for Windows resolution" on Client1, not on the PDC. Or
is that what you did? The idea is to allow Client1 to fall through to DNS
resolution on the off chance that NetBIOS name resolution isn't working
properly.
>6. Since this is an NT client, try connecting from the Run dialog,
>substituting the BDC's IP for it's name (e.g. \\192.168.101.10). If
>that works properly, wait a while (or reboot) then try connecting from
>the Run dialog again, but using the BDC's name this time.
>
>* I tried this and it did not work. I went to Start -> Run and typed
>in MyBDC and I got the message "can't find the file....." I also
>typed the IP address and got the same response. The Run option is
>looking for an executable
If you typed the name exactly as you indicated in here (i.e.
192.168.101.10, instead of \\192.168.101.10), you would not be able to
connect. The double backslash must precede a UNC. If you did leave off the
\\, please try again to connect from Client1's Run dialog to
\\192.168.101.10 and to \\MyBDC.
Have you tried using Network Monitor to watch what Client1 is doing as it
attempts to connect to MyBDC? The best bet would be, in you have the full
version of Network Monitor (or any other packet monitor), so you can watch
all packets sent by Client1. However, it would be informational just to
discover, if Client1 is correctly contacting the WINS server (MyPDC) in an
attempt to resolve MyBDC to an IP and, if so, does the reply from WINS
contain the proper information?
One other thing you might try to track dwn the problem is to implement an
lmhosts file on Client1 with the following entry:
192.168.101.10 MyBDC #PRE
Use 'nbtstat /R' to reload the NetBIOS cache, then try connecting to MyBDC.
On Tue, 23 Mar 1999 14:43:03 GMT, stoom...@arn.com (Steve T) wrote:
<snip>
Steve T
I've been trying to email you, but my messages keep getting bounced
back. The problem is solved.
Email me with your address and I'll give you the scoop as to what was
going on.
Steve
On 25 Mar 1999 03:48:32 GMT, j.bu...@remove-this.worldnet.att.net
(John R Buchan) wrote:
>This thread is getting a bit convoluted, so I'm going to try to summarize
>everything we've discussed so far. You haven't provided your machine names
>and domain name, so I'll make them up. Please read over this and verify it.
>
>PDC (MyPDC):
> NT Server 4.0 SP4
> TCP/IP, NetBEUI, IPX/SPX, Mac Svcs
> Server services: WINS, DNS, DHCP
> 172.16.1.22 (mask 255.255.0.0)
> Default Gateway: 172.16.0.0 IP of your T1 device
> WINS: Primary = 172.16.1.22, Secondary = 172.16.1.22
> lmhosts:
> 192.168.101.10 MyBDC #PRE #DOM:MyDomain
>
>BDC (MyBDC):
> NT Server 4.0 SP4
> TCP/IP, NetBEUI, IPX/SPX, Mac Svcs
> Server services: WINS, DNS, DHCP
> 192.168.101.10 (mask 255.255.255.0)
> Default Gateway: 192.168.101.0 IP of your T1 device
> WINS: Primary = 172.16.1.22, Secondary = 172.16.1.22
> lmhosts:
> 172.16.1.22 MyPDC #PRE #DOM:MyDomain
>>3. I assume you mean that you "Enable DNS for Windows resolution" in
>>the NT client. Exactly how did you try to connect and exactly what
>>happened?
>>
>>* Yes, that is what I mean. At the PDC I turned the option on and
>>rebooted the PDC. I then rebooted my NTWS. I then went to Network
>>Neighborhood (NN) and saw that my BDC was listed. When I double
>>clicked on it I was told that the Path Was Not Found. And remember,
>>if I ping by name first, then I can double click on the BDC in NN and
>>see the shares
>
>I'm not certain we're on the same wave length here. I meant for you to
>enable "Enable DNS for Windows resolution" on Client1, not on the PDC. Or
>is that what you did? The idea is to allow Client1 to fall through to DNS
>resolution on the off chance that NetBIOS name resolution isn't working
>properly.
>
>>6. Since this is an NT client, try connecting from the Run dialog,
>>substituting the BDC's IP for it's name (e.g. \\192.168.101.10). If
>>that works properly, wait a while (or reboot) then try connecting from
>>the Run dialog again, but using the BDC's name this time.
>>
>>* I tried this and it did not work. I went to Start -> Run and typed
>>in MyBDC and I got the message "can't find the file....." I also
>>typed the IP address and got the same response. The Run option is
>>looking for an executable
>
>If you typed the name exactly as you indicated in here (i.e.
>192.168.101.10, instead of \\192.168.101.10), you would not be able to
>connect. The double backslash must precede a UNC. If you did leave off the
>\\, please try again to connect from Client1's Run dialog to
>\\192.168.101.10 and to \\MyBDC.
>
>
>Have you tried using Network Monitor to watch what Client1 is doing as it
>attempts to connect to MyBDC? The best bet would be, in you have the full
>version of Network Monitor (or any other packet monitor), so you can watch
>all packets sent by Client1. However, it would be informational just to
>discover, if Client1 is correctly contacting the WINS server (MyPDC) in an
>attempt to resolve MyBDC to an IP and, if so, does the reply from WINS
>contain the proper information?
>
>One other thing you might try to track dwn the problem is to implement an
>lmhosts file on Client1 with the following entry:
>
> 192.168.101.10 MyBDC #PRE
>
>Use 'nbtstat /R' to reload the NetBIOS cache, then try connecting to MyBDC.
>
>On Tue, 23 Mar 1999 14:43:03 GMT, stoom...@arn.com (Steve T) wrote:
><snip>