Many businesses have moved TallyPrime from their office computer to a Cloud Server, Windows VPS, Remote Desktop Server or hosted Tally environment.

This provides several advantages because users can work in TallyPrime remotely from the office, home, branch office or while travelling.

At the same time, business owners increasingly want to view Tally information on their smartphones using applications such as:

• Biz Analyst
• LiveKeeping
• CredFlow
• Other Tally-on-Mobile applications
• Collection-management applications
• Tally dashboard applications
• MIS/reporting applications
• Custom Tally integrations
• Tally API/XML-based applications

A common question therefore arises:

If TallyPrime is running on a Cloud Server or VPS, can a Tally-on-Mobile desktop connector installed on my local office PC connect to that cloud Tally?

In many technical architectures, yes, this may be possible, provided the Tally/mobile application supports connecting to a remote Tally instance and the cloud/VPS environment permits the required network communication.

The basic architecture can be:

TallyPrime on Cloud/VPS → IP/Hostname + Port → Local Desktop Connector → Mobile Application/Cloud Platform

However, opening a Tally service directly to the public Internet creates security considerations. Therefore, configuration should be performed carefully with the Tally-on-Mobile application vendor and your Cloud/VPS provider.

Understanding the Basic Architecture

In a traditional local installation, the environment may look like:

TallyPrime

↓

Tally Mobile Desktop Connector

↓

Internet

↓

Mobile App

Because both TallyPrime and the connector may be running on the same computer or LAN, communication can be straightforward.

For example, an application may communicate with a service using:

localhost

or

127.0.0.1

or the computer's LAN IP.

But the situation changes when TallyPrime is moved to a cloud server.

The environment becomes:

Cloud/VPS

↓

TallyPrime

↓

Internet / Private Network

↓

Office PC

↓

Tally Mobile Desktop Connector

↓

Vendor Cloud Platform

↓

Mobile App

The connector must therefore know where TallyPrime is located and how it can securely reach it.

Three Important Pieces of Information

For many remote connector architectures, you may need:

1. Server Address

This could be:

IP Address

or

Hostname

or

DNS Name / URL

2. Port Number

The connector needs to know which service/port it should communicate with.

3. Network Permission

The cloud firewall, Windows Firewall or another security layer must permit the required communication.

In simplified form:

Server Address + Port + Permission = Connectivity

But authentication, application compatibility and security controls are also essential.

Example Architecture

Suppose TallyPrime is running on a Windows VPS.

The cloud provider gives you a server address such as:

203.0.113.25

Assume, purely for illustration, that the relevant Tally integration service has been configured to listen on:

Port 9000

The conceptual endpoint becomes:

203.0.113.25:9000

Alternatively, suppose a DNS hostname has been configured:

tally.example.com

Then the conceptual endpoint could be:

tally.example.com:9000

Important: These addresses are examples only. 203.0.113.25 belongs to an IP range reserved for documentation.

The actual port and connection method must be confirmed with your Tally/mobile integration vendor and cloud provider.

Is Port 9000 Always the Tally Port?

No.

This is an important point.

Port 9000 is commonly associated with Tally integrations and is frequently encountered in Tally configurations, but you should never assume that every installation uses port 9000.

Depending on:

• TallyPrime configuration
• Tally version
• Integration software
• Connector design
• Cloud architecture
• Multiple Tally instances
• Security policies

a different port may be configured.

Therefore, ask the application vendor:

Which protocol, destination port and connection method does your desktop connector require for connecting to TallyPrime on a remote VPS?

This is much safer than simply asking the cloud provider to "open port 9000."

Step 1 — Confirm That the Mobile Application Supports Remote Tally

Before changing any firewall configuration, contact your Tally-on-Mobile software vendor.

Ask:

"My TallyPrime is running on a Windows Cloud/VPS server. Can your desktop connector installed on my local PC connect to Tally using the server's IP address or hostname?"

Also ask:

• What port is required?
• TCP or UDP?
• Does the connector support hostname?
• Does it support an IP address?
• Does it require HTTP?
• Does it support HTTPS/TLS?
• Can the connector work through VPN?
• Can the connector itself be installed on the VPS?
• Is IP whitelisting supported?
• Does it require inbound Internet exposure?

Do not make firewall changes until these requirements are confirmed.

Step 2 — Ask Your Cloud/VPS Provider for the Server Address

If the application supports remote connections, you need an address through which the connector can reach the server.

This may be:

Public IP Address

Example:

203.0.113.25

Hostname

Example:

vps.example.com

Dedicated DNS Name

Example:

tally.example.com

