🚀 go-pugleaf

Not sure if anyone can help but I have ran into a weird problem with
WNetAddConnection2(), one of those "it should work but it doesn't"
problems... First off, the code is working fine in 14 locations with the
same computer/network setup. I would post the actual code but don't think it
would help because it is working in more places than it isn't.

A little background...

3 computers tied together, two running Windows 2000 one running NT 4.0,
simple LAN using NetBEUI. The two windows 2000 computers connect to a drive
on the NT computer via WNetAddConnection2() (logging in as Guest) in the
application(s) software. The code is identical in both applications. The
Guest account on the NT machine has Admin status...

In one location one of the Windows 2000 computers refuses to connect,
WNetAddConnection2() fails. Lets just call the two Win2000 computers Comp1
and Comp2 for the following...

Comp1 connects to the NT computer fine.
Comp2 refuses to connect even if Comp1 isn't on.
Replace Comp2 with another Computer and it works.
Take Comp2 to a different site and it works.
Can access the NT computers drive from Comp2 through My Network.
Can access Comp2 from the NT computer through Network Neighborhood.

It seem like that particular windows 2000 computer doesn't like that
particular NT computer because through all the switching and swapping
everything works except when these two computers are tied together.

Please understand this isn't a simple network problem we have spent two
solid days on the phone chasing down all the normal stuff plus the guy on
the other end has made many trips to another site swapping computers. Also a
permanent computer swap isn't possible for reasons outside my control. I
have an exact copy of the system here in my office and it works great, if I
could make this one fail I would know what is wrong with the other.

Any Ideas ? If I can't come up with a solution before next Tuesday I will
have to make a 900 mile round trip to try and fix it.

-- 
Bob