G
Guest
Hi,
I have a SBS 2000 server. It is the domain controller for our network (name
of machine CNG1). I have another machine, CNG3, which has Windows Server 2003
OS, but besides "File Server," it doesn't have any other roles installed. We
just use it for just that, file serving.
I joined the CNG3 machine to the SBS 2000 domain a few months ago. No
problem. I could map network drives from one machine to the other in both
directions.
Recently I have been getting the roaming profile cannot be loaded when I try
to log onto the SBS 2000 domain from the CNG3 (Windows Server 2003) machine.
No biggie.
But today, I can't map CNG1 network drives. If I am on the CNG3 (Win 2k3),
and try to map a network drive that is on the CNG1 domain controller machine,
I can't do it (whether I use \\CNG1\share or \\10.0.0.3\share), I get "The
drive could not be mapped because no network was found." But if I am on the
DC machine named CNG1, I can map a CNG3 network drive both with \\CNG3\share1
and \\10.0.0.4\share1
I have BackupExec installed on CNG 1. I also can't "see" the CNG3 machine
anymore when I use BackupExec under the "Remote Selections>Microsoft Windows
Network>MYCUSTOMDOMAIN" when want to back stuff up from the CNG3 machine. I
did make sure the "Backup Exec Remote Agent for Windows Servers" service is
started.
I can ping either machine from either machine.
I did a nslookup while on the CNG3 machine and I got
--
C:\Documents and Settings\growe>nslookup mycustomdomain.com
Server: CNG1.mycustomdomain.com
Address: 10.0.0.3
Name: mycustomdomain.com
Address: 10.0.0.3
--
internal network:
CNG1 10.0.0.3
CNG3 10.0.0.4
default gateway 10.0.0.2
I am sorry for the long note. I have GOT to backup items on the CNG3
machine. Any help will be greatly appreciated.
Thank you,
Grigore
I have a SBS 2000 server. It is the domain controller for our network (name
of machine CNG1). I have another machine, CNG3, which has Windows Server 2003
OS, but besides "File Server," it doesn't have any other roles installed. We
just use it for just that, file serving.
I joined the CNG3 machine to the SBS 2000 domain a few months ago. No
problem. I could map network drives from one machine to the other in both
directions.
Recently I have been getting the roaming profile cannot be loaded when I try
to log onto the SBS 2000 domain from the CNG3 (Windows Server 2003) machine.
No biggie.
But today, I can't map CNG1 network drives. If I am on the CNG3 (Win 2k3),
and try to map a network drive that is on the CNG1 domain controller machine,
I can't do it (whether I use \\CNG1\share or \\10.0.0.3\share), I get "The
drive could not be mapped because no network was found." But if I am on the
DC machine named CNG1, I can map a CNG3 network drive both with \\CNG3\share1
and \\10.0.0.4\share1
I have BackupExec installed on CNG 1. I also can't "see" the CNG3 machine
anymore when I use BackupExec under the "Remote Selections>Microsoft Windows
Network>MYCUSTOMDOMAIN" when want to back stuff up from the CNG3 machine. I
did make sure the "Backup Exec Remote Agent for Windows Servers" service is
started.
I can ping either machine from either machine.
I did a nslookup while on the CNG3 machine and I got
--
C:\Documents and Settings\growe>nslookup mycustomdomain.com
Server: CNG1.mycustomdomain.com
Address: 10.0.0.3
Name: mycustomdomain.com
Address: 10.0.0.3
--
internal network:
CNG1 10.0.0.3
CNG3 10.0.0.4
default gateway 10.0.0.2
I am sorry for the long note. I have GOT to backup items on the CNG3
machine. Any help will be greatly appreciated.
Thank you,
Grigore