timbar Posted February 21, 2008 Report Posted February 21, 2008 Attmpting to set up a mapped drive to run fscommander with widefs. Its a new build PC running Vista 64. I have mapped the root of each drive on each machine and can open the drives from the other machine but widefs does not connect. :?:
Pete Dowson Posted February 21, 2008 Report Posted February 21, 2008 Attmpting to set up a mapped drive to run fscommander with widefs. Its a new build PC running Vista 64. I have mapped the root of each drive on each machine and can open the drives from the other machine but widefs does not connect. :?: WideFS has nothing to do with drives and needs no mapping. It does not need access to folders on the networked PC at all. I think you may be getting mixed up with something else altogether? If you have a problem with WideFS not connecting, show me the WideServer and WideClient logs. However, if your problem is related to FSCommander not being able to access files it needs in remote folders, I'm afraid this isn't related at all to WideFS and you need FSCommander support. Regards Pete
Pete Dowson Posted February 22, 2008 Report Posted February 22, 2008 May I ask where I find these? The WideClient log is where the WideClient program is. The WideServer log is where WideServer is (or FSUIPC4 if you are using FSX). Of course. Pete
timbar Posted February 25, 2008 Author Report Posted February 25, 2008 here are the logs. The network is working fine (Wireless) I have recently put FSX onto a new build with Vista 64 (server) and Vista 32 on client. Have allowed fsx through firewall. ********* FSUIPC4, Version 4.152 by Pete Dowson ********* User Name="tim lewis" User Addr="tlewis20@tiscali.co.uk" FSUIPC4 Key is provided WideFS7 Key is provided [Continuation log requested by user] Running inside FSX on Windows Vista (SimConnect SP1 May07) Module base=61000000 160089 System time = 15:52:03, FSX time = 15:50:10 (15:50Z) [Log closed by user request, and continued in new file] 997330 System time = 16:06:00, FSX time = 15:50:14 (15:50Z) 997330 *** FSUIPC log file being closed Memory managed: 151 Allocs, 150 Freed ********* FSUIPC Log file closed *********** ********* WideClient Log [version 6.72] Class=FS98MAIN ********* Date (dmy): 25/02/08, Time 15:43:17.877: Client name is TIMSLAPTOP 826 Attempting to connect now 1825 Trying to locate server: Need details from Server Broadcast 1825 Failed to connect: waiting to try again 3837 Attempting to connect now 68531 Trying to locate server: Need details from Server Broadcast
Pete Dowson Posted February 25, 2008 Report Posted February 25, 2008 here are the logs. Where is the WideServer log? ********* FSUIPC4, Version 4.152 by Pete Dowson ********* FSUIPC 4.152 is a long way out of date, and not supported. ********* WideClient Log [version 6.72] Class=FS98MAIN ********* Wideclient 6.72 is also very much out of date. Why not try to get everything up to date when you have problems? 1825 Trying to locate server: Need details from Server Broadcast 1825 Failed to connect: waiting to try again Your system is not supporting the broadcasting of data from the Server to the Client, so the client cannot automatically connect. You probably have the two PCs in different workgroups. If you've left Windows to name your workgroups for you that is almost inevitable when using different versions of Windows. Please see the user documentation which tells you what to do -- basically if you don't want to fix your PCs to be in a single workgroup, then you have to explicitly tell WideClient the name of the Server and the Protocol you want it to use. Regards Pete
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now