hupeter Posted December 27, 2009 Report Posted December 27, 2009 Hi, I had to reinstall FSX with Windows 7. I cannot register FSUIPC4 and Wide FS. Need some help. The FSX is running with an external hard disk. Hope you can help me. Peter
JSkorna Posted December 27, 2009 Report Posted December 27, 2009 Hi, What is the message that you get?
hupeter Posted January 3, 2010 Author Report Posted January 3, 2010 Hi, still Problem with Wide FS. More detailed: I run FSX with Windows 7 (FSX is on an external HD. When I start FSX I get the message that FSUIPC and Wide FS are registered to my name. The message in FSX is: MS FSX with WideServer : waiting for clients. On the other computer running with Windows XP I see the message: WideClient FS98 Eliminator - waiting for a connection. Nothing more happens. I need some help to find a solution. I think there is a problem at the connection between the computer running FSX and the client. PETER
Pete Dowson Posted January 3, 2010 Report Posted January 3, 2010 The message in FSX is: MS FSX with WideServer : waiting for clients. On the other computer running with Windows XP I see the message: WideClient FS98 Eliminator - waiting for a connection. They are not seeing each other, then. Did you check and make sure that both computers are in the same Workgroup? Or if you prefer to have them in a separate workgroup, did you tell WideClient the name of the Server and the Protocol you want to use? This elementary part of the setup is described at the beginning of the section in the WideFS User Guide entitled thus: Configure your Network IT IS IMPORTANT FOR ALL USERS TO READ AT LEAST PART OF THIS! If you've checked that or attended to it and it still fails to connect, it may simply be the firewall at one end or the other. If you've disabled that or attended to it to allow FS and WideClient through, please show me the WideServer.log file from the FS Modules folder, and the WideClient.log file from the client folder. These might show the details of the problem. Pete
hupeter Posted January 4, 2010 Author Report Posted January 4, 2010 Hi Pete, in Windows 7 I have a Homegroup. This is so configured that I can access from the client computer all files included the external HD where FSX is running on the Server. The name of this computer is Peter-PC (Server) The Wide Client Configuration Settings is as follows now: [Config] ServerName=PETER-PC Protocol=TCP Port=8002 Window=4,4,1032,776 Visible=Yes ButtonScanInterval=20 ClassInstance=0 NetworkTiming=5,1 MailslotTiming=2000,1000 PollInterval=2000 Port2=9002 ResponseTime=18 ApplicationDelay=0 TCPcoalesce=No WaitForNewData=500 MaxSendQ=100 OnMaxSendQ=Log NewSendScanTime=50 Priority=3,1,2 Once more detailed: On the client computer which is running Windows XP I open My Network Places, Entire Network, Microsoft Windows Network: then I see MShome and Workgroup. Under Workgroup I can find my new computer running Windows 7 with his name Peter-PC. I open Peter-PC and have access to the printers, to the external HD, where FSX is located. In the Modules folder I find 2 Textdocuments: WideServer and WideServer0. ********* WideServer.DLL Log [version 7.53] ********* Blocksize guide = 4096 (double allowed) Date (dmy): 04/01/10, Time 18:05:42.969: Server name is PETER-PC 15709 Initialising TCP/IP server 15709 Initialising IPX/SPX server 15709 IPX/SPX socket() failed [Error=10047] Address family not supported by protocol family 15709 Failed to start IPX/SPX Server 15709 Initialising UDP/IP server 16162 Broadcasting service every 1000 mSecs and ********* WideServer.DLL Log [version 7.53] ********* Blocksize guide = 4096 (double allowed) Date (dmy): 03/01/10, Time 22:32:19.837: Server name is PETER-PC 15881 Initialising TCP/IP server 15881 Initialising IPX/SPX server 15881 IPX/SPX socket() failed [Error=10047] Address family not supported by protocol family 15881 Failed to start IPX/SPX Server 15881 Initialising UDP/IP server 16130 Broadcasting service every 1000 mSecs So I hope this information is enough for you to bring WideFS to running. Thanks for your help. Peter
Pete Dowson Posted January 4, 2010 Report Posted January 4, 2010 The Wide Client Configuration Settings is as follows now: [Config] ServerName=PETER-PC Protocol=TCP Okay. Those lines shouldn't really be needed if both PCs are in the same workgroup, but that is more difficult I think if you use Win7's new Homegroup mechanism which is only designed for Networks in which all PCs are using Win7. On the client computer which is running Windows XP I open My Network Places, Entire Network, Microsoft Windows Network: then I see MShome and Workgroup. Under Workgroup I can find my new computer running Windows 7 with his name Peter-PC. I open Peter-PC and have access to the printers, to the external HD, where FSX is located. In the Modules folder I find 2 Textdocuments: WideServer and WideServer0. They are Log files. The one with 0 on the end is the previous one, the one without is the current one. You have Explorer defaulted to hide file types from you where it thinks it knows what they mean. You can change that in the folder options in explorer. The names "workgroup" and "mshome" are presumably different workgroup names? You could change them to be the same on both PCs in Computer Properties. However, that shouldn't be needed now as you have the correct parameters added to the WideClient INI file. So I hope this information is enough for you to bring WideFS to running. You have not said anything yet about it not running since you changed the INI file!. What are the symptoms? The same as before? The WideServer logs you are showing are incomplete -- FSX was not closed first -- but they show nothing being received from the Client. Did you run WideClient? If so, where is its Log, which would show whatever problems it is having? You only show part of the story and don't tell me what is wrong. Have you allowed access through the firewall, or disabled it? Regards Pete
hupeter Posted January 5, 2010 Author Report Posted January 5, 2010 Hi Pete, sorry I have not much experience here. Since I have changed the INI File everything was same. ********* WideClient Log [version 6.75] Class=FS98MAIN ********* Date (dmy): 05/01/10, Time 23:06:33.359: Client name is ACER2 219 Attempting to connect now 250 Trying TCP/IP host "PETER-PC" port 8002 ... 250Okay, IP Address = 192.168.1.3 1157 Error on client pre-Connection Select() [Error=10061] Connection refused 1157 Ready to try connection again 2204 Attempting to connect now 6407 ****** End of session performance summary ****** 6407 Total time connected = 0 seconds 6407 Reception maximum: 0 frames/sec, 0 bytes/sec 6407 Transmission maximum: 0 frames/sec, 0 bytes/sec 6407 Max receive buffer = 0, Max send depth = 0, Send frames lost = 0 6407 ********* Log file closed (Buffers: MaxUsed 0, Alloc 0 Freed 0 Refused 0) ********* [Config] ServerName=PETER-PC Protocol=TCP Port=8002 Window=4,4,1032,776 Visible=Yes ButtonScanInterval=20 ClassInstance=0 NetworkTiming=5,1 MailslotTiming=2000,1000 PollInterval=2000 Port2=9002 ResponseTime=18 ApplicationDelay=0 TCPcoalesce=No WaitForNewData=500 MaxSendQ=100 OnMaxSendQ=Log NewSendScanTime=50 Priority=3,1,2 Firewall is deactivated. Regards Peter
Pete Dowson Posted January 5, 2010 Report Posted January 5, 2010 250 Trying TCP/IP host "PETER-PC" port 8002 ... 250Okay, IP Address = 192.168.1.3 1157 Error on client pre-Connection Select() [Error=10061] Connection refused ... Firewall is deactivated. It doesn't appear to be deactivated on at least one of the PCs -- the client evidently knows the Server, and WideClient tries to connect but it is being refused. Whether it isn't being let out of the client PC or not let into the FS (server) PC I cannot tell, but it is being blocked for sure. The error is from Windows telling WideClient it isn't allowed to connect. Regards Pete
hupeter Posted January 7, 2010 Author Report Posted January 7, 2010 Hi Pete, thanks for reply. So I don't know how to use Wide FS. Do you think it will bring a solution if I run Windows 7 on both computers? Regards. Peter
Pete Dowson Posted January 7, 2010 Report Posted January 7, 2010 So I don't know how to use Wide FS. There's nothing really to know about using WideFS. That isn't where there's a problem. The problem is you don't have a link between the two PCs which it can use. The pre-requisite for any networked application is a working and usable Network. I'm afraid that isn't something I can easily advise you on from here. Whenever I've had Networking problems I've only ever solved them by trial and error. Windows is not very helpful in this regard. If it says "connection refused" it simply means it isn't allowing WideClient to get any message through to the Server. "Why?" is another matter -- firewalls and other security measures are the most obvious culprit. Do you think it will bring a solution if I run Windows 7 on both computers? I don't know. It may do or it may just make matters worse. If you don't know how to allow programs through your firewalls, or how to disable them altogether, then perhaps you can get help with that, first? Seems less drastic to try and find the cause of the block, and fix that, first. If, in the Windows 7 side, you've used that new-fangled networking mechanism called "HomeGroup", then you should be aware that, as it clearly says, that only operates between Windows 7 PCs. Is this perhaps the problem? If so, then there would appear to be two ways to move forward: Either (1) disable the HomeGroup altogether and use the normal compatible networking facilities as on WinXP and Vista, or (2) Yes, use Win7 on all PCs and only use the HomeGroup system. Please note that in my house we have a Network of some 12 PCs and two Notebooks, and of these only 3 so far are using Windows 7. I avoided HomeGroup entirely, simply because it did say explicitly that it is only for connections to other Windows 7 PCs. So at present I cannot really advise on HomeGroup networking at all. I shouldn't think I'll ever get to the point where all of the PCs here will be running Win7, but you never know ... Regards Pete
hupeter Posted January 14, 2010 Author Report Posted January 14, 2010 Hi Pete, thanks for your help. I will try it with both computers running Windows 7 and if I have a result I will send a report to you. Regards Peter
hupeter Posted January 21, 2010 Author Report Posted January 21, 2010 Hi Pete, it was successful. Both Computers run W7 now. And WideFS is running properly. The most important was to install the network correct. Thanks for your help. Regards. Peter
ArnyLitheman Posted March 31, 2010 Report Posted March 31, 2010 I just had the same with my new FSX-PC (Win7) and its client (still running XP). Bought FSUIPC4 and WideFS7 today new, no connection, whatever I tried... I renamed the whole workgroup, ran the diagnostics, released folders with any properties and everything. I read the WideFS-Manual over and over and almost got nuts about it, because the network itself worked and I could see any PC and read and write in any every released folder. Just the same error in the log like above by trying to connect my FSX with the client via WideFS. My last idea was to set the servername and protocol in the [config] section of the .ini...nothing. And now in the middle of the night (I hate unsolved problems and can't let it go, whatever it will cost) I won the war against my network...I had to change the servername with its IP-adress 192.168.x.x FSX with WideServer: 1 connected :D :D :D Obviously there's any translation-mistake in the router the reason for that strange behavior...just keep in mind if that happens to the next one!
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