A hostname can be easier to manage than entering an IP everywhere, particularly if infrastructure changes later.

However, the hostname must resolve to the correct server address.

IP Address vs URL vs Hostname

These terms are frequently confused.

IP Address

Example:

203.0.113.25

This identifies the network endpoint.

Hostname

Example:

tally.example.com

DNS converts the hostname into an IP address.

URL

A URL may include a protocol and port, for example:

https://tally.example.com:9443

Not every Tally connector expects a complete URL.

Some applications may provide separate fields:

Server: tally.example.com
Port: 9000

Others may request:

Server URL: https://...

Therefore, enter information exactly in the format specified by the connector vendor.

Step 3 — Determine the Required Port

Ask the mobile application vendor which port the connector requires.

For example:

Server: tally.example.com

Port: 9000

The actual number may be different.

Do not randomly open several ports hoping that one will work.

Only the required port should be permitted.

This follows the security principle of:

Least Privilege

Step 4 — Ask the Cloud Vendor to Permit the Required Connection

Depending on the cloud infrastructure, there may be several firewall layers.

For example:

Internet

↓

Cloud Firewall / Security Group

↓

Windows Firewall

↓

TallyPrime / Required Service

The port must be permitted through every applicable layer.

If the cloud firewall blocks the traffic, changing Windows Firewall alone will not solve the problem.

Likewise, if the cloud firewall permits the connection but Windows Firewall blocks it, the connection will still fail.

What Information Should You Give Your Cloud Vendor?

Instead of saying:

"Please open Tally port."

provide complete technical information.

For example:

We are using a Tally-on-Mobile desktop connector on our office PC that needs to communicate with TallyPrime hosted on this VPS. Please confirm whether remote access to the required Tally integration service is supported. The application vendor has specified TCP port XXXX. If Internet exposure is required, please restrict access to our office public IP address where possible and advise whether VPN/private connectivity is preferable. Please also provide the appropriate server IP address or hostname for the connector configuration.

This gives the cloud provider enough information to implement the rule securely.

Step 5 — Prefer IP Whitelisting

This is one of the most important security recommendations in this article.

Suppose your office has a static public IP:

198.51.100.50

Instead of allowing:

Anyone on Internet → Tally Port

configure:

198.51.100.50 → Required Port → Tally VPS

where technically supported.

This means only the approved office Internet connection can initiate communication with that service.

Avoid This Configuration

Source: Any

Destination: Tally Server

Port: Tally integration port

Allowed: Yes

This may unnecessarily expose the service to the public Internet.

Better Configuration

Source: Authorized Office Public IP

↓

Cloud Firewall

↓

Required Port Only

↓

Tally VPS

↓

Tally Integration Service

This significantly reduces exposure.

Dynamic Public IP Can Create a Problem

Many broadband connections receive a dynamic public IP.

For example:

Monday:

49.x.x.100

Tuesday:

49.x.x.147

If the firewall permits only Monday's IP address, the connector may stop working after the ISP changes the address.

Possible solutions include:

• Static public IP from ISP
• VPN
• Site-to-site VPN
• Secure tunnel
• Vendor-supported relay
• Private networking
• Zero-trust networking solution

The correct method depends on the cloud provider and application.

A VPN Is Often Better Than Direct Public Port Exposure

Where supported, a VPN can provide a more secure architecture.

Instead of:

Internet → Public Tally Port

use:

Office PC

↓

Encrypted VPN

↓

Private VPS Network

↓

TallyPrime

The connector can then potentially communicate with Tally using a private VPN address.

Example:

10.10.0.5:9000

rather than a publicly exposed endpoint.

This is generally preferable when the connector supports it.

Can the Desktop Connector Be Installed Directly on the VPS?

This should be one of the first questions asked.

If the vendor supports it, an alternative architecture may be:

Windows VPS

TallyPrime + Mobile Desktop Connector

↓

Vendor Cloud

↓

Mobile Application

This can eliminate the need for the connector to travel from an office PC across the Internet to Tally.

Advantages may include:

• Lower dependency on office PC
• Lower dependency on office Internet
• Connector remains available when office PC is off
• Potentially simpler communication with Tally
• Reduced need for direct public Tally-port exposure

However, whether this is supported depends entirely on the application vendor and cloud environment.

Compare the Two Architectures

Architecture A — Connector on Local Office PC

Tally VPS

↓

Internet/VPN

↓

Local PC Connector

↓

Mobile Platform

Potential requirements:

• Server IP/hostname
• Required port
• Firewall rule
• Office Internet
• Local PC must remain running
• Security controls

Architecture B — Connector on VPS

TallyPrime + Connector on Same VPS

