Client Widefs says connectded but SB3 can not see it

[tomcruse7]

I am running widefs6.5 and fsuipc 3.5. I am trying to run SB3 on the client PC. When its all connectded up wideFS is giveing a conccted message but when i try to start SB3 it says SB was unable to establish a connection with FS. Is it possoble for widefs to be giveing you a connectded message and other programs still not being able to see this connection? Seems like the problme im haveing in a nutshell...

[Pete Dowson]

... when i try to start SB3 it says SB was unable to establish a connection with FS. Is it possoble for widefs to be giveing you a connectded message and other programs still not being able to see this connection?

SB3 needs TWO completely separate connections to FS. One is to FSUIPC (optionally via WideFS). The other is through FS's own Multiplayer interface. Check the latter. I know nothing about Multiplayer and it isn't anything to do with FSUIPC or WideFS.

Regards,

Pete

[tomcruse7]

Well, the thing is it worked a few days ago then I was exchanging from FSUIPC 3.4 and 3.5 to try to get active sky to work. (there is a prob, there as well it will not work with my 3.5 reg.) and this is the point SB was not able to see the connection. SB is not the only program that can not see the connection on the client PC so this all ads up to make me thing its the widefs or fsuipc or combo of the 2

[Pete Dowson]

Well, the thing is it worked a few days ago then I was exchanging from FSUIPC 3.4 and 3.5 to try to get active sky to work. (there is a prob, there as well it will not work with my 3.5 reg.) and this is the point SB was not able to see the connection. SB is not the only program that can not see the connection on the client PC so this all ads up to make me thing its the widefs or fsuipc or combo of the 2

What do the WideFS logs say? (There will be a WideClient.Log and a WideServer.Log).

You say "will not work with my 3.5 reg", but there are no version-specific registrations. It actually sounds very much like you are using an invalid user Key for either or both of FSUIPC and WideFS. Delete your FSUIPC.KEY file and try again. If that makes everything work, you will need to send me all your details (not here -- I'll give you the email address then) so we can find out why your registration is wrong.

Regards,

Pete

[tomcruse7]

What do the WideFS logs say?

I can post them if you like?

You say "will not work with my 3.5 reg", but there are no version-specific registrations

I am saying Active sky will not work with the key file present. The AS tech support had me try moving out the key file which allowed AS to connect with FS.

Delete your FSUIPC.KEY file and try again

I have to have FSUIPC reg. for widefs to work correct?

Let me ask it this way.....is it possible....if wideFS on the client PC is showing a connected status for software on that pc to not be able to see the FS connection. I am talking more than just one program not being able to see the connection (ie not likely a problem with that one program)

[Pete Dowson]

I am saying Active sky will not work with the key file present. The AS tech support had me try moving out the key file which allowed AS to connect with FS.

That is a sure sign of a bad key. Where did you purchase your keys? I have no record of your current email address -- is the one you are using here different?

Let me ask it this way.....is it possible....if wideFS on the client PC is showing a connected status for software on that pc to not be able to see the FS connection. I am talking more than just one program not being able to see the connection (ie not likely a problem with that one program)

The only explanation which fits everything you are seeing is that you have somehow acquired a bad (possibly illegally generated) Key, either for FSUIPC or for WideFS, or for both. If you would like to ZIP up your KEY file along with the receipts from SimMarket or wherever, or at least the name and email with which you registered, then I can try to resolve your problem. Make sure you ZIP things and send to petedowson@btconnect.com.

Regards,

Pete