Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
NOT FP/VFP but I am Desperately Seeking Network
Message
De
21/10/1997 18:53:18
 
 
À
Tous
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Titre:
NOT FP/VFP but I am Desperately Seeking Network
Divers
Thread ID:
00055895
Message ID:
00055895
Vues:
72
Hi all,

This has been eating me for a week now, so I thought I'd try here.

My current contract is at a place short on space, so they offered a ISDN service at home if I would use it to work there. Great!
Got it installed and got *most* things working. . . EXCEPT the MOST important thing.
It is set up through Win95 Dial-Up Networking, where I d-click a shortcut and a "Connect" dialogue appears. I click connect and it connects. I can then start up things like Lotus Notes and Extra! and talk to mainframe. BUT I also need to see the company's NT Network, and I never get "invited" to supply a password to do so.

The one little hooker in all this is that I have a 2-computer network (using SMC adapters and Ethernet). *Since* ininstalled the ISDN modem and the Dial-Up Networking *and* changed the "Client for Microsoft Networks" properties to check (on) "Connect to NT Server" and supplied the proper Domain name there, my boot-up networking dialogue chaged from only two entries (User Name & Password) to 3 items - User name, Password and Domain and domain is always filled with the same domain name that I supplied above.

Naturally, *THAT* domain name is *NOT* yet connected (it is the DIAL-UP, after all), so it comes back with a message along the lines of 'user authentication could not be done because the server was not available. . . some network resources may not be available as anticipated'. I click OK and I see MY local network. When I *then* dial up the company, it *SEEMS* that any references to the Domain have been 'used up' and it never seems to try that connection for the domain.

SUMMARY: On a 2 computer network with a dialup to a LAN, the LAN is *NOT* accessible (though it is useable) - at least the drives on the domain of interest are not accessible.

Finally, two calls to Microsoft said that this could NOT be done with "standard" settings alone. I would believe them, except that a guy in the office *IS* doing exactly this. Unfortunately, he does not know the details of how he accomplished it, but does confirm that he uses adapters for local net and an ISDN to the computer in question.

Can anyone shed any light????

All help truly appreciated.

Jim N
Répondre
Fil
Voir

Click here to load this message in the networking platform