When I connect my Windows CE 6 device to my development machine I get Microsoft USB Sync to register in Windows Device manager. But I cant connect with ActiveSync for some reason. Any ideas on how to fix this?
It worked with Windows CE 5, but when we upgraded ActiveSync-functionality disappeared.
NEW UPDATE 13.34:
Error log from WCESCOMM.LOG:
06/07/2010 13:31:12.495 - USB: RNDIS device id ...
06/07/2010 13:31:12.964 - USB: Event 32768, name ...
06/07/2010 13:31:12.964 - USB: Device Arrival notification
06/07/2010 13:31:12.980 - ComSerial: Closed device.
06/07/2010 13:31:13.042 - UsbComm: Open device <USB>.
06/07/2010 13:31:13.042 - UsbComm: Change DTR to 1.
06/07/2010 13:31:13.058 - Serial: Starting device detection at 115200.
06/07/2010 13:31:13.073 - UsbComm: Change DTR to 1.
06/07/2010 13:31:13.339 - AutobaudDetect: Found character <C>.
06/07/2010 13:31:13.355 - AutobaudDetect: Found character <L>.
06/07/2010 13:31:13.370 - AutobaudDetect: Found character <I>.
06/07/2010 13:31:13.386 - AutobaudDetect: Found character <E>.
06/07/2010 13:31:13.386 - AutobaudDetect: Found character <N>.
06/07/2010 13:31:13.402 - AutobaudDetect: Found character <T>.
06/07/2010 13:31:13.402 - Serial: Unimodem handshake at 115200.
06/07/2010 13:31:13.417 - Proxy: Change connection state 1.
06/07/2010 13:31:13.417 - Proxy: Created dynamic proxy on port 5655.
06/07/2010 13:31:13.433 - Proxy: Created dynamic proxy on port 3000.
06/07/2010 13:31:13.433 - Proxy: Created dynamic proxy on port 3001.
06/07/2010 13:31:13.449 - Proxy: Created dynamic proxy on port 3002.
06/07/2010 13:31:13.464 - Proxy: Created dynamic proxy on port 3003.
06/07/2010 13:31:13.464 - Proxy: Created dynamic proxy on port 3004.
06/07/2010 13:31:13.464 - Proxy: Created dynamic proxy on port 3005.
06/07/2010 13:31:13.480 - Proxy: Created dynamic proxy on port 3006.
06/07/2010 13:31:13.480 - Proxy: Created dynamic proxy on port 3007.
06/07/2010 13:31:13.495 - Proxy: Created dynamic proxy on port 3008.
06/07/2010 13:31:13.495 - Proxy: Created dynamic proxy on port 3009.
06/07/2010 13:31:13.495 - Proxy: Created dynamic proxy on port 3010.
06/07/2010 13:31:13.511 - Proxy: Created dynamic proxy on port 3011.
06/07/2010 13:31:13.511 - Proxy: Created dynamic proxy on port 3012.
06/07/2010 13:31:13.511 - Proxy: Created dynamic proxy on port 3013.
06/07/2010 13:31:13.527 - Proxy: Created dynamic proxy on port 3014.
06/07/2010 13:31:13.527 - Proxy: Created dynamic proxy on port 3015.
06/07/2010 13:31:13.527 - Proxy: Created dynamic proxy on port 3016.
06/07/2010 13:31:13.527 - Proxy: Created dynamic proxy on port 3017.
06/07/2010 13:31:13.542 - Proxy: Created dynamic proxy on port 3018.
06/07/2010 13:31:13.542 - Proxy: Created dynamic proxy on port 3019.
06/07/2010 13:31:13.542 - Proxy: Created dynamic proxy on port 3020.
06/07/2010 13:31:13.558 - Proxy: Created dynamic proxy on port 3021.
06/07/2010 13:31:13.558 - Proxy: Created dynamic proxy on port 3022.
06/07/2010 13:31:13.574 - Proxy: Created dynamic proxy on port 3023.
06/07/2010 13:31:13.574 - Proxy: Created dynamic proxy on port 3024.
06/07/2010 13:31:13.574 - Proxy: Created dynamic proxy on port 3025.
06/07/2010 13:31:13.589 - Proxy: Created dynamic proxy on port 3026.
06/07/2010 13:31:13.589 - Proxy: Created dynamic proxy on port 3027.
06/07/2010 13:31:13.589 - Proxy: Created dynamic proxy on port 3028.
06/07/2010 13:31:13.605 - Proxy: Created dynamic proxy on port 3029.
06/07/2010 13:31:13.605 - Proxy: Created dynamic proxy on port 3030.
06/07/2010 13:31:13.605 - Proxy: Created dynamic proxy on port 3031.
06/07/2010 13:31:13.620 - Proxy: Created dynamic proxy on port 6510.
06/07/2010 13:31:13.620 - Proxy: Created dynamic proxy on port 6511.
06/07/2010 13:31:13.636 - Proxy: Created dynamic proxy on port 6512.
06/07/2010 13:31:13.636 - Proxy: Created dynamic proxy on port 6513.
06/07/2010 13:31:13.636 - Proxy: Created dynamic proxy on port 6514.
06/07/2010 13:31:13.652 - Proxy: Created dynamic proxy on port 6515.
06/07/2010 13:31:13.652 - Proxy: Created dynamic proxy on port 6516.
06/07/2010 13:31:13.667 - Proxy: Created dynamic proxy on port 6517.
06/07/2010 13:31:13.667 - Proxy: Created dynamic proxy on port 6518.
06/07/2010 13:31:13.667 - Proxy: Created dynamic proxy on port 6519.
06/07/2010 13:31:13.683 - Proxy: Created dynamic proxy on port 6520.
06/07/2010 13:31:13.683 - Proxy: Created dynamic proxy on port 6521.
06/07/2010 13:31:13.683 - Proxy: Created dynamic proxy on port 6522.
06/07/2010 13:31:13.699 - Proxy: Created dynamic proxy on port 6523.
06/07/2010 13:31:13.699 - Proxy: Created dynamic proxy on port 6524.
06/07/2010 13:31:13.714 - Proxy: Created dynamic proxy on port 6525.
06/07/2010 13:31:13.714 - Proxy: Created dynamic proxy on port 6526.
06/07/2010 13:31:13.714 - Proxy: Created dynamic proxy on port 6527.
06/07/2010 13:31:13.730 - Proxy: Created dynamic proxy on port 6528.
06/07/2010 13:31:13.730 - Proxy: Created dynamic proxy on port 6529.
06/07/2010 13:31:13.730 - Proxy: Created dynamic proxy on port 6530.
06/07/2010 13:31:13.745 - Proxy: Created dynamic proxy on port 6531.
06/07/2010 13:31:13.745 - Proxy: Created dynamic proxy on port 6532.
06/07/2010 13:31:13.761 - Proxy: Created dynamic proxy on port 6533.
06/07/2010 13:31:13.761 - Proxy: Created dynamic proxy on port 6534.
06/07/2010 13:31:13.761 - Proxy: Created dynamic proxy on port 6535.
06/07/2010 13:31:13.777 - Proxy: Created dynamic proxy on port 6536.
06/07/2010 13:31:13.777 - Proxy: Created dynamic proxy on port 6537.
06/07/2010 13:31:13.777 - Proxy: Created dynamic proxy on port 6538.
06/07/2010 13:31:13.792 - Proxy: Created dynamic proxy on port 6539.
06/07/2010 13:31:13.792 - Proxy: Created dynamic proxy on port 6540.
06/07/2010 13:31:13.792 - Proxy: Created dynamic proxy on port 6541.
06/07/2010 13:31:13.808 - Proxy: Created dynamic proxy on port 1026.
Error log from WCESMgr.log:
06/07/2010 13:31:51.339 **************** Logging Started ****************
06/07/2010 13:31:51.339 Process C:\Program\Microsoft ActiveSync\WCESMgr.exe p(3040)
06/07/2010 13:31:51.339 ActiveSync second instance started, Cmd line: '/show'
06/07/2010 13:31:51.339 ActiveSync second instance exiting
06/07/2010 13:31:51.339 **************** Logging Stopped ****************
Windows CE 6 and Windows CE 5 are two different things so saying that something that relates to a driver worked on one does not reflect on the other.
What exactly is the error? Does Windows (I assume XP) ask for a driver to be installed or does it say that there is an unrecognized device attached.
Are you building the OS? If so:
Having worked with Windows CE 5 you know the HW is OK so you need to make sure you have a USBFN driver that operates properly. You also need to make sure that your USB serial_class registry settings are correct and that the catalog item is included (if you are building the OS of course). Catalog item is SYSGEN_USBFN_SERIAL. You also need to make sure that Active Synce is included in the OS (SYSGEN_AS_BASE).
Update:
So, you are the OEM. If you say that you see the dialer start and stop on the Windows CE device you can look at your debug serial to look for an error code. It might be that your RAS phone book entry is not correct.
Try the following:
Check on the Desktop to see whether it identifies an unidentified USB device. At least you will know that the desktop tried to communicate with the device and failed to retreive the descriptors.
Make sure that the Serial_class is the one that Windows CE tries to use. You do this by settings the following registry setting (Windows CE 6 does not support ActiveSync over RNDIS):
[HKEY_LOCAL_MACHINE\Drivers\USB\FunctionDrivers]
"DefaultClientDriver"="Serial_Class"
You should have an entry for [HKEY_LOCAL_MACHINE\Drivers\USB\FunctionDrivers\Serial_Class] once you include the serial class catalog item. This entry is copied from WINCE600\PUBLIC\COMMON\OAK\FILES\common.reg in case you are not setting something of your own in one of your OSDesing registry files.
Did you delete the old connection and start a new one? I've had similar issues with CE 5. That sometimes worked as well as just rebooting everything.
Related
As the question at title, I'm setup the following architecture on Azure Cloud and having trouble at restricting direct access from the internet to VMs.
Here are architecture requirements:
Both VMs must have public ips (for SysAdmin to access via SSH)
Direct traffics from Internet to WebService on VMs (via port 80) must be denied
The web traffics from Internet must go thru Public LB to VMs
Suppose that both VMs are in WebASG (Application Security Group), in the NSG setting that applied to VM's Subnet, I've add some rules (which have higher priority than 3 Azure NSG default rules):
Scenario A (adding 1 custom rule):
Port: 80 - Protocol: Tcp - Source: Internet - Destination:
WebASG - Action: Allow
With this NSG setting, I could access WebService from LoadBalancer IP (satisfy #3 requirement), but WebService on port 80 of both VMs will be exposed to Internet (that violates #2 requirement)
Scenario B (adding 2 custom rules):
Port: 80 - Protocol: Tcp - Source: AzureLoadBalancer -
Destination: WebASG - Action: Allow
Port: 80 - Protocol: Tcp - Source: Internet - Destination:
WebASG - Action: Deny
With this NSG setting, #2 requirement is satisfied, but I could not access WebService when visit LoadBalancer IP (violates #3 requirement)
Please note that: using AGW (Azure Application Gateway, I could make all the requirements happened by these NSG configuration:
RuleName: AllowSSH Port: 22 - Protocol: Tcp - Source:
sys-admin-ip-address - Destination: WebASG - Action: Allow
RuleName: DenyInternet2Web Port: Any - Protocol: Any -
Source: Internet - Destination: WebASG - Action: Deny
RuleName: AllowProbe2Web Port: 80 - Protocol: Tcp -
Source: VirtualNetwork - Destination: WebASG - Action:
Allow
RuleName: AllowProbe2Web Port: 80 - Protocol: Tcp -
Source: VirtualNetwork - Destination: WebASG - Action:
Allow
I dont want using AGW because it would cost more money than Azure LoadBalancer (actually the Basic LoadBalancer is free). So, how could I change NSG to satisfy all requirements when using LoadBalancer?
Thank in advance for any help!
I don't think there are NSG rules that will satisfy all requirements because of the #1 and #2 requirements are contradictory.
If the VMs must have public IP addresses, it actually has a chance to expose to the Internet. Any clients could access the VMs via the public IP. It works the same if you want to access the VMs through the load balancer frontend IP. Read the https://learn.microsoft.com/en-us/azure/load-balancer/load-balancer-overview#load-balancer-concepts
Load Balancer doesn't terminate or originate flows, interact with the
payload of the flow, or provide any application layer gateway
function. Protocol handshakes always occur directly between the client
and the back-end pool instance. A response to an inbound flow is
always a response from a virtual machine. When the flow arrives on the
virtual machine, the original source IP address is also preserved.
In this case, you could remove the backend-instance IP address, just use the load balancer frontend for the web traffic and SSH connection. If so, You could configure port forwarding in Azure Load Balancer for the SSH connections to individual instances and a load balancer rule for the web traffic following this quickstart, which works with standard LB. You can only allow port 80 and 22 from your clients' IP addresses. The NSG will look like this,
Port: 80,22 - Protocol: Tcp - Source: client's IP list - Destination: WebASG - Action: Allow
I'm trying to set up a Redis with docker-compose for different environments.
Therefore I need to expose two domains with traefik on the same port:
domain.com:6379
domain-dev.com:6379
I can't expose those ports on the container, because they are running on the same server.
My docker-compose file (for domain-dev) looks like this:
version: '2'
services:
redis:
container_name: redis-signalr-dev
image: redis
volumes:
- ./redis-signalr-data:/data
restart: always
labels:
- traefik.enable=true
- traefik.backend=redis-signalr-dev
- traefik.frontend.rule=Host:domain-dev.com
- traefik.port=6379
- traefik.docker.network=traefik_default
- traefik.frontend.entryPoints=redis
networks:
- traefik_default
volumes:
redis-signalr-data:
networks:
traefik_default:
external: true
I also tried to configure the treafik to use the following endpoint:
--entrypoints='Name:redis Address::6379'
When connecting to "domain-dev.com:6379" a connection cannot be astablished.
Does anyone know a solution to this problem?
Traefik is a reverse proxy for http, not a tcp load balancer. So traefik itself (usually) opens ports 80 and 443 for ingress and forwards incoming http requests to the given http-able backends. The port you specify in your compose service labels is the port of the container, the traffic should be passed to.
So if you run a nodejs (http) server on port 3000, you would connect to http://yourdomain:80 and traefik would forward the requests to your nodejs container on port 3000. This means that by specifying a port on a compose service, you will not open this port on your host.
In your example running redis with its custom protocol, traefik is not a solution as traefik only does http proxying. To expose redis on your host (if you really want to do that), just use regular docker port mappings and point your domains to your docker hosts. Doing this, there is no way to use the same port with different domains, just specify two different ports for your both instances. For http this works by traefik inspecting the http requests and doing routing based on the host header.
Traefik 2.0 will have TCP support: https://github.com/containous/traefik/pull/4587
Until then you'd have to use NGINX or similar.
I am using docker-compose to work across multiple docker containers, all these containers are mostly individual django rest framework built applications. I have downloaded all the containers and am able to build the whole application using all these containers.
Each container has postgres db running, I want to browse the db now using any ui tool. I know pgadmin can do the work here, but how I can configure my pgadmin to showcase any postgres database from these containers?
It should be possible to expose your database port also to your local network.
Normally you connect your application containers internally to the database container. In that case it's not needed declare the ports section in your compose file for the database, but if you have that entry you bind your database in addition to your local host.
After you have also expose the postgres port to your host port it should be no problem to connect with the gui tool of your choice.
version: '3.2'
services:
httpd:
image: "oth/d_apache2.4:0.2"
ports:
# container port 80 of the webserver to localhost 80
- "80:80"
keycloak:
# keycloak uses keycloak_db
image: "jboss/keycloak-postgres:3.2.1.Final"
environment:
# internal network reference to db container
- POSTGRES_PORT_5432_TCP_ADDR=keycloak_db
- POSTGRES_PORT_5432_TCP_PORT=5432
keycloak_db:
environment:
image: "postgres:alpine"
ports:
# container port 5432 to localhost 5432
# stack intern is the port still available
- "5432:5432"
Make sure that the port of the postgres container is mapped to the host system. The default postgres port is 5432. You can do that with the port directive in your docker-compose.yml. You are only able to map the port once. So your config file would look like:
services:
postgres_1:
ports:
- "49000:54321"
[...]
postgres_2:
ports:
- "49001:54321"
[...]
After that you should be able to access the desired database with the IP of your docker host and the above specified port.
If you still encounter problems connecting with a client like pgadmin check the following configuration files inside your container.
Is there anything blocking your connection attempt? Is yourdocker host behind a firewall?
postgresql.conf under the section connections and authentication:
listen_addresses
port
Check your pg_hba.conf, which controls client authentication.
For debug purposes you can set it to the following:
Don't do the following in production:
host all all all trust
I have a use case where I am running services on my local machine which is behind a router behind a NAT, so I can't port forward to my public IP. The only way to do it is via ssh tunneling or a VPN, for both I would need an exposed port to connect from my local
So,
i tried setting up my yml config with external ip,
and it looks like this :
spec:
ports:
- name: 8022-tcp
protocol: TCP
port: 8022
targetPort: 8022
nodePort: 31043
- name: 8080-tcp
protocol: TCP
port: 8080
targetPort: 8080
nodePort: 30826
selector:
deploymentconfig: remote-forward
clusterIP: 172.30.83.16
type: LoadBalancer
externalIPs:
- 10.130.79.198
deprecatedPublicIPs:
- 10.130.79.198
sessionAffinity: None
If I understand correctly here 10.130.79.198, is the IP I will need to connect to from my local ssh on port 31043 which then forwards it to the service port 8022 which then forwards to container port 8022 where the ssh server is running.
The problem is that I am not able to connect to this external IP.
ssh logs:
"debug1: connect to address 10.130.79.198 port 31043: Connection timed out"
I got this external IP from the pod -> dashboard page -> external IP. Is this external IP needs to be configured anywhere or is my above config has any issue with the setup?
Message Analyzer seems to have no UI way to parse protocols on non-default ports. I have TLS server running on non standard port (not 443) and Message Analyzer won't parse captured as TLS.
Quick workaround is to update TLS port from 443 to needed port number in C:\Users\\AppData\Local\Microsoft\MessageAnalyzer\OPNAndConfiguration\OPNs\CoreNetworking\TLS.opn
// http://www.iana.org/assignments/port-numbers
pattern Port = enum ushort
{
...
HTTPS = 443