I built a signalR service that my WPF application uses and in development everything worked fine (since its running locally).
When it came to test environment, when I published it (on remote windows server 2008 r2 as windows service) I had error connecting.
The service runs on port 8080 and when I tried to run it on port 80 (I had to remove IIS for that) it worked fine so I assume its firewall problems.
I need an explanation of how to make it work (I had in mind that maybe because its duplex connection things work different) and since its for intranet app i'll have to ask my IT manager for opening these ports,
Related
I'm trying to access an API (created with visual studio WebAPI) on a remote computer.
I've followed this guide (https://www.codeproject.com/Articles/805238/Access-IIS-Express-Website-From-Remote-Machine), and I can now access it locally with http://IP:Port but not remotely. But it works when I disable the Firewall on my local PC, however I don't want it to be ad vitam aeternam opened
I've opened the port for ISS express like so in the guide, but it seems I need to open something else, I tried TCP and UDP inbound/outbound (TCP inboud was the one I opened with the guide), but it still don't work.
Thanks for your help.
I've installed Jira application server Version 7.1.4 on windows 10, I can connect to it with VM Ubuntu at my pc and also I can connect to it locally but I can't connect to it in other pc's in our office network.
I Use telnet MyserverIp and Myserver port and everything was ok.
let me know what is your idea.
Update: I changed firewall to turn off but it doesn't matter.
Thanks
I added tomcat8w.exe to "Allow a program or feature through windows firewall" at control panel windows firewall and problem is resolved.
I'm developing a web site with Visual Studio 2013 Express for Web on Windows 7, and I need to ensure compatibility with IE8, so I installed Windows Virtual Machine/XP Mode, and set up network bridging to that the VM uses the same network adapter as the main machine.
Ideally, I would like to be able to connect IE8 running in the VM to the debug IIS server started by Visual Studio on the W7 machine, since having to deploy the site to the actual server every time I want to test a minor fix to the formatting would be a hassle.
The VM network bridging seems to be successful, since I can access domain-only web sites and ping the W7 machine from the VM, but pointing a browser to the site address and substituting the W7 IP for "localhost" comes back with a connection problem, I suspect because IIS is refusing the connection.
Is there a way to configure the IIS process that Visual Studio uses for debugging so that I can connect to it from a virtual machine?
I have Windows Azure SDK 1.6 installed along with Azure tools. I have one web role (with two endpoints, port 80 for http and port 443 for https) and only have one instance of the web role running (for testing purposes).
When I ran it from Visual Studio for debugging last week, it ran the emulator, attached it to IIS with a binding of 127.0.0.1:80 and everything was peachy.
But as of yesterday, as soon as I started it was trying to bind it to 127.255.0.1:82 and it stopped working with this error (from Visual Studio):
There was an error attaching the debugger to the iis worker process
for URL 'http://127.255.0.0:82'
Now if I manually go to IIS and change the bindings back, I can access the site through a browser but obviously I can't debug it via VS.
Why is Visual Studio doing this? What made it change from last week (I've only made code changes and I have commented them out)?
Edit: I know about this blog, but my issue seems to be different because for one reason I don't have errors in the event logs. And like I mentioned as soon as I change the bindings manually in IIS, I can access the site properly so the app pool is configured correctly.
Edit2: I have the following set:
<compilation debug="true" targetFramework="4.0" />
And my cloud project is set to startup project as well.
When I ran it from Visual Studio for debugging last week, it ran the
emulator, attached it to IIS with a binding of 127.0.0.1:80 and
everything was peachy.
I don't believe you ever debugged a Azure Emulator deployed project on 127.0.0.1:80 binding with IIS. There is a chance that what you've debugged is just the Web Application project and not the Azure Deployed one. Let me explain why:
Windows Azure Emulator uses internal emulated Load Balancer (LB).
This emulated LB binds to 127.0.0.1 port 80 (if port 80 is already
taken it uses port 81)
Windows Azure Tools are dynamically creating a virtual IP address
for every instance of a webrole you have. These dynamic IP Addresses
are 127.255.0.X, where X is the logical number of the instance (0,
1, 2, etc...).
Windows Azure tools creates a website in the local IIS, with binding
of 127.255.0.X and port 82
Step 3 is repeated for every instance you have defined.
When start debugging, your browser usually opens http: //127.0.0.1:81/ which is the address of the LB. But the request from this address is forwarded to the IIS and its binding to 127.255.0.X:82. You could not have debugged a Windows Azure Emulator deployed project by manually attaching debugger to 127.0.0.1:80, because, if everything was fine there is no w3wp process listening on that address:port, but Azure emulated LB.
When you only have the WebRole (no additional sites defined), Windows Azure Tools does know that it shall attach the debugger to 127.255.0.X:82 where a w3wp process is listening.
This is the clean working configuration of Azure Emulator & SDK & Tools v.1.6 (I think also 1.5 and even back to 1.3 where the Full IIS mode was introduced for first time)
Now if I manually go to IIS and change the bindings back, I can access
the site through a browser but obviously I can't debug it via VS.
Yes, you will be able to access the site, but in that way you are skipping the emulated LB, which is not the point when developing Windows Azure Applications.
If you are heving issues of that kind, I suggest that you clean your solution, restart the computer, and if the problem persist uninstall the SDK & Tools and perform clean full install of SDK & Authoring tols for Windows Azure v.1.6 using the Web Platform Installer.
I have a VM on my Win 7 machine running Server 2008. My website can't run properly unless it's running on the server due to COM+, other website integration and environment variables. Currently, I have VS2008 installed on the Windows Server 2008 and I develop there (which is dumb, I know) instead on in my Win 7 workstation. I hate this setup.
My question is, how can I developer on my workstation and then EASILY push and test th websites on the VM Server?
Access files across the network so the actual changes are made on the VM Server?
Make changes locally and publish to VM Server?
Can I set up VS2008 so that if I when I Run the application in VS2008 it pushes everything over and opens a web browser that points to the VMServer's IIS Website?
Of course, the VM is a server on your network. Exactly like any other server on your network, virtual or otherwise.
For debugging you can setup VS2008 to remote debug but I think you'd have to publish the site, start it and then hook up the debugging but I'm happy to learn that there's an easier way... anyone?