M
Mick
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?
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?