↓

Internet

↓

Mobile Platform

Potential advantages:

• No dependency on local office PC
• No need for remote connector-to-Tally communication
• Potentially lower latency
• Easier continuous synchronization

But it must be explicitly supported by the software vendor.

Which Architecture Is Better?

Where supported, installing the connector inside the same secured VPS environment as TallyPrime can often be operationally simpler.

However, some vendors may design their desktop connector specifically for another deployment model.

Therefore:

Always follow the supported architecture recommended by the Tally-on-Mobile application provider.

What Happens When You Enter the IP and Port?

Conceptually, the connector attempts something similar to:

Connect → Server IP/Hostname → Port → Tally Service

If the server responds, the connector can proceed with the application-specific communication.

If not, errors may appear such as:

• Connection failed
• Unable to connect to Tally
• Server not found
• Connection refused
• Connection timed out
• Tally not running
• Port unavailable
• Unable to fetch company
• No company found
• Synchronization failed

Each message can indicate a different problem.

Connection Refused vs Connection Timed Out

These two errors are different.

Connection Refused

Usually indicates that the server was reachable but nothing accepted the connection on the specified port, or a firewall/service actively rejected it.

Possible reasons:

• Wrong port
• Tally not listening
• Required service stopped
• Incorrect configuration

Connection Timed Out

Frequently indicates that network traffic cannot reach the destination.

Possible reasons:

• Cloud firewall
• Windows Firewall
• Wrong IP
• ISP restriction
• Routing problem
• NAT problem
• Security policy

This distinction can help troubleshooting.

Check Whether TallyPrime Is Running

A mobile connector cannot normally retrieve live Tally information from a service that is not running or not exposing the required interface.

Therefore verify:

TallyPrime running?

↓

Correct company open/available?

↓

Required integration interface enabled?

↓

Correct port?

↓

Firewall permitted?

↓

Connector configured correctly?

Multiple Tally Instances Require Special Attention

Suppose the VPS runs multiple Tally instances.

For example:

Tally Instance 1 → Port 9000

Tally Instance 2 → Port 9001

Tally Instance 3 → Port 9002

This is only an example configuration.

The connector must communicate with the correct instance.

Incorrect port mapping could connect the application to the wrong Tally instance or simply fail.

Document the environment carefully.

Public IP May Not Always Be Available

Some cloud services use:

• NAT
• Shared public IP
• Reverse proxies
• Private networks
• Gateway servers
• RDP gateways

In these environments, you cannot assume that because RDP works, a Tally integration port can also be reached.

RDP and Tally integration traffic are separate services.

Your cloud provider must confirm whether the required network route can be provided.

RDP Address Is Not Automatically a Tally API Address

This is another common misunderstanding.

Suppose you connect to your server through:

server.example.com:3389

This does not automatically mean:

server.example.com:9000

will work.

The RDP port may be exposed while every other inbound port is blocked.

Therefore, confirm the network configuration with the cloud provider.

Never Expose RDP or Tally Ports Unnecessarily

Internet-facing services are continuously scanned by automated systems.

Therefore:

• Do not open unnecessary ports.
• Do not disable Windows Firewall.
• Do not use "Allow All."
• Do not expose a port to the whole Internet unless absolutely necessary and securely designed.
• Use IP restrictions whenever practical.
• Prefer VPN/private connectivity.
• Use strong authentication.
• Maintain Windows security updates.
• Monitor server logs.

Port Opening Alone Does Not Guarantee Connectivity

A successful connection requires the complete chain to work:

Connector

↓

Local Firewall

↓

Office Router/ISP

↓

Internet/VPN

↓

Cloud Firewall

↓

Windows Firewall

↓

Correct IP/Hostname

↓

Correct Port

↓

Tally/Integration Service

If any one component blocks communication, synchronization may fail.

DNS Hostname Can Be Easier Than Remembering IP Addresses

Instead of configuring:

203.0.113.25

you may configure:

tally.example.com

where supported.

If the VPS IP changes later, DNS can potentially be updated while keeping the same hostname.

However, DNS should be configured correctly and securely.

What About HTTPS?

If the application supports a secure HTTPS/TLS gateway, that may be preferable to exposing a plain HTTP service.

The architecture might become:

Local Connector

↓

HTTPS/TLS

↓

Secure Gateway

↓

Tally Integration Service

Whether this is possible depends on the connector, Tally integration design and cloud environment.

Do not simply add HTTPS yourself and assume that the application will support it.

Performance Considerations

Connecting a mobile application to cloud-hosted Tally also creates additional workload.

The synchronization process may use:

• VPS CPU
• VPS RAM
• Storage I/O
• Tally processing resources
• Internet bandwidth

If Tally is already being used by many simultaneous RDP users, aggressive synchronization can add to the workload.

Keep a Reasonable Synchronization Interval

For example, suppose a connector checks Tally every minute.

During ten hours:

10 × 60 = 600 synchronization cycles

If the business only needs reports every 15 minutes:

600 ÷ 15 = 40 synchronization cycles

The actual amount of work per synchronization varies significantly by application because many connectors use incremental processing.

Nevertheless:

Avoid unnecessarily frequent synchronization when the business does not require real-time data.

This is especially important on busy Tally Cloud/VPS environments.

Suggested Deployment Planning

A professionally managed deployment can follow this approach:

Step 1

Identify the Tally-on-Mobile application.

Step 2

Ask the application vendor whether remote Tally connectivity is supported.

Step 3

Ask whether the connector can run directly on the VPS.

Step 4

Obtain the exact protocol and port requirements.

Step 5

Obtain the VPS IP address or hostname.

Step 6

Prefer VPN/private networking if supported.

Step 7

If a public port is necessary, restrict it to authorized source IPs where possible.

Step 8

Configure Windows Firewall.

Step 9

Configure the cloud firewall/security group.

Step 10

Configure the connector with the correct server address and port.

Step 11

Test connectivity.

Step 12

Test synchronization.

Step 13

Monitor Tally/VPS performance.

Step 14

Adjust synchronization frequency according to business requirements.

Example Configuration

Assume:

Tally Server

Windows VPS

Hostname

tally.example.com

Required Port

9000

Office Public IP

198.51.100.50

A restricted firewall design could conceptually be:

Source

198.51.100.50

Destination

Tally VPS

Protocol

TCP

Destination Port

9000

Action

Allow

Then the connector may be configured:

Server: tally.example.com

Port: 9000

Again, these are examples.

The actual port, protocol and connector settings must come from the application vendor.

Recommended Security Architecture

Where technically possible:

Mobile App

↓

Vendor Cloud

↓

Local/VPS Connector

↓

VPN / Private Connection

↓

TallyPrime

is preferable to simply exposing a Tally integration service broadly to the Internet.

Troubleshooting Checklist

If the Tally-on-Mobile application cannot connect to cloud-hosted Tally, check:

1. Is TallyPrime running?
2. Is the correct company available?
3. Is the required Tally integration interface enabled?
4. Is the correct port configured?
5. Is the connector using the correct IP/hostname?
6. Does DNS resolve correctly?
7. Is the cloud firewall allowing the connection?
8. Is Windows Firewall allowing it?
9. Is access restricted to the correct source IP?
10. Has the office public IP changed?
11. Is the connector running?
12. Does the application support remote Tally?
13. Is a VPN required?
14. Is the server behind NAT?
15. Is the cloud provider blocking custom inbound ports?
16. Are multiple Tally instances using different ports?
17. Is antivirus/security software blocking the connector?
18. Is Internet connectivity stable?
19. Are application credentials valid?
20. Are application and connector versions compatible?

Frequently Asked Questions (FAQ)

1. Can I connect a Tally-on-Mobile app when Tally is running on a VPS?

Potentially yes. It depends on whether the particular mobile application's connector supports remote Tally connectivity and whether the VPS permits the required network communication.

2. Can I install the mobile connector on my local office PC?

If the vendor supports remote server connectivity, yes. You will typically need the server address and required network settings.

3. Do I need my Tally Cloud server's IP address?

Often an IP address or resolvable hostname is required for a remote connection, depending on the application.

4. Can I use a hostname instead of an IP address?

Yes, if the connector supports hostnames and DNS is configured correctly.

5. Do I need to open a port?

If the local connector initiates a direct connection to a service on the VPS, an appropriate network path must exist. That may require a firewall rule, VPN or another vendor-supported mechanism.

6. Which port should I open?

Use only the port specified by the application/integration vendor and your Tally configuration. Do not assume a port number.

7. Is Tally commonly associated with port 9000?

Port 9000 is commonly encountered in Tally integration configurations, but this does not mean every environment uses it.

8. Can I simply open port 9000 for everyone?

This is not recommended. Public exposure should be minimized. Prefer source-IP restrictions, VPN or another secure architecture.

9. What is IP whitelisting?

It means allowing access only from specified trusted public IP addresses rather than the entire Internet.

10. What if my office has a dynamic IP?

Your firewall rule may stop working when the ISP changes your IP. Consider a static public IP, VPN or another secure connectivity solution.

11. Can I install the connector directly on the VPS?

