Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Remote connection

3 posts in Networking Last posting was on 2006-07-19 13:15:15.0Z
Advantage Posted on 2006-03-21 20:05:38.0Z
From: "Advantage" <timstone@masterlinksoftware.com>
Newsgroups: Advantage.Networking
Subject: Remote connection
Date: Tue, 21 Mar 2006 12:05:38 -0800
Lines: 19
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2670
X-RFC2646: Format=Flowed; Original
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
NNTP-Posting-Host: 68.4.154.81
Message-ID: <44205bce@solutions.advantagedatabase.com>
X-Trace: 21 Mar 2006 13:02:22 -0700, 68.4.154.81
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!68.4.154.81
Xref: solutions.advantagedatabase.com Advantage.Networking:582
Article PK: 1132005

I am trying to get a new installation up and running. There are 13
workstations at the primary location, and 4 at the remote site. The two
sites are connected by a dedicated T line, using Cisco routers. The techs
swear that the computers at the remote site are seeing the primary site and
are "on the same network / workgroup" based on how they have it configured.
They have run other programs and access data across the system as if they
were all in the same location.

My application will sense the ADS on the NT 2000 Server at the primary
location. However, at the remote sites, the program reverts to LOCAL SERVER
mode.

Theoretically this is not an internet connection ... it is a dedicated T
line connection between two nodes. Shouldn't this work ? How can I check
it ?

Tim


Mark Wilkins Posted on 2006-03-21 21:30:58.0Z
From: "Mark Wilkins" <tired@of.spam>
Newsgroups: Advantage.Networking
References: <44205bce@solutions.advantagedatabase.com>
Subject: Re: Remote connection
Date: Tue, 21 Mar 2006 14:30:58 -0700
Lines: 49
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-RFC2646: Format=Flowed; Response
NNTP-Posting-Host: 198.102.102.12
Message-ID: <44206fcc@solutions.advantagedatabase.com>
X-Trace: 21 Mar 2006 14:27:40 -0700, 198.102.102.12
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!198.102.102.12
Xref: solutions.advantagedatabase.com Advantage.Networking:583
Article PK: 1132006

Hi,

Yes it should work. My guess is that discovery is failing. If you are
trying to connect to something like h:\data\ where h: is mapped to the
remote server or if you are using UNC paths such as \\remoteserver\path,
then the client tries to discover the actual address of the server. A
couple of the most common ways are through mailslots and multicast. It is
quite possible that the routers are not allowing that information through.
Rather than trying to reconfigure the routers, it is probably better to use
a connection path of one of the following forms:

\\ip:port\path
or
\\remoteserver:port\path

In the first example, all "discovery" is eliminated and the client simply
tries to connect to the given address. In the second example, the IP
address is retrieved via DNS lookups. You can also use aliases in the
ads.ini file to specify the address. For example, if you are using UNC
paths currently, you can add the IP and port number to the ads.ini file to
avoid discovery and avoid having to rebuild your application.

HTH,
Mark Wilkins
Advantage R&D

"Advantage" <timstone@masterlinksoftware.com> wrote in message
news:44205bce@solutions.advantagedatabase.com...
>I am trying to get a new installation up and running. There are 13
>workstations at the primary location, and 4 at the remote site. The two
>sites are connected by a dedicated T line, using Cisco routers. The techs
>swear that the computers at the remote site are seeing the primary site and
>are "on the same network / workgroup" based on how they have it configured.
>They have run other programs and access data across the system as if they
>were all in the same location.
>
> My application will sense the ADS on the NT 2000 Server at the primary
> location. However, at the remote sites, the program reverts to LOCAL
> SERVER mode.
>
> Theoretically this is not an internet connection ... it is a dedicated T
> line connection between two nodes. Shouldn't this work ? How can I check
> it ?
>
> Tim
>


Maaz Rizki Posted on 2006-07-19 13:15:15.0Z
From: "Maaz Rizki" <mrizki@fairwaymarket.com>
Newsgroups: Advantage.Networking
References: <44205bce@solutions.advantagedatabase.com> <44206fcc@solutions.advantagedatabase.com>
Subject: Re: Remote connection
Date: Wed, 19 Jul 2006 09:15:15 -0400
Lines: 63
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1807
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1807
NNTP-Posting-Host: 67.106.130.227
Message-ID: <44be3047@solutions.advantagedatabase.com>
X-Trace: 19 Jul 2006 07:14:47 -0700, 67.106.130.227
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!67.106.130.227
Xref: solutions.advantagedatabase.com Advantage.Networking:629
Article PK: 1132048

I had the same problem but it was resolved as soon as I put port in my
connection strings and plus we are using IP no UNC. Don't forget to
activated port setting on ADS server site also.
MR

"Mark Wilkins" <tired@of.spam> wrote in message
news:44206fcc@solutions.advantagedatabase.com...
> Hi,
>
> Yes it should work. My guess is that discovery is failing. If you are
> trying to connect to something like h:\data\ where h: is mapped to the
> remote server or if you are using UNC paths such as \\remoteserver\path,
> then the client tries to discover the actual address of the server. A
> couple of the most common ways are through mailslots and multicast. It is
> quite possible that the routers are not allowing that information through.
> Rather than trying to reconfigure the routers, it is probably better to
use
> a connection path of one of the following forms:
>
> \\ip:port\path
> or
> \\remoteserver:port\path
>
> In the first example, all "discovery" is eliminated and the client simply
> tries to connect to the given address. In the second example, the IP
> address is retrieved via DNS lookups. You can also use aliases in the
> ads.ini file to specify the address. For example, if you are using UNC
> paths currently, you can add the IP and port number to the ads.ini file to
> avoid discovery and avoid having to rebuild your application.
>
> HTH,
> Mark Wilkins
> Advantage R&D
>
>
> "Advantage" <timstone@masterlinksoftware.com> wrote in message
> news:44205bce@solutions.advantagedatabase.com...
> >I am trying to get a new installation up and running. There are 13
> >workstations at the primary location, and 4 at the remote site. The two
> >sites are connected by a dedicated T line, using Cisco routers. The
techs
> >swear that the computers at the remote site are seeing the primary site
and
> >are "on the same network / workgroup" based on how they have it
configured.
> >They have run other programs and access data across the system as if they
> >were all in the same location.
> >
> > My application will sense the ADS on the NT 2000 Server at the primary
> > location. However, at the remote sites, the program reverts to LOCAL
> > SERVER mode.
> >
> > Theoretically this is not an internet connection ... it is a dedicated T
> > line connection between two nodes. Shouldn't this work ? How can I
check
> > it ?
> >
> > Tim
> >
>
>