Premise Premise Server

[nov0798]

OK,
I am having a problem connecting to my Premise server, from a laptop. I have trid typing in the IP address of the server, I have tried the machine name. I had this problem once before, but was able to connect using the machine name. Also, the server does not show up in the local network list when connecting, even though it is sitting on my local network. Does anyone have any ideas?

Thanks

 

[samgreco]

For some reason I have never been able to connect from the "Local Network" tab on my network. From "The Internet" tab, add a site and use the IP address. That should work. But if not, check your firewalls. I needed to add an exception for Premise on both ends to let it through, as I recall.

 

[nov0798]

Yes, I have tried the internet tab also, NO LUCK!

 

[chucklyons]

Yes, I have tried the internet tab also, NO LUCK!

Do you have port 3977 open on your laptop firewall? On your router? I am going to assume you can get to it from your local machine? (the one that has Premise on it)

You might want to hit 123's Premise forums....(I don't remember the url, and I may/may not have my own local version). If I recall, someone else had the same problem back in the day....

 

[samgreco]

Firewall?

I think that Premise defaults to Internet authenticate, but you can check it in the Builder on the server (since you can't get to it from your laptop) under WebServer>Sites>Default Web Site>Authenticate and check the same setting under Secure Web Site.

I expect that both settings will be correct, but it's worth a look.

But even if you think that the firewalls are OK, try turning them both off temporarily and see what happens.

EDIT: I was typing as Chuck answered, but the firewall seems to be the consensus

 

[nov0798]

YES, it was the firewall. I created a rule that allowed it , and presto. Now if I can just get the dyn dns service to let me in.

 

[samgreco]

If you mean getting in from the outside world using a DynDNS address, you probably need to poke a whole thru the firwall on your router. Depending on your modem, you may need to open that up too. Be careful what you open up there though. Others can find holes too

 

[nov0798]

Yea I opened it up through the router but still no go?? I need someone who knows routers to fill me in on how to keep it safe.

 

[chucklyons]

On the machine that you have Premise installed on - go to the Microsoft Firewall under Control Panel - turn it off. Fire up Premise. You should see 'Local Computer'. If you have a separate pc, do the same, launch builder, and you should be able to access it from the Internet 'add a site'. If not, PM me, and I'll see if I can hit it from my Builder.

 

[123]

If you want to access your Premise Server using Premise Browser from the Internet, you'll need to open port 80 on your router and have it directed to the Premise Server PC. Be aware that your ISP may block port 80 (mine does). In this case, you'll have to force Premise to use port 86. I don't recommend either of these ports because the protocol is http and not secure.

A better option is to open port 443 which is https. You'll need to create a self-certified certificate for Premise's web server (the instructions are documented in Premise Help). Configure your router to direct port 443 to your Premise Server PC. Afterwards, the web-browser will carp that the certificate is not certified by a trusted authority but you can ignore that (after all, you know the site is fine).

On the other hand, if you want to remotely-access Premise Server using Builder, you'll need to open port 3977 (at the very least). I've never done this so I can't offer more help on this issue.

 

[chucklyons]

123 is correct in opening 3977 will provide you the ability to use the builder remotely. I've done it a number of times, for both paid jobs and being on the road (a lot lately). It was really a well thought out notion, as when one has a number of installs, being able to log in remotely and 'tweak' configs is/was a big timesaver....

 

[nov0798]

I just want to be able to see the web page from a remote location, not necessarily use builder. I have port forwarded any IN to 443 on that servers IP address, but still cant get it??

 

[123]

Search Premise Help for "Using SSL in Premise".

 

[chucklyons]

So I am assuming you have port 80 opened on the firewall...and you're using the ip address of your router, vs your internal ip address? Can you get to it via port 80? 443? 86? (If you look at builder->webserver, select the default site, then in the properties , you'll see the default port and the alternatiye port). I have always used the alternate port as my primary, so I'm not sure how it handles the two...the other thing, just as a reminder, make sure you are able to grab the activex component. If you want to make sure that the activex-browser isnt the problem, you can hit your ip address/ppc and get the minibrowser version (which doesn't require activex)

 

[nov0798]

I know Ive been asking alot of questions here, but another issue Im having is that the premise browser, and the "last triggered" doesnt show up properly in the web browser, or the server end. Example: my kitchen door shows that it was last opened on x date, and x time, however the basement window shows 2002 year, and wont update the browser or the server?? Any ideas on this?