Problems Document sharing w/ 2000 server and crossover cable

I've spent the entire day trying to move large files between 2
servers. I figured the easiest avenue was to connect a crossover
cable to the 2nd NICs on both systems. Share the directories that I
need to copy. Wala!

Negative.

Windows 2000 Server 1:
NIC 1 = Internet
NIC 2 = Crossover cable to Windows 2000 Server 2 (ip: 192.168.0.1/sn:
255.255.255.0)

Windows 200 Server 2:
NIC 1 = Internet (separate subnet than Server 1)
NIC 2 = Crossover cable to Windows 2000 Server 1 (ip: 192.168.0.2/sn:
255.255.255.0)

Both systems are in the same workgroup.

I can ping System 2 from System 1 and vice versa.

I go to run > "\\192.168.0.1\c$", system could not be found.
I tried using the system name and shared folder name, run > "\
\System1\SharedFolder, same results.

I've double checked permissions, I double checked connection.

I even used NSLOOKUP and ARP... the command prompts show no problems
with communications.

I can only believe it is some sort of Sharing Security Policy in 2000
Server.

Any ideas?

Thanks.
Larry

Hi Larry,

> ... Crossover cable ...
Can you place a hub in between (rather than going NIC to NIC)? I've
seen some odd ball problems with contention amoung who is autosensing
the line; DTE, who is DTC, etc.

> I've double checked permissions, I double checked connection.
Then, this is where I would investigate further. Can you provide an
output of CACLS of each server's shared folder (not the permissions on
the Share itself)?

Jeff

On Jun 1, 6:11 pm, "larryzo...@gmail.com" <larryzo...@gmail.com>
wrote:
> I've spent the entire day trying to move large files between 2
> servers. I figured the easiest avenue was to connect a crossover
> cable to the 2nd NICs on both systems. Share the directories that I
> need to copy. Wala!
>
> Negative.
>
> Windows 2000 Server 1:
> NIC 1 = Internet
> NIC 2 = Crossover cable to Windows 2000 Server 2 (ip: 192.168.0.1/sn:
> 255.255.255.0)
>
> Windows 200 Server 2:
> NIC 1 = Internet (separate subnet than Server 1)
> NIC 2 = Crossover cable to Windows 2000 Server 1 (ip: 192.168.0.2/sn:
> 255.255.255.0)
>
> Both systems are in the same workgroup.
>
> I can ping System 2 from System 1 and vice versa.
>
> I go to run > "\\192.168.0.1\c$", system could not be found.
> I tried using the system name and shared folder name, run > "\
> \System1\SharedFolder, same results.
>
> I've double checked permissions, I double checked connection.
>
> I even used NSLOOKUP and ARP... the command prompts show no problems
> with communications.
>
> I can only believe it is some sort of Sharing Security Policy in 2000
> Server.
>
> Any ideas?
>
> Thanks.
> Larry

Thanks for replying Jeff.

I'm not going home until I can start moving some files and I
definately don't want it to be a short weekend.

On System 1, the server that I am trying to get the data from:

C:\>calc e:\MoveMe
e:\MoveMe
System1\IUSER_System1OI)(CI)F
BUILTIN\AdministratorsOI)(CI)F
EveryoneOI)(CI)F

I'm not sure what all this means.... hopefully you can tell me.

Thanks.
Larry

On Jun 1, 6:31 pm, Jeffrey Walton <noloa...@gmail.com> wrote:
> Hi Larry,
>
> > ... Crossover cable ...
>
> Can you place a hub in between (rather than going NIC to NIC)? I've
> seen some odd ball problems with contention amoung who is autosensing
> the line; DTE, who is DTC, etc.
>
> > I've double checked permissions, I double checked connection.
>
> Then, this is where I would investigate further. Can you provide an
> output of CACLS of each server's shared folder (not the permissions on
> the Share itself)?
>
> Jeff
>
> On Jun 1, 6:11 pm, "larryzo...@gmail.com" <larryzo...@gmail.com>
> wrote:
>
>
>
> > I've spent the entire day trying to move large files between 2
> > servers. I figured the easiest avenue was to connect a crossover
> > cable to the 2nd NICs on both systems. Share the directories that I
> > need to copy. Wala!
>
> > Negative.
>
> > Windows 2000 Server 1:
> > NIC 1 = Internet
> > NIC 2 = Crossover cable to Windows 2000 Server 2 (ip: 192.168.0.1/sn:
> > 255.255.255.0)
>
> > Windows 200 Server 2:
> > NIC 1 = Internet (separate subnet than Server 1)
> > NIC 2 = Crossover cable to Windows 2000 Server 1 (ip: 192.168.0.2/sn:
> > 255.255.255.0)
>
> > Both systems are in the same workgroup.
>
> > I can ping System 2 from System 1 and vice versa.
>
> > I go to run > "\\192.168.0.1\c$", system could not be found.
> > I tried using the system name and shared folder name, run > "\
> > \System1\SharedFolder, same results.
>
> > I've double checked permissions, I double checked connection.
>
> > I even used NSLOOKUP and ARP... the command prompts show no problems
> > with communications.
>
> > I can only believe it is some sort of Sharing Security Policy in 2000
> > Server.
>
> > Any ideas?
>
> > Thanks.
> > Larry- Hide quoted text -
>
> - Show quoted text -

Here is the exact error I get when I START > RUN > \\192.168.0.1

