Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
ADIR timing out in Windows NT
Message
General information
Forum:
Visual FoxPro
Category:
FoxPro 2.x
Miscellaneous
Thread ID:
00240921
Message ID:
00241002
Views:
20
>Ed,
> thanks for the reply. Unfortunately, we are using FoxPro 2.6, so we are forced to use ADIR(). We are logged into the domain. Any ideas?
>
> Is there a timeout parameter for NT? I ask this question because the workstation we're testing on is a win95 machine, but is accessing an NT server drive.
>

Nope, not on the NT side of things at least, and I have no idea what to tell you about a Win16 workaround. If you're seeing a different behavior, it's either something involving the protocol stack (you're probably using TCP/IP to talk to the NT Server, and using an IPX-compatible protocol for NetWare) or in the network client. If NetWare is working, you might try adding an IPX stack to the NT Server and use IPX/SPX compatible packets to talk across the WAN, but I wouldn't choose to go that route - OTOH, I wouldn't be using FPW, either...

>Thank you.
EMail: EdR@edrauh.com
"See, the sun is going down..."
"No, the horizon is moving up!"
- Firesign Theater


NT and Win2K FAQ .. cWashington WSH/ADSI/WMI site
MS WSH site ........... WSH FAQ Site
Wrox Press .............. Win32 Scripting Journal
eSolutions Services, LLC

The Surgeon General has determined that prolonged exposure to the Windows Script Host may be addictive to laboratory mice and codemonkeys
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform