x Want to participate? Join the group to interact
Options
  • State Verified Answer
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 1 subscriber
  • Views 87 views
  • Users 0 members are here
Browse Forums
Announcements
32
topics
2
replies
General Discussion
856
topics
2k
replies
seawardcecil

Unable to connect to database on a Windows 10 2004 fresh client

SOLVED
Posted By

Edit FIXED - see edit below

OK, so FAS 2020.1 Network Depreciation - User's current workstation works fine (she is currently on 1903), as do two others (also on 1903) - so I know that permissions are set correctly on server for the user in question.

I am getting ready her new machine, which is loaded with Windows 10 2004.  After installing the client FAS will not connect to the database on this one.  Tried manually typing the ip address of the server.  No dice, tried manually opening up the port in firewall Inbound/Outbound.

Just to be sure, tried a client install on my admin box(loaded with 1909), no problem.

Is there something about 2004 that needs to be done to make this work?  Tried all the troubleshooting steps in the knowledgebase for it - it's pretty tough to google with the terms "Windows 2004" (can't wait until 2103 and 2109)

.NET 3.5 is already installed in case that mattered (Sage 300 CRE did that), and something turned on SMB 1.0 already in case that did too.

Thanks.

Edit:  Nevermind, I must have been having a bad day yesterday and missed a key bit on the knowledgebase - "Replace the Xs with the IP of the server"  I had nuked the whole {HOST=XXX.XXX.XXX.XXX} and replaced it with the IP.

So, instead of 10.9.1.12 it should have been {HOST=10.9.1.12} - I had plenty of coffee yesterday, but I just have to say, this year's flu vaccine has beat me over the head.  I mean, I remember having to do this.. oh well.

  • 0
    SUGGESTED

    Hello seawardcecil,

    Funny, you should ask this, I too just had one of my test machines for the new product release which did something very similar when a surprise windows update to the version 2004 went through and I had some difficulty afterwards, but then I figured out the update turned the Firewall on and after turning off the firewall, the Network product worked without any issues which I just figured out when I read this. 

    I just finish turning the firewall back on and poking the holes needed for Port 2638 inbound and outbound, and it is still working. As near as I can tell at this point there is nothing new in Windows 10 Version 2004 except for the Firewall.

    ~Delray

  • 0

    Yep, tried ditching the firewall all together after punching hole in it didn't work.  Still a no go.  I'll have to see if there are any relevant logs/events

  • 0
    verified answer

    Nevermind, I must have been having a bad day yesterday and missed a key bit on the knowledgebase - "Replace the Xs with the IP of the server"  I had nuked the whole {HOST=XXX.XXX.XXX.XXX} and replaced it with the IP.

*Community Hub is the new name for Sage City