The network location cannot be reached.

On Jun 1, 6:39 pm, "larryzo...@gmail.com" <larryzo...@gmail.com>
wrote:
> Thanks for replying Jeff.
>
> I'm not going home until I can start moving some files and I
> definately don't want it to be a short weekend.
>
> On System 1, the server that I am trying to get the data from:
>
> C:\>calc e:\MoveMe
> e:\MoveMe
> System1\IUSER_System1OI)(CI)F
> BUILTIN\AdministratorsOI)(CI)F
> EveryoneOI)(CI)F
>
> I'm not sure what all this means.... hopefully you can tell me.
>
> Thanks.
> Larry
>
> On Jun 1, 6:31 pm, Jeffrey Walton <noloa...@gmail.com> wrote:
>
>
>
> > Hi Larry,
>
> > > ... Crossover cable ...
>
> > Can you place a hub in between (rather than going NIC to NIC)? I've
> > seen some odd ball problems with contention amoung who is autosensing
> > the line; DTE, who is DTC, etc.
>
> > > I've double checked permissions, I double checked connection.
>
> > Then, this is where I would investigate further. Can you provide an
> > output of CACLS of each server's shared folder (not the permissions on
> > the Share itself)?
>
> > Jeff
>
> > On Jun 1, 6:11 pm, "larryzo...@gmail.com" <larryzo...@gmail.com>
> > wrote:
>
> > > I've spent the entire day trying to move large files between 2
> > > servers. I figured the easiest avenue was to connect a crossover
> > > cable to the 2nd NICs on both systems. Share the directories that I
> > > need to copy. Wala!
>
> > > Negative.
>
> > > Windows 2000 Server 1:
> > > NIC 1 = Internet
> > > NIC 2 = Crossover cable to Windows 2000 Server 2 (ip: 192.168.0.1/sn:
> > > 255.255.255.0)
>
> > > Windows 200 Server 2:
> > > NIC 1 = Internet (separate subnet than Server 1)
> > > NIC 2 = Crossover cable to Windows 2000 Server 1 (ip: 192.168.0.2/sn:
> > > 255.255.255.0)
>
> > > Both systems are in the same workgroup.
>
> > > I can ping System 2 from System 1 and vice versa.
>
> > > I go to run > "\\192.168.0.1\c$", system could not be found.
> > > I tried using the system name and shared folder name, run > "\
> > > \System1\SharedFolder, same results.
>
> > > I've double checked permissions, I double checked connection.
>
> > > I even used NSLOOKUP and ARP... the command prompts show no problems
> > > with communications.
>
> > > I can only believe it is some sort of Sharing Security Policy in 2000
> > > Server.
>
> > > Any ideas?
>
> > > Thanks.
> > > Larry- Hide quoted text -
>
> > - Show quoted text -- Hide quoted text -
>
> - Show quoted text -

Hi Larry,

I presume you've ruled out the crossover. At least look at the LEDs on
the NICs, and make sure there is no amber or red indications.

> EveryoneOI)(CI)F
This is the important one: Everyone - F (Full Control). OI and CI are
describing permission inheritance. We don't care how it got there, as
long as it is there.

Next, verify the accounts (on EACH server) used for the transfer.
WORKGROUPS are a collection of stand alones - under a single name
space. This is nothing like a Domain. There is no 'shared security
database'. So make sure user 'Larry' exists on both systems, with the
same password (we're trying to backdoor it using pass through
authentication).


On Jun 1, 6:39 pm, "larryzo...@gmail.com" <larryzo...@gmail.com>
wrote:
> Thanks for replying Jeff.
>
> I'm not going home until I can start moving some files and I
> definately don't want it to be a short weekend.
>
> On System 1, the server that I am trying to get the data from:
>
> C:\>calc e:\MoveMe
> e:\MoveMe
> System1\IUSER_System1OI)(CI)F
> BUILTIN\AdministratorsOI)(CI)F
> EveryoneOI)(CI)F
>
> I'm not sure what all this means.... hopefully you can tell me.
>
> Thanks.
> Larry
>
> On Jun 1, 6:31 pm, Jeffrey Walton <noloa...@gmail.com> wrote:
>
>
>
> > Hi Larry,
>
> > > ... Crossover cable ...
>
> > Can you place a hub in between (rather than going NIC to NIC)? I've
> > seen some odd ball problems with contention amoung who is autosensing
> > the line; DTE, who is DTC, etc.
>
> > > I've double checked permissions, I double checked connection.
>
> > Then, this is where I would investigate further. Can you provide an
> > output of CACLS of each server's shared folder (not the permissions on
> > the Share itself)?
>
> > Jeff
>
> > On Jun 1, 6:11 pm, "larryzo...@gmail.com" <larryzo...@gmail.com>
> > wrote:
>
> > > I've spent the entire day trying to move large files between 2
> > > servers. I figured the easiest avenue was to connect a crossover
> > > cable to the 2nd NICs on both systems. Share the directories that I
> > > need to copy. Wala!
>
> > > Negative.
>
> > > Windows 2000 Server 1:
> > > NIC 1 = Internet
> > > NIC 2 = Crossover cable to Windows 2000 Server 2 (ip: 192.168.0.1/sn:
> > > 255.255.255.0)
>
> > > Windows 200 Server 2:
> > > NIC 1 = Internet (separate subnet than Server 1)
> > > NIC 2 = Crossover cable to Windows 2000 Server 1 (ip: 192.168.0.2/sn:
> > > 255.255.255.0)
>
> > > Both systems are in the same workgroup.
>
> > > I can ping System 2 from System 1 and vice versa.
>
> > > I go to run > "\\192.168.0.1\c$", system could not be found.
> > > I tried using the system name and shared folder name, run > "\
> > > \System1\SharedFolder, same results.
>
> > > I've double checked permissions, I double checked connection.
>
> > > I even used NSLOOKUP and ARP... the command prompts show no problems
> > > with communications.
>
> > > I can only believe it is some sort of Sharing Security Policy in 2000
> > > Server.
>
> > > Any ideas?
>
> > > Thanks.
> > > Larry- >

