Re: Can only access servers via UNC if I use the FQDN
- From: "Lanwench [MVP - Exchange]" <lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 20 Mar 2008 09:41:53 -0400
gareththackeray@xxxxxxxxx wrote:
On 29 Feb, 16:15, "Lanwench [MVP - Exchange]"
<lanwe...@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
gareththacke...@xxxxxxxxx wrote:
Thanks for your reply. Here's the info you asked for:
This is from the problematic server:
Windows IP Configuration
Host Name . . . . . . . . . . . . : DHB03714-NLAR3
Primary Dns Suffix . . . . . . . : bpprod.dom
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : bpprod.dom
Ethernet adapter NIC 1-1 172.16.7.164:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP NC7170 Dual Gigabit Server
Adapter
Physical Address. . . . . . . . . : 00-11-0A-5F-6D-60
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 172.16.7.164
Subnet Mask . . . . . . . . . . . : 255.255.255.240
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 172.16.7.181
172.16.7.182
Ethernet adapter NIC 1-2 172.16.144.197:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP NC7170 Dual Gigabit Server
Adapter #2
Physical Address. . . . . . . . . : 00-11-0A-5F-6D-61
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 172.16.144.197
Subnet Mask . . . . . . . . . . . : 255.255.255.192
Default Gateway . . . . . . . . . :
Ethernet adapter NIC 0-2 172.16.66.133:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP NC7782 Gigabit Server
Adapter
Physical Address. . . . . . . . . : 00-17-A4-A7-EC-95
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 172.16.66.133
Subnet Mask . . . . . . . . . . . : 255.255.255.192
Default Gateway . . . . . . . . . : 172.16.66.129
Ethernet adapter NIC 0-1 10.3.22.9:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP NC7782 Gigabit Server
Adapter #2
Physical Address. . . . . . . . . : 00-17-A4-A7-EC-96
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.3.22.9
Subnet Mask . . . . . . . . . . . : 255.255.254.0
Default Gateway . . . . . . . . . :
This is from the DC:
Windows IP Configuration
Host Name . . . . . . . . . . . . : DHB0371C-NLAR3
Primary Dns Suffix . . . . . . . : bpprod.dom
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : bpprod.dom
Ethernet adapter NIC 0-2 172.16.7.181:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP NC7782 Gigabit Server
Adapter
Physical Address. . . . . . . . . : 00-17-A4-AA-D7-9F
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 172.16.7.181
Subnet Mask . . . . . . . . . . . : 255.255.255.240
Default Gateway . . . . . . . . . : 172.16.7.183
DNS Servers . . . . . . . . . . . : 172.16.7.181
172.16.7.182
Ethernet adapter NIC 0-1 10.3.22.17:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP NC7782 Gigabit Server
Adapter #2
Physical Address. . . . . . . . . : 00-17-A4-AA-D7-A0
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.3.22.17
Subnet Mask . . . . . . . . . . . : 255.255.254.0
Default Gateway . . . . . . . . . :
Ethernet adapter NIC 1-1 172.16.144.205:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP NC7170 Dual Gigabit Server
Adapter
Physical Address. . . . . . . . . : 00-11-0A-5F-6F-2C
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 172.16.144.205
Subnet Mask . . . . . . . . . . . : 255.255.255.192
Default Gateway . . . . . . . . . :
OK - my first question is, why the heck do you have so many NICs in
your servers? Please describe your network topology or post a link
to a diagram.
Multihomed DCs are usually considered very bad news - I am not a fan
of multihomed *servers* in general.
Hi, thanks for the reply. I completely forgot about this problem for
a while as we found a workaround; rude of me not to reply.
No worries.
The short answer is "I don't know". We're on a hosted environment and
the network topology is moreorless a mystery to those of us working on
the application layer. I believe it's something to do with dedicated
management NICs.
This is a mess, seriously. You ought to talk to whomever is responsible for
the network.
Since we have a workaround (i.e. always specify FQDN) and it looks
like any solution would involve all sorts of unravelling of network
routes and stuff I think we'll just stick with the workaround! Thanks
for your time anyway though.
No problem. I'd be extremely concerned about the health of your AD, tho.
On 28 Feb, 22:28, "Lanwench [MVP - Exchange]"
<lanwe...@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
gareththacke...@xxxxxxxxx wrote:
Hi,
We have a server in our Windows Server 2003 network that can only
make UNC fileshare access to another server by using \\<FQDN>;
simply using \\<ComputerName> produces a "The network path was not
found" error.
However, domain name resolution using just <ComputerName> works
fine, as does ping. \\<IPAddress> does not work either.
Any ideas how this could be or what to do about it? I think
NETBIOS / WINS is probably the answer but I don't have a full
enough idea of how these work to understand what to do.
Thanks in advance for any help.
Gareth
Please post an unedited ipconfig /all from this server & from your
DC (or one of them), clearly labeling which is which.- Hide quoted
text -
- Show quoted text -- Hide quoted text -
- Show quoted text -- Hide quoted text -
- Show quoted text -
.
- References:
- Re: Can only access servers via UNC if I use the FQDN
- From: gareththackeray
- Re: Can only access servers via UNC if I use the FQDN
- Prev by Date: Re: Daylight-saving best practice
- Next by Date: Re: Daylight saving best practice
- Previous by thread: Re: Can only access servers via UNC if I use the FQDN
- Next by thread: Re: 802.1x authentication issue
- Index(es):
Relevant Pages
|