jefmo Posted January 24, 2005 Share Posted January 24, 2005 When i try to log on from a network computer I get this message. NETWORKING STACK COULD NOT BE INITIALIZED IN FILEMAKER. HELP! Sharing is allowed, I have tried disableing firewalls.. Link to comment Share on other sites More sharing options...
transpower Posted January 24, 2005 Share Posted January 24, 2005 Don't use Windows sharing for the FM files. Link to comment Share on other sites More sharing options...
jefmo Posted January 24, 2005 Author Share Posted January 24, 2005 Can you explain that? What do you mean by "windows sharing"? Link to comment Share on other sites More sharing options...
Lee Smith Posted January 24, 2005 Share Posted January 24, 2005 I think he is trying to say. Don't use the Operating Systems to share your files, instead use FileMaker File Sharing instead. It's available under the "File" menu in FileMaker. HTH Lee Link to comment Share on other sites More sharing options...
jefmo Posted January 24, 2005 Author Share Posted January 24, 2005 I think your referring to edit/sharing/filmaker network? I have that as "on". i don't see anything under the "file" menu relating to file sharing.. Link to comment Share on other sites More sharing options...
Newbies persistentfool Posted January 28, 2005 Newbies Share Posted January 28, 2005 I ran into the exact same problem and after trying several things I finally found another article on the Microsoft Knowledgebase that worked: From Microsoft Support database article #811259: http://support.microsoft.com/kb/811259#kb3 How to Recover from Winsock2 corruption To resolve this issue, delete the corrupted registry keys, and then reinstall the TCP/IP protocol. Step 1: Delete the corrupted registry keys 1. Click Start, and then click Run. 2. In the Open box, type regedit, and then click OK. 3. In Registry Editor, locate the following keys, right-click each key, and then click Delete: HKEY_LOCAL_MACHINESystemCurrentControlSetServicesWinsock HKEY_LOCAL_MACHINESystemCurrentControlSetServicesWinsock2 4. When you are prompted to confirm the deletion, click Yes. Note Restart the computer after you delete the Winsock keys. Doing so causes the Windows XP operating system to create new shell entries for those two keys. If you do not restart the computer after you delete the Winsock keys, the next step does not work correctly. Step 2: Install TCP/IP 1. Right-click the network connection, and then click Properties. 2. Click Install. 3. Click Protocol, and then click Add. 4. Click Have Disk. 5. Type C:Windowsinf, and then click OK. 6. On the list of available protocols, click Internet Protocol (TCP/IP), and then click OK. 7. Restart the computer. Link to comment Share on other sites More sharing options...
jefmo Posted February 3, 2005 Author Share Posted February 3, 2005 the odd thing is that it happens on all computers. I even tried it in a different office on a different netwwork and I get the same message. "network stack could not be initialized in filemaker" crazy Link to comment Share on other sites More sharing options...
DykstrL Posted February 3, 2005 Share Posted February 3, 2005 The procedures that persistentfool gives is reinstalling the IP stack, which it sounds like what you may have is a corrupt IP stack. If it is happening on all of your computers, a corrupt IP stack on a DNS server or a router gone bad could cause an IP stack on connected boxes to become corrupt. Link to comment Share on other sites More sharing options...
jefmo Posted February 7, 2005 Author Share Posted February 7, 2005 It is happening on all my computers and I just installed a new Router. Any other thoughts? Link to comment Share on other sites More sharing options...
Recommended Posts
This topic is 7010 days old. Please don't post here. Open a new topic instead.
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