After going through the headache of getting FLServer to work in Windows 7, I thought I'd share it here. No sense in anyone else having the headache.
Normally, when you run FLServer in 7, then try to connect to it in FL, you see some odd hexadecimal numbers where the IP address should be, and you're unable to connect. The cause of the problem is IPv6 (apparently the new IP standard that nobody's using yet).
The first thing to try is disabling IPv6 in the network connection properties doesn't work. Open your start menu, right-click on Network, and select properties. In the window that opens, click on 'Change adapter settings' at the top-left. In there, you'll see your internet connection. Maybe more than one. Right-click on each one, and go into properties. Clear the IPv6 check box on all of them. It should look something like the image below. If it works for you, then you're gold, and can skip the rest of this.
Now, if like me, your problem persisted, you need to dig a bit deeper. Go to the start menu, click run, and type in 'regedit'. This will open the Registry Editor. Be careful when editing the registry, as you can do some serious damage if you're not careful. You won't be doing anything dangerous or risky here, though. Just follow my instructions and you'll be fine*. In the left pane, you'll see a series of folders, much like Windows explorer. Browse to 'Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TCPIP6\Parameters'. In there, you'll see two entries. Leave those alone. Right-click anywhere in the empty space in the right pane, and under 'New', click on 'DWORD (32-Bit) Value'. Name it 'DisabledComponents' and enter 'ffffffff' for the value. It should look like the image below. Click on the image for a larger version.
This completely disables IPv6, and should solve your FLServer problem. If you should ever need to turn IPv6 on again (such as in the event that people actually begin using it), then just change the 'DisabledComponents' registry value to '0'.
*Any edits to the registry are done at your own risk, and despite any promises, Captain Morgan can not be held liable for any bugs, crashes, or spontaneous hard drive combustions that may occur.
Indeed. From the looks of that thread, it got as far as the control panel. The link that was posted said how to do it in Windows Server 2008, but that procedure looked slightly different than the one in Windows 7.
That thread is a good addition, but I still think my post on the subject is plenty helpful enough to warrant posting.
' Wrote:Indeed. From the looks of that thread, it got as far as the control panel. The link that was posted said how to do it in Windows Server 2008, but that procedure looked slightly different than the one in Windows 7.
That thread is a good addition, but I still think my post on the subject is plenty helpful enough to warrant posting.
That procedure is working and thats the point:)I just wanted to inform you that there is another way we have been already talking about. No more, no less. This is not critic or offensive post :D
The value 'ffffffff' didn't work for me. But I set just 'ff' instead and worked. This one just disables IPv6 for the Windows Server 2008. This means that the servers you host will have IPv6 disabled, but not the rest of the stuff (clients, other apps, etc...)
I have been fighting with FLserver for couple of days. I am running Win7. I have a small home wireless network with a linksys router, the other station on the network is an XP machine.
Problem:
When I run FLserver on the WIN7 machine and try to log on from the Win7 station I see the server but the IP address appears to be the mess with IPV6.
2nd Problem
When I get the list of servers on the XP station I do not even see the server running on the Win7 machine.
What I have tried
I have followed the steps here to disable IPV6 both in the network properties and via both of the registry edits I have seen here. I have made sure that I am running FLserver in XP service pack 2 compatiblity and am running as Administrator. This has not worked. I still see the IPv6 address in the server list on the Win 7 station, and I still do not see the server on the XP machine at all. I have also disabled my firewall on the Win7 machine, which feels real creepy. I have double checked and I have installed the 1.1 patch. I am also running Cisco's "Network Magic" network managing system on both stations.
What has worked
I can run the Server on the XP Machine and both systems can see the server and log on fine. However, there was some jumpiness and lag and I thought running on Win7 would be a better setup. But so far no go.
This is no longer valid and needs to be removed before someone destroys their network like I did. IPv6 is now required for internet access for Windows 7 SP1. I am experienced with disabling IPv6 in the past, I did this myself, skipping the part where I needed to add a registry value, and FLServer started working, but the rest of my internet cut out and my PC only had limited connectivity to my router, I had to literally go restart my router and restore IPv6 on my PC to get internet back and now if I even attempt to run FLServer.exe even with IPv6 enabled, my connection gets disabled and I need to restart the router again. My ISP said that now Windows 7 is required to keep IPv6 on.
Posts: 3,665
Threads: 143
Joined: Aug 2009
Staff roles: Server Manager Coding Dev Moderator
' Wrote:This is no longer valid and needs to be removed before someone destroys their network like I did. IPv6 is now required for internet access for Windows 7 SP1. I am experienced with disabling IPv6 in the past, I did this myself, skipping the part where I needed to add a registry value, and FLServer started working, but the rest of my internet cut out and my PC only had limited connectivity to my router, I had to literally go restart my router and restore IPv6 on my PC to get internet back and now if I even attempt to run FLServer.exe even with IPv6 enabled, my connection gets disabled and I need to restart the router again. My ISP said that now Windows 7 is required to keep IPv6 on.
This is valid. It will not destroy your network if it's set up properly. No. Who is your ISP and why do they not allow you to use IPv4 internally?
' Wrote:This is valid. It will not destroy your network if it's set up properly. No. Who is your ISP and why do they not allow you to use IPv4 internally?
It's not my ISP's fault my PC could no longer connect to my belkin router with IPv6 disabled. My connection doesn't even have IPv6 connected, but if I disable it, my connection breaks. Windows 7 REQUIRS IPv6, as told to me by an ISP and a programmer. Windows 7 Ultimate 32 bit Service Pack 1.
Posts: 3,665
Threads: 143
Joined: Aug 2009
Staff roles: Server Manager Coding Dev Moderator
' Wrote:Windows 7 REQUIRS IPv6, as told to me by an ISP and a programmer. Windows 7 Ultimate 32 bit Service Pack 1.
No. I have followed the instructions in this thread to disable IPv6 in my Windows 7 Ultimate 64-bit Service Pack 1 VM. The connection still works perfectly.