Weird situation, I have a single domain network with a windows 2003
server as FS DNS DHCP etc. All of the systems on the network and in
the domain can resolve the server just fine (as well as all the other
systems in the domain). But, if I am building a system, or bring in a
system from a client, not in the domain, it gets an IP address from
the DHCP server just fine, resolves and pings all the systems on the
network just fine, BUT, if I try to connect to (or ping) the server,
it can not resolve it. It's bizarre. It just started recently because
I build systems all the time, and have the install source for acrobat
and FireFox etc on that server.

Normally I would go to \\server\source and it would prompt me to enter
the user ID and password and then connect just fine. Now if I try it
says it can't find the server. if I ping server it says it can't
resolve it, if I ping 192.168.10.100 it pings it just fine. Only
problem with connecting to \\192.168.10.100\source is that my install
batch points to the server\share for each install so it fails out.

Any idea where this might be going bad?

Read inline please.

In news:(E-Mail Removed),
Mick <(E-Mail Removed)> typed:
> Weird situation, I have a single domain network with a windows 2003
> server as FS DNS DHCP etc. All of the systems on the network and in
> the domain can resolve the server just fine (as well as all the other
> systems in the domain). But, if I am building a system, or bring in a
> system from a client, not in the domain, it gets an IP address from
> the DHCP server just fine, resolves and pings all the systems on the
> network just fine, BUT, if I try to connect to (or ping) the server,
> it can not resolve it. It's bizarre. It just started recently because
> I build systems all the time, and have the install source for acrobat
> and FireFox etc on that server.
>
> Normally I would go to \\server\source and it would prompt me to enter
> the user ID and password and then connect just fine. Now if I try it
> says it can't find the server. if I ping server it says it can't
> resolve it, if I ping 192.168.10.100 it pings it just fine. Only
> problem with connecting to \\192.168.10.100\source is that my install
> batch points to the server\share for each install so it fails out.
>
> Any idea where this might be going bad?

This is a NetBIOS resolution problem, "server" is not a DNS compatible name,
and until the client is joined to the domain, and it gets a primary DNS
suffix, which is added to the DNS suffix search list, host name resolution
in DNS won't work.
If you configure DHCP to use option 015 with the domain name, this will be
added to the DNS suffix search list. Without, a DNS suffix search list, it
falls back on NetBIOS resolution.



--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This Helps

===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
http://message.wftx.us/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================

Yep, that was it. Thanks!

On Oct 11, 12:47 pm, "Kevin D. Goodknecht Sr. [MVP]"
<ad...@nospam.WFTX.US> wrote:
> Read inline please.
>
> Innews:(E-Mail Removed),
> Mick <MickBurke...@gmail.com> typed:
>
>
>
> > Weird situation, I have a single domain network with a windows 2003
> > server as FS DNS DHCP etc. All of the systems on the network and in
> > the domain can resolve the server just fine (as well as all the other
> > systems in the domain). But, if I am building a system, or bring in a
> > system from a client, not in the domain, it gets an IP address from
> > the DHCP server just fine, resolves and pings all the systems on the
> > network just fine, BUT, if I try to connect to (or ping) the server,
> > it can not resolve it. It's bizarre. It just started recently because
> > I build systems all the time, and have the install source for acrobat
> > and FireFox etc on that server.
>
> > Normally I would go to \\server\source and it would prompt me to enter
> > the user ID and password and then connect just fine. Now if I try it
> > says it can't find the server. if I ping server it says it can't
> > resolve it, if I ping 192.168.10.100 it pings it just fine. Only
> > problem with connecting to \\192.168.10.100\source is that my install
> > batch points to the server\share for each install so it fails out.
>
> > Any idea where this might be going bad?
>
> This is a NetBIOS resolution problem, "server" is not a DNS compatible name,
> and until the client is joined to the domain, and it gets a primary DNS
> suffix, which is added to the DNS suffix search list, host name resolution
> in DNS won't work.
> If you configure DHCP to use option 015 with the domain name, this will be
> added to the DNS suffix search list. Without, a DNS suffix search list, it
> falls back on NetBIOS resolution.
>
> --
> Best regards,
> Kevin D. Goodknecht Sr. [MVP]
> Hope This Helps
>
> ===================================
> When responding to posts, please "Reply to Group"
> via your newsreader so that others may learn and
> benefit from your issue, to respond directly to
> me remove the nospam. from my email address.
> ===================================http://www.lonestaramerica.com/http://support.wftx.us/http://message.wftx.us/
> ===================================
> Use Outlook Express?... Get OE_Quotefix:
> It will strip signature out and morehttp://home.in.tum.de/~jain/software/oe-quotefix/
> ===================================
> Keep a back up of your OE settings and folders
> with OEBackup:http://www.oehelp.com/OEBackup/Default.aspx
> ===================================