I surely double checked the crossover. I get connectivity
(greenlights) on the NICs as well as the SysTray icons showing
connectivity as well as Amber lights when there is communications.

When I ping, I can see the packets of the two systems moving, so that
should be fine.

I created a local admin account by my name on both systems with the
same password. Log into both.

Created a test folder and shared it with the proper groups to gain
access.

It still tells me that the other System name was not found, I even
attempted to search My Network Places and Computers Around Me.
Nothing.

I'm wondering if there is a Service that isn't started that I'm not
aware of should be on. It could have been disabled in the mist of the
60 hot fixes Microsoft provided after SP4.

What do you think?

On Jun 1, 6:48 pm, Jeffrey Walton <noloa...@gmail.com> wrote:
> Hi Larry,
>
> I presume you've ruled out the crossover. At least look at the LEDs on
> the NICs, and make sure there is no amber or red indications.
>
> > EveryoneOI)(CI)F
>
> This is the important one: Everyone - F (Full Control). OI and CI are
> describing permission inheritance. We don't care how it got there, as
> long as it is there.
>
> Next, verify the accounts (on EACH server) used for the transfer.
> WORKGROUPS are a collection of stand alones - under a single name
> space. This is nothing like a Domain. There is no 'shared security
> database'. So make sure user 'Larry' exists on both systems, with the
> same password (we're trying to backdoor it using pass through
> authentication).
>
> On Jun 1, 6:39 pm, "larryzo...@gmail.com" <larryzo...@gmail.com>
> wrote:
>
>
>
> > Thanks for replying Jeff.
>
> > I'm not going home until I can start moving some files and I
> > definately don't want it to be a short weekend.
>
> > On System 1, the server that I am trying to get the data from:
>
> > C:\>calc e:\MoveMe
> > e:\MoveMe
> > System1\IUSER_System1OI)(CI)F
> > BUILTIN\AdministratorsOI)(CI)F
> > EveryoneOI)(CI)F
>
> > I'm not sure what all this means.... hopefully you can tell me.
>
> > Thanks.
> > Larry
>
> > On Jun 1, 6:31 pm, Jeffrey Walton <noloa...@gmail.com> wrote:
>
> > > Hi Larry,
>
> > > > ... Crossover cable ...
>
> > > Can you place a hub in between (rather than going NIC to NIC)? I've
> > > seen some odd ball problems with contention amoung who is autosensing
> > > the line; DTE, who is DTC, etc.
>
> > > > I've double checked permissions, I double checked connection.
>
> > > Then, this is where I would investigate further. Can you provide an
> > > output of CACLS of each server's shared folder (not the permissions on
> > > the Share itself)?
>
> > > Jeff
>
> > > On Jun 1, 6:11 pm, "larryzo...@gmail.com" <larryzo...@gmail.com>
> > > wrote:
>
> > > > I've spent the entire day trying to move large files between 2
> > > > servers. I figured the easiest avenue was to connect a crossover
> > > > cable to the 2nd NICs on both systems. Share the directories that I
> > > > need to copy. Wala!
>
> > > > Negative.
>
> > > > Windows 2000 Server 1:
> > > > NIC 1 = Internet
> > > > NIC 2 = Crossover cable to Windows 2000 Server 2 (ip: 192.168.0.1/sn:
> > > > 255.255.255.0)
>
> > > > Windows 200 Server 2:
> > > > NIC 1 = Internet (separate subnet than Server 1)
> > > > NIC 2 = Crossover cable to Windows 2000 Server 1 (ip: 192.168.0.2/sn:
> > > > 255.255.255.0)
>
> > > > Both systems are in the same workgroup.
>
> > > > I can ping System 2 from System 1 and vice versa.
>
> > > > I go to run > "\\192.168.0.1\c$", system could not be found.
> > > > I tried using the system name and shared folder name, run > "\
> > > > \System1\SharedFolder, same results.
>
> > > > I've double checked permissions, I double checked connection.
>
> > > > I even used NSLOOKUP and ARP... the command prompts show no problems
> > > > with communications.
>
> > > > I can only believe it is some sort of Sharing Security Policy in 2000
> > > > Server.
>
> > > > Any ideas?
>
> > > > Thanks.
> > > > Larry- >- Hide quoted text -
>
> - Show quoted text -

Hi Larry,

> It still tells me that the other System name was not found...
Add an entry to lmhosts in %SYSTEM32%\Drivers\etc (etc is the name of
the folder). IIRC, lmhosts does not have an exetension. Open it with
notepad, edit, and save without an extension.