Possibly, and it can be an attractive design. Ask the mobile application vendor whether server/VPS installation is officially supported.

12. Which is better: local connector or VPS connector?

If supported, running the connector close to Tally can simplify connectivity. However, the application's supported architecture should determine the final design.

13. Why does my RDP work but the Tally mobile connector does not?

Because RDP and the Tally integration service use different network services/ports. The firewall may permit RDP while blocking the connector's required port.

14. What does "Connection Refused" mean?

It commonly means the destination was reachable but the requested service was not accepting the connection on that port.

15. What does "Connection Timed Out" mean?

It often indicates firewall, routing, NAT or network reachability problems.

16. Can Windows Firewall block the connection?

Yes.

17. Can the cloud provider's firewall block it even if Windows Firewall allows it?

Yes. Both layers may need appropriate rules.

18. Is a VPN safer?

In many architectures, yes. A VPN can allow the connector to reach the server through a private encrypted network without broadly exposing the integration port.

19. Can mobile synchronization slow down cloud Tally?

It can add workload during synchronization. The actual impact depends on application design, data volume, frequency, VPS resources and concurrent Tally usage.

20. Should I increase the sync interval?

If real-time information is unnecessary and the application permits adjustment, a longer interval can reduce synchronization frequency.

21. Does the local PC need to remain switched on?

If the desktop connector runs on the local PC, generally it needs to remain available whenever synchronization is required.

22. What happens if the office Internet fails?

A local connector may temporarily lose access to the cloud Tally server. Synchronization behavior after reconnection depends on the application.

23. Would installing the connector on the VPS solve this problem?

It can eliminate dependency on the office PC and office Internet for connector-to-Tally communication, provided the application vendor supports this deployment.

24. Is Tally-on-Mobile synchronization the same as Tally backup?

No. Mobile synchronization should not automatically be treated as a backup solution.

25. Should my cloud provider configure this?

Network/firewall changes on a managed Tally cloud environment should generally be coordinated with the cloud provider. The mobile application vendor should provide the exact technical requirements.

Conclusion

If your TallyPrime is running on a Cloud Server, Windows VPS or hosted RDP environment, you may still be able to use Tally-on-Mobile solutions such as Biz Analyst, LiveKeeping, CredFlow and other compatible Tally-connected applications.

A possible architecture is:

TallyPrime on Cloud/VPS

↓

Server IP / Hostname + Required Port

↓

Secure Network Connection

↓

Tally-on-Mobile Desktop Connector on Local PC

↓

Mobile Application

However, this architecture should not be implemented by randomly opening Tally ports to the Internet.

First ask the mobile application vendor:

"Can your connector communicate with TallyPrime running on a remote VPS, and what exact protocol, port and server-address format are required?"

Then ask the cloud provider to provide or configure the appropriate:

IP Address / Hostname + Port + Firewall Rule + IP Whitelisting or VPN

Also investigate whether the mobile connector can be installed directly on the VPS alongside TallyPrime. If officially supported, this can sometimes be simpler and eliminate dependency on the local office PC.

The preferred order of connectivity should generally be:

Private/VPN connectivity → Restricted IP-based access → Public exposure only when necessary and properly secured.

Most importantly:

Never ask a cloud provider simply to "open the Tally port for everyone." Specify the required port, protocol and authorized source, and use the most restrictive configuration supported by the application.

A properly designed configuration can provide the convenience of Tally-on-Mobile while your actual TallyPrime remains hosted on the Cloud/VPS, without unnecessarily exposing your accounting server to the public Internet.

#tags

#TallyOnCloud #TallyOnVPS #TallyOnMobile #TallyPrime #TallyMobile #TallyCloud #TallyVPS #TallyPrimeCloud #TallyConnector #BizAnalyst #LiveKeeping #CredFlow #TallyIntegration #TallyAPI #TallyXML #TallyPort #TallyPort9000 #TallyFirewall #TallyIP #TallyServer #TallyRemoteAccess #TallyCloudAccess #TallyRDP #WindowsVPS #WindowsServer #TallyHosting #CloudTally #TallySynchronization #TallySync #TallyMobileApp #TallyReportsOnMobile #TallyDashboard #TallyRemote #TallySecurity #TallyVPN #TallyNetworking #TallyFirewallRule #TallyIPWhitelisting #TallyAPIIntegration #TallyXMLAPI #TallyHTTP #TallyCloudSecurity #TallyVPSSecurity #TallyTroubleshooting #TallyPerformance #TallyConfiguration #TallySupport #AccountingSoftware #CloudAccounting #TallyRemoteConnection