Premise Builder can't see the server

[TheLightKeeper]

I have used Premise Systems for over 5 years. I just purchased a new house and installed Premise on a new computer, new operating system and the house has a new local network all hard wired. My builder program can not see the Premise server on the network.

Premise server:
P3, 1G, 1G memory, running XP Professional, SP2 with all the latest updates. I do not install builder on to the server computer. No anti virus programs running. (the old system ran the server under W2K.)

Premise Builder:
P4, 1.3G, 2G memory, running XP Media Center Edition, SP2 with all the latest updates. (the older system ran under W2K)

My builder program can not see Premise server on the local network. I know it is a simple network problem or some of the newer security systems in XP are preventing builder from seeing the server.

I have turned off firewalls, security settings and nothing. Any ideas?

Thanks,

Matt

 

[BraveSirRobbin]

I don't use Premise, but on the belief that this is a simple network problem you may want to list the IP addresses as well as Gateway and Subnet settings for both machines. Then maybe our network expert members can provide some suggestions.

 

[123]

After you've confirmed that basic networking is functional (i.e. you can ping the Premise server PC from the Premise Builder PC) ensure that Windows Firewall, on both PCs, permits the Universal Plug and Play (uPnP) protocol.

When you start Builder, the first dialog box, "Connect to Premise Home Control Server", shows all Premise servers on the network. Builder performs this discovery using the uPnP protocol.

 

[TheLightKeeper]

The server is 192.168.254.1 / 255.255.255.0 (fixed IP address)
Builder is 192.168.254.68 / 255.255.255.0 (DHCP)
Gateway 192.168.254.200 / 255.255.255.0
Workgroup is same for both computers.

 

[TheLightKeeper]

123

I see nothing in the "Connect to Premise Home Control Server". I am able to ping the server. I need to look into the UPNP settings. If I can find them.

Thanks,

Matt

 

[123]

Full discussion of Windows XP SP2 and UPnP here.

To check if it is permitted by your PC's firewall:
Start > Control Panel > Windows Firewall.
Click the Exceptions tab. It should list "UPnP Framework".

If it is not in the list, you can add the two required ports manually. You'll need one for TCP on port 2869 and another for UDP on port 1900.

 

[samgreco]

Mine does this too. Don't know why, but to connect click on the Internet tab then Add Site. Manually add your server, with it's IP address and connect that way.

Works great for me.

 

[TheLightKeeper]

Thanks for all the suggestions and I have tried all of them without any success. I have UPnP up and running on both the server and builder programs. All the ports are checked under the UPnP Framework.

I tried using the Internet tab in builder with my IP address (192.168.254.1 and also http://192.168.254.1). I still can not log on to the server. When I have builder on the same computer as the server, I have no problems. I can also access the server from any other computer using the GUI web pages to run things but not to configure things.

Thanks,

Matt

 

[123]

Connection via Add Site *should* work. Temporarily disable Windows Firewall on both machines and try to connect via Add Site. If it works, re-enable Windows Firewall and ensure port 3977 is open (used by Builder).

If it doesn't work ... I'm not sure what's blocking it. What is the version of Premise you are using? 2.1?

 

[TheLightKeeper]

ver 2.1 Build 15117, the last published update.

 

[georgejm]

Mine does this too. Don't know why, but to connect click on the Internet tab then Add Site. Manually add your server, with it's IP address and connect that way.

Works great for me.

Sam,

I saw this too (and I think I documented it in the old forum). I used Ethereal to sniff packets on my LAN and discovered that my NETGEAR router (provided with my FIOS service) responds to the Builder's UPnP discover device broadcast with a "network unavailable" message. Not sure who isn't implementing the UPnP protocol correctly, but the combination of Premise and NETGEAR fails. I've used DLINK and it works fine, but it has issues with FIOS. Like you, I ended up using the Internet tab as a workaround.


Matthew,

As an experiment, try disconnecting your Cable/DSL router. Let's see if you are having a protocol-related problem.

-John

 

[samgreco]

Funny - I have a D-Link router and I still don't see the standard UPnP discovery. Strange. But again, for me, using the internet connection method always works.

 

[Nugget]

I apologize for bringing up an old thread, but I'm having this same issue while trying to get Premise up and working for the first time. I've installed builder and server on my home server (Windows Home Server 2011), builder only on my PC (Windows 7), and verified that the two SYS services are running on the server. Builder works on the server, but on the PC, the Premise server isn't being detected by builder, though I can connect using IE / Automation Browser.

I've added firewall exceptions for ports 86 and 3977 on both sides, as well as verified the exception for UPnP on the home server and PC firewalls. Is it possible that my wireless router is interfering in some way? I've had difficulty setting up port forwarding with this router (Asus RT-n56u), and am wondering if this is related. Any suggestions would be much appreciated!

 

[Nugget]

Well, the old truism holds, and as soon as I posted this, I was able to get it working by adding a firewall exception on a program basis. Now it's off to get my Zwave network set up - I'm sure I'll have other questions, so thanks in advance!

 

[samgreco]

Try using the internet tab on the connect box and add the server by IP address and see if that works.