The hosts and lmhosts file are parsed before a DNS or WINS resolution
occurs, so you should be safe. If this does not work, post the output
of "Route PRINT".

Jeff

On Jun 1, 7:04 pm, "larryzo...@gmail.com" <larryzo...@gmail.com>
wrote:
> I surely double checked the crossover. I get connectivity
> (greenlights) on the NICs as well as the SysTray icons showing
> connectivity as well as Amber lights when there is communications.
>
> When I ping, I can see the packets of the two systems moving, so that
> should be fine.
>
> I created a local admin account by my name on both systems with the
> same password. Log into both.
>
> Created a test folder and shared it with the proper groups to gain
> access.
>
> It still tells me that the other System name was not found, I even
> attempted to search My Network Places and Computers Around Me.
> Nothing.
>
> I'm wondering if there is a Service that isn't started that I'm not
> aware of should be on. It could have been disabled in the mist of the
> 60 hot fixes Microsoft provided after SP4.
>
> What do you think?
>
> On Jun 1, 6:48 pm, Jeffrey Walton <noloa...@gmail.com> wrote:
>
>
>
> > Hi Larry,
>
> > I presume you've ruled out the crossover. At least look at the LEDs on
> > the NICs, and make sure there is no amber or red indications.
>
> > > EveryoneOI)(CI)F
>
> > This is the important one: Everyone - F (Full Control). OI and CI are
> > describing permission inheritance. We don't care how it got there, as
> > long as it is there.
>
> > Next, verify the accounts (on EACH server) used for the transfer.
> > WORKGROUPS are a collection of stand alones - under a single name
> > space. This is nothing like a Domain. There is no 'shared security
> > database'. So make sure user 'Larry' exists on both systems, with the
> > same password (we're trying to backdoor it using pass through
> > authentication).
>
> > On Jun 1, 6:39 pm, "larryzo...@gmail.com" <larryzo...@gmail.com>
> > wrote:
>
> > > Thanks for replying Jeff.
>
> > > I'm not going home until I can start moving some files and I
> > > definately don't want it to be a short weekend.
>
> > > On System 1, the server that I am trying to get the data from:
>
> > > C:\>calc e:\MoveMe
> > > e:\MoveMe
> > > System1\IUSER_System1OI)(CI)F
> > > BUILTIN\AdministratorsOI)(CI)F
> > > EveryoneOI)(CI)F
>
> > > I'm not sure what all this means.... hopefully you can tell me.
>
> > > Thanks.
> > > Larry
>
> > > On Jun 1, 6:31 pm, Jeffrey Walton <noloa...@gmail.com> wrote:
>
> > > > Hi Larry,
>
> > > > > ... Crossover cable ...
>
> > > > Can you place a hub in between (rather than going NIC to NIC)? I've
> > > > seen some odd ball problems with contention amoung who is autosensing
> > > > the line; DTE, who is DTC, etc.
>
> > > > > I've double checked permissions, I double checked connection.
>
> > > > Then, this is where I would investigate further. Can you provide an
> > > > output of CACLS of each server's shared folder (not the permissions on
> > > > the Share itself)?
>
> > > > Jeff
>
> > > > On Jun 1, 6:11 pm, "larryzo...@gmail.com" <larryzo...@gmail.com>
> > > > wrote:
>
> > > > > I've spent the entire day trying to move large files between 2
> > > > > servers. I figured the easiest avenue was to connect a crossover
> > > > > cable to the 2nd NICs on both systems. Share the directories that I
> > > > > need to copy. Wala!
>
> > > > > Negative.
>
> > > > > Windows 2000 Server 1:
> > > > > NIC 1 = Internet
> > > > > NIC 2 = Crossover cable to Windows 2000 Server 2 (ip: 192.168.0.1/sn:
> > > > > 255.255.255.0)
>
> > > > > Windows 200 Server 2:
> > > > > NIC 1 = Internet (separate subnet than Server 1)
> > > > > NIC 2 = Crossover cable to Windows 2000 Server 1 (ip: 192.168.0.2/sn:
> > > > > 255.255.255.0)
>
> > > > > Both systems are in the same workgroup.
>
> > > > > I can ping System 2 from System 1 and vice versa.
>
> > > > > I go to run > "\\192.168.0.1\c$", system could not be found.
> > > > > I tried using the system name and shared folder name, run > "\
> > > > > \System1\SharedFolder, same results.
>
> > > > > I've double checked permissions, I double checked connection.
>
> > > > > I even used NSLOOKUP and ARP... the command prompts show no problems
> > > > > with communications.
>
> > > > > I can only believe it is some sort of Sharing Security Policy in 2000
> > > > > Server.
>
> > > > > Any ideas?
>
> > > > > Thanks.
> > > > > Larry- >- Hide quoted text -
>
> > - Show quoted text -- Hide quoted text -
>
> - Show quoted text -

Hi Larry,

Also, post the output of ping <other server by IP>. I'm interested to
see if the request is going out on the wrong interface (i.e., to the
internet) rather than the Crossover interface. Route will show this
conclusevly.

Jeff


Jeff

