http://i.imagebanana.com/img/jwxkgjo7/wrong.JPG
Printable View
I currently have a similar problem:
Attachment 126944
Attachment 126945
any ideas on how to solve this problem? the configs are all right im using them on my test server vps and its working fine but on a dedicated root it seems like it doesnt connect right or cannot be certified or sth like that but its running fine as you can see in the picture without any errors being trown ... im using br files gateway together with vsro files btw
Gateway is not "bind" to a ip with some srpatchs? maybe that is your problema, check if Gateway connects on your actual ip
and how would i do that?
To check if the gateway is connected to your actual I.P. address go to CMD and type in netstat -b and it will print out a log of all the programs running(i.e. msnmsger.exe), it will show what I.P. address and port the program is using to connect to.
the gateway server is using a lot of ports but on the important port (15779) its connected to IP 0.0.0.0 ... on my test server i have the same but also another connection to the right ip look at this:
Root Server:
Attachment 126981
VPS Test Server:
Attachment 126982
anyone knows how to make it connect to the right ip again or why its not connecting to the ip?
as i said already the configurations (server.cfg and cert inis) are same on the root and vps test server except the ips and database instance name (in cert inis)
//edit:
tested it again and it connected to the right ip this time but its still not working <.<
P.S. Your inbox is full Lemon.
Try using VMWare if not already..for the virtual server.
Give your virtual server the MAC address of the dedicated server.
Use two separate I.P. addresses(sub-netting)
i think you got me wrong, the VPS test server is NOT on the dedicated root
its on another machine and got its own ip adress
can you post your certification configuration here so we know what's your issue?
the certification configuration is good i know that for sure because its working on another server (with different ips and mssql server name) any other ideas? could this be because its running on windows server 2012?
sorry for guessing, but i have not run into this issue before, but I can guess the possible issue; could be PrivilegedIP on sql table. If not that then I have no clue.
even if priv.IP is empty it doesnt work already tried that but thanks anyways, any other ideas?
