Sage 100

Moving MAS 200 4.4 to new Windows 2008 R2 server - installer (run as Administrator) says that TCP/IP must be set up, but it quite obviously is as I am connected remotely. Any ideas? I have never seen this message before.

Can i tbe pinged by IP and/or name?

Check the protocol. WOuld be strange, but they could be using anothher network protocol which would allow you to connect.

ipconfig /all shows typical results

ping from another machine works...Sage support suggests rebooting

reboot did not help

windows firewall is off

I have also seen where the TCP/IP stack is correct. There are utilities that fix this. Our techs typically jump in at this point so I do not have any utility at my finger tips but it is something you might try to google. IP Stack not binding sounds kind a familiar..... I got lost in the thread. Can you ping the server from the workstation?

Can ping from another computer

Can you ping from the server the workstation?

Now Sage is wasting more time saying ""try it from the console session"" and refusing to look up the code that generates that error and seeing what it is actually checking for...

can ping in both directions, can download files from the internet, can copy files from the old server

I'm not sure it's really necessary or related in any way to this error but I always do the install from a console logon with Mstsc /v:{server name} /admin

Turn off Antivirus programs

no av installed yet and in the console session

Did you ping in both directions by both name and IP Address?

Bleeping IT fools: ""Think I may have found the answer in a software restriction policy. Give me a minute to disable and force a policy refresh."" Thanks everyone!