On Jun 1, 7:04 pm, "larryzo...@gmail.com" <larryzo...@gmail.com>
wrote:
> I surely double checked the crossover. I get connectivity
> (greenlights) on the NICs as well as the SysTray icons showing
> connectivity as well as Amber lights when there is communications.
>
> When I ping, I can see the packets of the two systems moving, so that
> should be fine.
>
> I created a local admin account by my name on both systems with the
> same password. Log into both.
>
> Created a test folder and shared it with the proper groups to gain
> access.
>
> It still tells me that the other System name was not found, I even
> attempted to search My Network Places and Computers Around Me.
> Nothing.
>
> I'm wondering if there is a Service that isn't started that I'm not
> aware of should be on. It could have been disabled in the mist of the
> 60 hot fixes Microsoft provided after SP4.
>
> What do you think?
>
> On Jun 1, 6:48 pm, Jeffrey Walton <noloa...@gmail.com> wrote:
>
>
>
> > Hi Larry,
>
> > I presume you've ruled out the crossover. At least look at the LEDs on
> > the NICs, and make sure there is no amber or red indications.
>
> > > EveryoneOI)(CI)F
>
> > This is the important one: Everyone - F (Full Control). OI and CI are
> > describing permission inheritance. We don't care how it got there, as
> > long as it is there.
>
> > Next, verify the accounts (on EACH server) used for the transfer.
> > WORKGROUPS are a collection of stand alones - under a single name
> > space. This is nothing like a Domain. There is no 'shared security
> > database'. So make sure user 'Larry' exists on both systems, with the
> > same password (we're trying to backdoor it using pass through
> > authentication).
>
> > On Jun 1, 6:39 pm, "larryzo...@gmail.com" <larryzo...@gmail.com>
> > wrote:
>
> > > Thanks for replying Jeff.
>
> > > I'm not going home until I can start moving some files and I
> > > definately don't want it to be a short weekend.
>
> > > On System 1, the server that I am trying to get the data from:
>
> > > C:\>calc e:\MoveMe
> > > e:\MoveMe
> > > System1\IUSER_System1OI)(CI)F
> > > BUILTIN\AdministratorsOI)(CI)F
> > > EveryoneOI)(CI)F
>
> > > I'm not sure what all this means.... hopefully you can tell me.
>
> > > Thanks.
> > > Larry
>
> > > On Jun 1, 6:31 pm, Jeffrey Walton <noloa...@gmail.com> wrote:
>
> > > > Hi Larry,
>
> > > > > ... Crossover cable ...
>
> > > > Can you place a hub in between (rather than going NIC to NIC)? I've
> > > > seen some odd ball problems with contention amoung who is autosensing
> > > > the line; DTE, who is DTC, etc.
>
> > > > > I've double checked permissions, I double checked connection.
>
> > > > Then, this is where I would investigate further. Can you provide an
> > > > output of CACLS of each server's shared folder (not the permissions on
> > > > the Share itself)?
>
> > > > Jeff
>
> > > > On Jun 1, 6:11 pm, "larryzo...@gmail.com" <larryzo...@gmail.com>
> > > > wrote:
>
> > > > > I've spent the entire day trying to move large files between 2
> > > > > servers. I figured the easiest avenue was to connect a crossover
> > > > > cable to the 2nd NICs on both systems. Share the directories that I
> > > > > need to copy. Wala!
>
> > > > > Negative.
>
> > > > > Windows 2000 Server 1:
> > > > > NIC 1 = Internet
> > > > > NIC 2 = Crossover cable to Windows 2000 Server 2 (ip: 192.168.0.1/sn:
> > > > > 255.255.255.0)
>
> > > > > Windows 200 Server 2:
> > > > > NIC 1 = Internet (separate subnet than Server 1)
> > > > > NIC 2 = Crossover cable to Windows 2000 Server 1 (ip: 192.168.0.2/sn:
> > > > > 255.255.255.0)
>
> > > > > Both systems are in the same workgroup.
>
> > > > > I can ping System 2 from System 1 and vice versa.
>
> > > > > I go to run > "\\192.168.0.1\c$", system could not be found.
> > > > > I tried using the system name and shared folder name, run > "\
> > > > > \System1\SharedFolder, same results.
>
> > > > > I've double checked permissions, I double checked connection.
>
> > > > > I even used NSLOOKUP and ARP... the command prompts show no problems
> > > > > with communications.
>
> > > > > I can only believe it is some sort of Sharing Security Policy in 2000
> > > > > Server.
>
> > > > > Any ideas?
>
> > > > > Thanks.
> > > > > Larry- >- Hide quoted text -
>
> > - Show quoted text -- Hide quoted text -
>
> - Show quoted text -

Help me with this one...

>Add an entry to lmhosts in %SYSTEM32%\Drivers\etc (etc is the name of
>the folder). IIRC, lmhosts does not have an exetension. Open it with
>notepad, edit, and save without an extension.

>The hosts and lmhosts file are parsed before a DNS or WINS resolution
>occurs, so you should be safe. If this does not work, post the output
>of "Route PRINT".

I did find the LMHOST file on both servers. The old server (System 1)
had a .SAM extension. I'm not sure what that means, but I removed the
ext.

Forgive me, I'm not a very good microsoft network guy. I appreciate
your help.

Larry

====================================

System 1:
Ethernet adapter XOVER:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT
Network Connect
ion #2
Physical Address. . . . . . . . . : 00-14-22-0E-96-F7
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled

C:\>ping 192.168.0.1

Pinging 192.168.0.1 with 32 bytes of data:

Reply from 192.168.0.1: bytes=32 time<10ms TTL=128
Reply from 192.168.0.1: bytes=32 time<10ms TTL=128
Reply from 192.168.0.1: bytes=32 time<10ms TTL=128
Reply from 192.168.0.1: bytes=32 time<10ms TTL=128

Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\>tracert -d 192.168.0.1

Tracing route to 192.168.0.1 over a maximum of 30 hops

1 <10 ms <10 ms <10 ms 192.168.0.1

Trace complete.

===============================================

System 2:
Ethernet adapter X-OVER:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 XT
Network Connect
ion #2
Physical Address. . . . . . . . . : 00-0B-DB-91-04-15
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . :

C:\>ping 192.168.0.2

Pinging 192.168.0.2 with 32 bytes of data:

Reply from 192.168.0.2: bytes=32 time<10ms TTL=128
Reply from 192.168.0.2: bytes=32 time<10ms TTL=128
Reply from 192.168.0.2: bytes=32 time<10ms TTL=128
Reply from 192.168.0.2: bytes=32 time<10ms TTL=128

Ping statistics for 192.168.0.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\>tracert -d 192.168.0.2

Tracing route to 192.168.0.2 over a maximum of 30 hops

1 <10 ms <10 ms <10 ms 192.168.0.2

Trace complete.















On Jun 1, 7:53 pm, Jeffrey Walton <noloa...@gmail.com> wrote:
> Hi Larry,
>
> Also, post the output of ping <other server by IP>. I'm interested to
> see if the request is going out on the wrong interface (i.e., to the
> internet) rather than the Crossover interface. Route will show this
> conclusevly.
>
> Jeff
>
> Jeff
>
> On Jun 1, 7:04 pm, "larryzo...@gmail.com" <larryzo...@gmail.com>
> wrote:
>
>
>
> > I surely double checked the crossover. I get connectivity
> > (greenlights) on the NICs as well as the SysTray icons showing
> > connectivity as well as Amber lights when there is communications.
>
> > When I ping, I can see the packets of the two systems moving, so that
> > should be fine.
>
> > I created a local admin account by my name on both systems with the
> > same password. Log into both.
>
> > Created a test folder and shared it with the proper groups to gain
> > access.
>
> > It still tells me that the other System name was not found, I even
> > attempted to search My Network Places and Computers Around Me.
> > Nothing.
>
> > I'm wondering if there is a Service that isn't started that I'm not
> > aware of should be on. It could have been disabled in the mist of the
> > 60 hot fixes Microsoft provided after SP4.
>
> > What do you think?
>
> > On Jun 1, 6:48 pm, Jeffrey Walton <noloa...@gmail.com> wrote:
>
> > > Hi Larry,
>
> > > I presume you've ruled out the crossover. At least look at the LEDs on
> > > the NICs, and make sure there is no amber or red indications.
>
> > > > EveryoneOI)(CI)F
>
> > > This is the important one: Everyone - F (Full Control). OI and CI are
> > > describing permission inheritance. We don't care how it got there, as
> > > long as it is there.
>
> > > Next, verify the accounts (on EACH server) used for the transfer.
> > > WORKGROUPS are a collection of stand alones - under a single name
> > > space. This is nothing like a Domain. There is no 'shared security
> > > database'. So make sure user 'Larry' exists on both systems, with the
> > > same password (we're trying to backdoor it using pass through
> > > authentication).
>
> > > On Jun 1, 6:39 pm, "larryzo...@gmail.com" <larryzo...@gmail.com>
> > > wrote:
>
> > > > Thanks for replying Jeff.
>
> > > > I'm not going home until I can start moving some files and I
> > > > definately don't want it to be a short weekend.
>
> > > > On System 1, the server that I am trying to get the data from:
>
> > > > C:\>calc e:\MoveMe
> > > > e:\MoveMe
> > > > System1\IUSER_System1OI)(CI)F
> > > > BUILTIN\AdministratorsOI)(CI)F
> > > > EveryoneOI)(CI)F
>
> > > > I'm not sure what all this means.... hopefully you can tell me.
>
> > > > Thanks.
> > > > Larry
>
> > > > On Jun 1, 6:31 pm, Jeffrey Walton <noloa...@gmail.com> wrote:
>
> > > > > Hi Larry,
>
> > > > > > ... Crossover cable ...
>
> > > > > Can you place a hub in between (rather than going NIC to NIC)? I've
> > > > > seen some odd ball problems with contention amoung who is autosensing
> > > > > the line; DTE, who is DTC, etc.
>
> > > > > > I've double checked permissions, I double checked connection.
>
> > > > > Then, this is where I would investigate further. Can you provide an
> > > > > output of CACLS of each server's shared folder (not the permissions on
> > > > > the Share itself)?
>
> > > > > Jeff
>
> > > > > On Jun 1, 6:11 pm, "larryzo...@gmail.com" <larryzo...@gmail.com>
> > > > > wrote:
>
> > > > > > I've spent the entire day trying to move large files between 2
> > > > > > servers. I figured the easiest avenue was to connect a crossover
> > > > > > cable to the 2nd NICs on both systems. Share the directories that I
> > > > > > need to copy. Wala!
>
> > > > > > Negative.
>
> > > > > > Windows 2000 Server 1:
> > > > > > NIC 1 = Internet
> > > > > > NIC 2 = Crossover cable to Windows 2000 Server 2 (ip: 192.168.0.1/sn:
> > > > > > 255.255.255.0)
>
> > > > > > Windows 200 Server 2:
> > > > > > NIC 1 = Internet (separate subnet than Server 1)
> > > > > > NIC 2 = Crossover cable to Windows 2000 Server 1 (ip: 192.168.0.2/sn:
> > > > > > 255.255.255.0)
>
> > > > > > Both systems are in the same workgroup.
>
> > > > > > I can ping System 2 from System 1 and vice versa.
>
> > > > > > I go to run > "\\192.168.0.1\c$", system could not be found.
> > > > > > I tried using the system name and shared folder name, run > "\
> > > > > > \System1\SharedFolder, same results.
>
> > > > > > I've double checked permissions, I double checked connection.
>
> > > > > > I even used NSLOOKUP and ARP... the command prompts show no problems
> > > > > > with communications.
>
> > > > > > I can only believe it is some sort of Sharing Security Policy in 2000
> > > > > > Server.
>
> > > > > > Any ideas?
>
> > > > > > Thanks.
> > > > > > Larry- >- Hide quoted text -
>
> > > - Show quoted text -- Hide quoted text -
>
> > - Show quoted text -- Hide quoted text -
>
> - Show quoted text -

