Jump to content
The simFlight Network Forums

Recommended Posts

Posted

hi

I have the following problem:

I use Istation in a remote laptop with Widefs without any problem.

now i changed the laptop for a better one and i´m not able to make it conect with the server computer.

The configuration in the server is ok, because if I conect the old computer it works perfect.

the new laptop has a Lan conection that works because this new laptop conects with the server computer with wire and run Prosim displays without any problem. prosim does not need wide fs to connect

when i try to run Instructor station, it does not cocnect with wideFS.

I had reinstalled Microsoft framework3.5 and the SP1 and not working

i copy and paste to you the wideclient log

********* WideClient Log [version 6.78] Class=FS98MAIN *********

Date (dmy): 04/04/11, Time 00:09:48.625: Client name is HP-607D24540DA9

187 Attempting to connect now

1187 Trying to locate server: Need details from Server Broadcast

1187 Failed to connect: waiting to try again

3187 Attempting to connect now

8984 New Client Application: "istation" (Id=2156)

67187 Trying to locate server: Need details from Server Broadcast

129562 ****** End of session performance summary ******

129562 Total time connected = 0 seconds

129562 Reception maximum: 0 frames/sec, 0 bytes/sec

129562 Transmission maximum: 0 frames/sec, 0 bytes/sec

129562 Max receive buffer = 0, Max send depth = 0, Send frames lost = 0

129562 **************** Individual client application activity ****************

129562 Client 2156 requests: 15 (Ave 15/sec), Data: 600 bytes (600/sec), Average 40 bytes/Process

129562 ********* Log file closed (Buffers: MaxUsed 1, Alloc 15 Freed 15 Refused 0) *********

any idea?

Thanks a lot

Miguel

Posted

1187 Trying to locate server: Need details from Server Broadcast

1187 Failed to connect: waiting to try again

The client PC is not receiving broadcasts from the Server, so it cannot identify that Server. This almost always means that your two PCs are in different workgroups. If you've never changed the workgroup names it is important to note that Vista and Win7 use a different default workgroup name to XP.

Please check the Installation section of the WideFS User Guide, and in particular the part headed:

Configure your Network

IT IS IMPORTANT FOR ALL USERS TO READ AT LEAST PART OF THIS!

Pete

Posted

hi Pete

my serverIPadress is 192.168.1.15

how can i know he servername?

so what i have to do is:

[Config]

Port=8002

Window=43,44,886,589

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

ServerName=????????????????????? (how do i know the name of the server?

Protocol=TCP

ServerIPAddr=192.168.1.15

is thbis correct?

thanks a lot

quote name='Pete Dowson' timestamp='1301871121' post='425215']

The client PC is not receiving broadcasts from the Server, so it cannot identify that Server. This almost always means that your two PCs are in different workgroups. If you've never changed the workgroup names it is important to note that Vista and Win7 use a different default workgroup name to XP.

Please check the Installation section of the WideFS User Guide, and in particular the part headed:

Configure your Network

IT IS IMPORTANT FOR ALL USERS TO READ AT LEAST PART OF THIS!

Pete

Posted

my serverIPadress is 192.168.1.15

More important in this case is the Workgroup -- if you make sure all your computers are in the same workgroup you should have no problem in any case.

how can i know he servername?

It is the name of your computer, as shown in WindowsExplorer from the other PC, or in the Properties of "My Computer" -- right click on "My Computer", select Properties, then, on WinXP, Computer Name. There you will see your computer name AND your workgroup name. And you can change either using the Change button. On Vista and Win7 you right click "Computer" and select properties, and the details are shown where it says "computer name ...", and you can change them by using the Change Settings button.

so what i have to do is:

ServerName=????????????????????? (how do i know the name of the server?

Protocol=TCP

ServerIPAddr=192.168.1.15

is thbis correct?

More or less. You don't need both "ServerName" and "ServerIPAddr". If you give the IPAddr the Name is ignored. I still think your first step should be to try to put both PCs in the same workgroup.

Pete

Posted

Hi pete

So, i have to see the name of workgropu that has the seerver computer and then change the workgroup in tha client computer setting exactly the same name.

is this correct?

so, the wideclient.ini must be like this:

[Config]

Port=8002

Window=43,44,886,589

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

Protocol=TCP

ServerIPAddr=192.168.1.15

is ok?

Miguel

Posted

So, i have to see the name of workgropu that has the seerver computer and then change the workgroup in tha client computer setting exactly the same name.

is this correct?

Yes. If both PCs are in the same workgroup you only have one workgroup so broadcasts will work between them.

so, the wideclient.ini must be like this:

If both PCs are in the same workgroup you shouldn't need to make any changes to any files. The default Wideclient.ini should work. You can do both but it is overkill.

Regards

Pete

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.