Hi Larry,

> I did find the LMHOST file on both servers. The old server (System 1)
> had a .SAM extension. I'm not sure what that means, but I removed the
> ext.
Add the SAM extension back (my bad).

> Default Gateway . . . . . . . . . :
No default gateway - suspect but it has been a few years since I
worked with a multihomed system. We use multiple NICs for Teaming -
redundancy or throughput.

> C:\>ping 192.168.0.1
> Pinging 192.168.0.1 with 32 bytes of data:
> Reply from 192.168.0.1: bytes=32 time<10ms TTL=128
This indicates network connectivity. We need to go higher up in the
protocol stack. See http://www.howtonetworking.com/workgroupsetup.htm.
Sorry it's been too long for a Workgroup for me - 1999.

Jeff

On Jun 1, 8:39 pm, "larryzo...@gmail.com" <larryzo...@gmail.com>
wrote:
> Help me with this one...
>
> >Add an entry to lmhosts in %SYSTEM32%\Drivers\etc (etc is the name of
> >the folder). IIRC, lmhosts does not have an exetension. Open it with
> >notepad, edit, and save without an extension.
> >The hosts and lmhosts file are parsed before a DNS or WINS resolution
> >occurs, so you should be safe. If this does not work, post the output
> >of "Route PRINT".
>
> I did find the LMHOST file on both servers. The old server (System 1)
> had a .SAM extension. I'm not sure what that means, but I removed the
> ext.
>
> Forgive me, I'm not a very good microsoft network guy. I appreciate
> your help.
>
> Larry
>
> ====================================
>
> System 1:
> Ethernet adapter XOVER:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Intel(R) PRO/1000 MT
> Network Connect
> ion #2
> Physical Address. . . . . . . . . : 00-14-22-0E-96-F7
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.0.2
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . :
> DNS Servers . . . . . . . . . . . :
> NetBIOS over Tcpip. . . . . . . . : Disabled
>
> C:\>ping 192.168.0.1
>
> Pinging 192.168.0.1 with 32 bytes of data:
>
> Reply from 192.168.0.1: bytes=32 time<10ms TTL=128
> Reply from 192.168.0.1: bytes=32 time<10ms TTL=128
> Reply from 192.168.0.1: bytes=32 time<10ms TTL=128
> Reply from 192.168.0.1: bytes=32 time<10ms TTL=128
>
> Ping statistics for 192.168.0.1:
> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> Approximate round trip times in milli-seconds:
> Minimum = 0ms, Maximum = 0ms, Average = 0ms
>
> C:\>tracert -d 192.168.0.1
>
> Tracing route to 192.168.0.1 over a maximum of 30 hops
>
> 1 <10 ms <10 ms <10 ms 192.168.0.1
>
> Trace complete.
>
> ===============================================
>
> System 2:
> Ethernet adapter X-OVER:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Intel(R) PRO/1000 XT
> Network Connect
> ion #2
> Physical Address. . . . . . . . . : 00-0B-DB-91-04-15
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.0.1
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . :
> DNS Servers . . . . . . . . . . . :
>
> C:\>ping 192.168.0.2
>
> Pinging 192.168.0.2 with 32 bytes of data:
>
> Reply from 192.168.0.2: bytes=32 time<10ms TTL=128
> Reply from 192.168.0.2: bytes=32 time<10ms TTL=128
> Reply from 192.168.0.2: bytes=32 time<10ms TTL=128
> Reply from 192.168.0.2: bytes=32 time<10ms TTL=128
>
> Ping statistics for 192.168.0.2:
> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> Approximate round trip times in milli-seconds:
> Minimum = 0ms, Maximum = 0ms, Average = 0ms
>
> C:\>tracert -d 192.168.0.2
>
> Tracing route to 192.168.0.2 over a maximum of 30 hops
>
> 1 <10 ms <10 ms <10 ms 192.168.0.2
>
> Trace complete.
>
> On Jun 1, 7:53 pm, Jeffrey Walton <noloa...@gmail.com> wrote:
>
>
>
> > Hi Larry,
>
> > Also, post the output of ping <other server by IP>. I'm interested to
> > see if the request is going out on the wrong interface (i.e., to the
> > internet) rather than the Crossover interface. Route will show this
> > conclusevly.
>
> > Jeff
>
> > Jeff
>
> > On Jun 1, 7:04 pm, "larryzo...@gmail.com" <larryzo...@gmail.com>
> > wrote:
>
> > > I surely double checked the crossover. I get connectivity
> > > (greenlights) on the NICs as well as the SysTray icons showing
> > > connectivity as well as Amber lights when there is communications.
>
> > > When I ping, I can see the packets of the two systems moving, so that
> > > should be fine.
>
> > > I created a local admin account by my name on both systems with the
> > > same password. Log into both.
>
> > > Created a test folder and shared it with the proper groups to gain
> > > access.
>
> > > It still tells me that the other System name was not found, I even
> > > attempted to search My Network Places and Computers Around Me.
> > > Nothing.
>
> > > I'm wondering if there is a Service that isn't started that I'm not
> > > aware of should be on. It could have been disabled in the mist of the
> > > 60 hot fixes Microsoft provided after SP4.
>
> > > What do you think?
>
> > > On Jun 1, 6:48 pm, Jeffrey Walton <noloa...@gmail.com> wrote:
>
> > > > Hi Larry,
>
> > > > I presume you've ruled out the crossover. At least look at the LEDs on
> > > > the NICs, and make sure there is no amber or red indications.
>
> > > > > EveryoneOI)(CI)F
>
> > > > This is the important one: Everyone - F (Full Control). OI and CI are
> > > > describing permission inheritance. We don't care how it got there, as
> > > > long as it is there.
>
> > > > Next, verify the accounts (on EACH server) used for the transfer.
> > > > WORKGROUPS are a collection of stand alones - under a single name
> > > > space. This is nothing like a Domain. There is no 'shared security
> > > > database'. So make sure user 'Larry' exists on both systems, with the
> > > > same password (we're trying to backdoor it using pass through
> > > > authentication).
>
> > > > On Jun 1, 6:39 pm, "larryzo...@gmail.com" <larryzo...@gmail.com>
> > > > wrote:
>
> > > > > Thanks for replying Jeff.
>
> > > > > I'm not going home until I can start moving some files and I
> > > > > definately don't want it to be a short weekend.
>
> > > > > On System 1, the server that I am trying to get the data from:
>
> > > > > C:\>calc e:\MoveMe
> > > > > e:\MoveMe
> > > > > System1\IUSER_System1OI)(CI)F
> > > > > BUILTIN\AdministratorsOI)(CI)F
> > > > > EveryoneOI)(CI)F
>
> > > > > I'm not sure what all this means.... hopefully you can tell me.
>
> > > > > Thanks.
> > > > > Larry
>
> > > > > On Jun 1, 6:31 pm, Jeffrey Walton <noloa...@gmail.com> wrote:
>
> > > > > > Hi Larry,
>
> > > > > > > ... Crossover cable ...
>
> > > > > > Can you place a hub in between (rather than going NIC to NIC)? I've
> > > > > > seen some odd ball problems with contention amoung who is autosensing
> > > > > > the line; DTE, who is DTC, etc.
>
> > > > > > > I've double checked permissions, I double checked connection.
>
> > > > > > Then, this is where I would investigate further. Can you provide an
> > > > > > output of CACLS of each server's shared folder (not the permissions on
> > > > > > the Share itself)?
>
> > > > > > Jeff
>
> > > > > > On Jun 1, 6:11 pm, "larryzo...@gmail.com" <larryzo...@gmail.com>
> > > > > > wrote:
>
> > > > > > > I've spent the entire day trying to move large files between 2
> > > > > > > servers. I figured the easiest avenue was to connect a crossover
> > > > > > > cable to the 2nd NICs on both systems. Share the directories that I
> > > > > > > need to copy. Wala!
>
> > > > > > > Negative.
>
> > > > > > > Windows 2000 Server 1:
> > > > > > > NIC 1 = Internet
> > > > > > > NIC 2 = Crossover cable to Windows 2000 Server 2 (ip: 192.168.0.1/sn:
> > > > > > > 255.255.255.0)
>
> > > > > > > Windows 200 Server 2:
> > > > > > > NIC 1 = Internet (separate subnet than Server 1)
> > > > > > > NIC 2 = Crossover cable to Windows 2000 Server 1 (ip: 192.168.0.2/sn:
> > > > > > > 255.255.255.0)
>
> > > > > > > Both systems are in the same workgroup.
>
> > > > > > > I can ping System 2 from System 1 and vice versa.
>
> > > > > > > I go to run > "\\192.168.0.1\c$", system could not be found.
> > > > > > > I tried using the system name and shared folder name, run > "\
> > > > > > > \System1\SharedFolder, same results.
>
> > > > > > > I've double checked permissions, I double checked connection.
>
> > > > > > > I even used NSLOOKUP and ARP... the command prompts show no problems
> > > > > > > with communications.
>
> > > > > > > I can only believe it is some sort of Sharing Security Policy in 2000
> > > > > > > Server.
>
> > > > > > > Any ideas?
>
> > > > > > > Thanks.
> > > > > > > Larry- >- Hide quoted text -
>
> > > > - Show quoted text -- Hide quoted text -
>
> > > - Show quoted text -- Hide quoted text -
>
> > - Show quoted text -- Hide quoted text -
>
> - Show quoted text -