Succesfully created a MSDE 2000 rel A backend on 2003
server. I can connect a MS Access project frontend to it
from an XP client on the same LAN segment. I can connect
the same frontend over the internet to this server when
set out in the firewall's DMZ.
And now for my next trick! When I tuck the MSDE server
back behind the firewall and open up TCP and UDP ports at
1433 and 1434 for both incoming and outgoing traffic, I
cannot connect. I include a filtered log showing traffic
between the Access client on the Internet and the firewall
for detail. It appears that the Netgear firewall passes
packets to the server but it times out in a little less
than a minute... I am looking forward to any ideas that
may move this project forward!
TimeProtocolSrcDstApplication
Message
13:58:28UDP645521434ms-sql-m
[Service access request successful]
13:58:28TCP645532418cas[Access
Policy not found, dropping packet]
13:58:31TCP645532418cas[Access
Policy not found, dropping packet]
13:58:37TCP645532418cas[Access
Policy not found, dropping packet]
13:58:51TCP645582418cas[Access
Policy not found, dropping packet]
13:58:54TCP645582418cas[Access
Policy not found, dropping packet]
13:59:00TCP645582418cas[Access
Policy not found, dropping packet]
13:59:14TCP64564445ms-ds[Access
Policy not found, dropping packet]
13:59:14TCP64565139netbios-ssn
[Access Policy not found, dropping packet]
13:59:17TCP64565139netbios-ssn
[Access Policy not found, dropping packet]
13:59:17TCP64564445ms-ds[Access
Policy not found, dropping packet]
13:59:20UDP645521434ms-sql-m
[Connection timed out.Bytes transferred : 137]
13:59:23TCP64565139netbios-ssn
[Access Policy not found, dropping packet]
13:59:23TCP64564445ms-ds[Access
Policy not found, dropping packet]
From your trace it appears that many more IP ports (than 1433 & 1434) are
being attempted to be used.
I suspect it's failing because of the attempt to do name resolution.
Steve
"Ed Morra" <ed@.orl-inc.com> wrote in message
news:36f801c4297b$6a642240$a601280a@.phx.gbl...
> Succesfully created a MSDE 2000 rel A backend on 2003
> server. I can connect a MS Access project frontend to it
> from an XP client on the same LAN segment. I can connect
> the same frontend over the internet to this server when
> set out in the firewall's DMZ.
> And now for my next trick! When I tuck the MSDE server
> back behind the firewall and open up TCP and UDP ports at
> 1433 and 1434 for both incoming and outgoing traffic, I
> cannot connect. I include a filtered log showing traffic
> between the Access client on the Internet and the firewall
> for detail. It appears that the Netgear firewall passes
> packets to the server but it times out in a little less
> than a minute... I am looking forward to any ideas that
> may move this project forward!
> Time Protocol Src Dst Application
> Message
> 13:58:28 UDP 64552 1434 ms-sql-m
> [Service access request successful]
> 13:58:28 TCP 64553 2418 cas [Access
> Policy not found, dropping packet]
> 13:58:31 TCP 64553 2418 cas [Access
> Policy not found, dropping packet]
> 13:58:37 TCP 64553 2418 cas [Access
> Policy not found, dropping packet]
> 13:58:51 TCP 64558 2418 cas [Access
> Policy not found, dropping packet]
> 13:58:54 TCP 64558 2418 cas [Access
> Policy not found, dropping packet]
> 13:59:00 TCP 64558 2418 cas [Access
> Policy not found, dropping packet]
> 13:59:14 TCP 64564 445 ms-ds [Access
> Policy not found, dropping packet]
> 13:59:14 TCP 64565 139 netbios-ssn
> [Access Policy not found, dropping packet]
> 13:59:17 TCP 64565 139 netbios-ssn
> [Access Policy not found, dropping packet]
> 13:59:17 TCP 64564 445 ms-ds [Access
> Policy not found, dropping packet]
> 13:59:20 UDP 64552 1434 ms-sql-m
> [Connection timed out.Bytes transferred : 137]
> 13:59:23 TCP 64565 139 netbios-ssn
> [Access Policy not found, dropping packet]
> 13:59:23 TCP 64564 445 ms-ds [Access
> Policy not found, dropping packet]
>
Showing posts with label backend. Show all posts
Showing posts with label backend. Show all posts
Wednesday, March 21, 2012
MSDE over firewall
Succesfully created a MSDE 2000 rel A backend on 2003
server. I can connect a MS Access project frontend to it
from an XP client on the same LAN segment. I can connect
the same frontend over the internet to this server when
set out in the firewall's DMZ.
And now for my next trick! When I tuck the MSDE server
back behind the firewall and open up TCP and UDP ports at
1433 and 1434 for both incoming and outgoing traffic, I
cannot connect. I include a filtered log showing traffic
between the Access client on the Internet and the firewall
for detail. It appears that the Netgear firewall passes
packets to the server but it times out in a little less
than a minute... I am looking forward to any ideas that
may move this project forward!
Time Protocol Src Dst Application
Message
13:58:28 UDP 64552 1434 ms-sql-m
[Service access request successful]
13:58:28 TCP 64553 2418 cas [Access
Policy not found, dropping packet]
13:58:31 TCP 64553 2418 cas [Access
Policy not found, dropping packet]
13:58:37 TCP 64553 2418 cas [Access
Policy not found, dropping packet]
13:58:51 TCP 64558 2418 cas [Access
Policy not found, dropping packet]
13:58:54 TCP 64558 2418 cas [Access
Policy not found, dropping packet]
13:59:00 TCP 64558 2418 cas [Access
Policy not found, dropping packet]
13:59:14 TCP 64564 445 ms-ds [Access
Policy not found, dropping packet]
13:59:14 TCP 64565 139 netbios-ssn
[Access Policy not found, dropping packet]
13:59:17 TCP 64565 139 netbios-ssn
[Access Policy not found, dropping packet]
13:59:17 TCP 64564 445 ms-ds [Access
Policy not found, dropping packet]
13:59:20 UDP 64552 1434 ms-sql-m
[Connection timed out.Bytes transferred : 137]
13:59:23 TCP 64565 139 netbios-ssn
[Access Policy not found, dropping packet]
13:59:23 TCP 64564 445 ms-ds [Access
Policy not found, dropping packet]From your trace it appears that many more IP ports (than 1433 & 1434) are
being attempted to be used.
I suspect it's failing because of the attempt to do name resolution.
Steve
"Ed Morra" <ed@.orl-inc.com> wrote in message
news:36f801c4297b$6a642240$a601280a@.phx.gbl...
> Succesfully created a MSDE 2000 rel A backend on 2003
> server. I can connect a MS Access project frontend to it
> from an XP client on the same LAN segment. I can connect
> the same frontend over the internet to this server when
> set out in the firewall's DMZ.
> And now for my next trick! When I tuck the MSDE server
> back behind the firewall and open up TCP and UDP ports at
> 1433 and 1434 for both incoming and outgoing traffic, I
> cannot connect. I include a filtered log showing traffic
> between the Access client on the Internet and the firewall
> for detail. It appears that the Netgear firewall passes
> packets to the server but it times out in a little less
> than a minute... I am looking forward to any ideas that
> may move this project forward!
> Time Protocol Src Dst Application
> Message
> 13:58:28 UDP 64552 1434 ms-sql-m
> [Service access request successful]
> 13:58:28 TCP 64553 2418 cas [Access
> Policy not found, dropping packet]
> 13:58:31 TCP 64553 2418 cas [Access
> Policy not found, dropping packet]
> 13:58:37 TCP 64553 2418 cas [Access
> Policy not found, dropping packet]
> 13:58:51 TCP 64558 2418 cas [Access
> Policy not found, dropping packet]
> 13:58:54 TCP 64558 2418 cas [Access
> Policy not found, dropping packet]
> 13:59:00 TCP 64558 2418 cas [Access
> Policy not found, dropping packet]
> 13:59:14 TCP 64564 445 ms-ds [Access
> Policy not found, dropping packet]
> 13:59:14 TCP 64565 139 netbios-ssn
> [Access Policy not found, dropping packet]
> 13:59:17 TCP 64565 139 netbios-ssn
> [Access Policy not found, dropping packet]
> 13:59:17 TCP 64564 445 ms-ds [Access
> Policy not found, dropping packet]
> 13:59:20 UDP 64552 1434 ms-sql-m
> [Connection timed out.Bytes transferred : 137]
> 13:59:23 TCP 64565 139 netbios-ssn
> [Access Policy not found, dropping packet]
> 13:59:23 TCP 64564 445 ms-ds [Access
> Policy not found, dropping packet]
>
server. I can connect a MS Access project frontend to it
from an XP client on the same LAN segment. I can connect
the same frontend over the internet to this server when
set out in the firewall's DMZ.
And now for my next trick! When I tuck the MSDE server
back behind the firewall and open up TCP and UDP ports at
1433 and 1434 for both incoming and outgoing traffic, I
cannot connect. I include a filtered log showing traffic
between the Access client on the Internet and the firewall
for detail. It appears that the Netgear firewall passes
packets to the server but it times out in a little less
than a minute... I am looking forward to any ideas that
may move this project forward!
Time Protocol Src Dst Application
Message
13:58:28 UDP 64552 1434 ms-sql-m
[Service access request successful]
13:58:28 TCP 64553 2418 cas [Access
Policy not found, dropping packet]
13:58:31 TCP 64553 2418 cas [Access
Policy not found, dropping packet]
13:58:37 TCP 64553 2418 cas [Access
Policy not found, dropping packet]
13:58:51 TCP 64558 2418 cas [Access
Policy not found, dropping packet]
13:58:54 TCP 64558 2418 cas [Access
Policy not found, dropping packet]
13:59:00 TCP 64558 2418 cas [Access
Policy not found, dropping packet]
13:59:14 TCP 64564 445 ms-ds [Access
Policy not found, dropping packet]
13:59:14 TCP 64565 139 netbios-ssn
[Access Policy not found, dropping packet]
13:59:17 TCP 64565 139 netbios-ssn
[Access Policy not found, dropping packet]
13:59:17 TCP 64564 445 ms-ds [Access
Policy not found, dropping packet]
13:59:20 UDP 64552 1434 ms-sql-m
[Connection timed out.Bytes transferred : 137]
13:59:23 TCP 64565 139 netbios-ssn
[Access Policy not found, dropping packet]
13:59:23 TCP 64564 445 ms-ds [Access
Policy not found, dropping packet]From your trace it appears that many more IP ports (than 1433 & 1434) are
being attempted to be used.
I suspect it's failing because of the attempt to do name resolution.
Steve
"Ed Morra" <ed@.orl-inc.com> wrote in message
news:36f801c4297b$6a642240$a601280a@.phx.gbl...
> Succesfully created a MSDE 2000 rel A backend on 2003
> server. I can connect a MS Access project frontend to it
> from an XP client on the same LAN segment. I can connect
> the same frontend over the internet to this server when
> set out in the firewall's DMZ.
> And now for my next trick! When I tuck the MSDE server
> back behind the firewall and open up TCP and UDP ports at
> 1433 and 1434 for both incoming and outgoing traffic, I
> cannot connect. I include a filtered log showing traffic
> between the Access client on the Internet and the firewall
> for detail. It appears that the Netgear firewall passes
> packets to the server but it times out in a little less
> than a minute... I am looking forward to any ideas that
> may move this project forward!
> Time Protocol Src Dst Application
> Message
> 13:58:28 UDP 64552 1434 ms-sql-m
> [Service access request successful]
> 13:58:28 TCP 64553 2418 cas [Access
> Policy not found, dropping packet]
> 13:58:31 TCP 64553 2418 cas [Access
> Policy not found, dropping packet]
> 13:58:37 TCP 64553 2418 cas [Access
> Policy not found, dropping packet]
> 13:58:51 TCP 64558 2418 cas [Access
> Policy not found, dropping packet]
> 13:58:54 TCP 64558 2418 cas [Access
> Policy not found, dropping packet]
> 13:59:00 TCP 64558 2418 cas [Access
> Policy not found, dropping packet]
> 13:59:14 TCP 64564 445 ms-ds [Access
> Policy not found, dropping packet]
> 13:59:14 TCP 64565 139 netbios-ssn
> [Access Policy not found, dropping packet]
> 13:59:17 TCP 64565 139 netbios-ssn
> [Access Policy not found, dropping packet]
> 13:59:17 TCP 64564 445 ms-ds [Access
> Policy not found, dropping packet]
> 13:59:20 UDP 64552 1434 ms-sql-m
> [Connection timed out.Bytes transferred : 137]
> 13:59:23 TCP 64565 139 netbios-ssn
> [Access Policy not found, dropping packet]
> 13:59:23 TCP 64564 445 ms-ds [Access
> Policy not found, dropping packet]
>
Wednesday, March 7, 2012
MSDE Installation and usage on client PC. URGENT HELP!
Hi All,
Have developed Client/Server (VB.NET) application with SQL Server 2000
backend engine. It is working fine. This application can connect to
Database engine if user in our LAN or WAN.
Now, my users need to work on application while they are not in our
network. For instance from Hotel, travel etc.. To achieve this, I
thought to have MSDE installed on user's laptop and get copy of SQL 2k
DB on user machine. But. here I got stuck !. Woudl really appreciate if
you could help me !
MSDE engine, I hope that I can d/load from MS site. Belive that can be
installed easly like other MS application. Upon installation, how can I
get my SQL 2K DB attached or Sychronized ?
What about login id (like "sa") to connect to MSDE engine from my
applciation. I will modify my application user to choose DB engine LOCAL
or LAN. If LAN, I will use my existing connection string. But, LOCAL,
what would be the provider, password, user id etc..
Never user MSDE, so queries will be bit more.
Appreciate all your help to get this resolved.
Many thanks in advance..
Regards,
AJ
*** Sent via Developersdex http://www.developersdex.com ***You have to setup some replication, please refer to the BOL or ressources in
the internet for that, there are tons of examples out there.
HTH, Jens SUessmeyer.
--
http://www.sqlserver2005.de
--
"Ahmed Jewahar" <ahmed.jewahar@.dhl.com> schrieb im Newsbeitrag
news:%23klgAGhWFHA.3280@.TK2MSFTNGP09.phx.gbl...
> Hi All,
> Have developed Client/Server (VB.NET) application with SQL Server 2000
> backend engine. It is working fine. This application can connect to
> Database engine if user in our LAN or WAN.
> Now, my users need to work on application while they are not in our
> network. For instance from Hotel, travel etc.. To achieve this, I
> thought to have MSDE installed on user's laptop and get copy of SQL 2k
> DB on user machine. But. here I got stuck !. Woudl really appreciate if
> you could help me !
> MSDE engine, I hope that I can d/load from MS site. Belive that can be
> installed easly like other MS application. Upon installation, how can I
> get my SQL 2K DB attached or Sychronized ?
> What about login id (like "sa") to connect to MSDE engine from my
> applciation. I will modify my application user to choose DB engine LOCAL
> or LAN. If LAN, I will use my existing connection string. But, LOCAL,
> what would be the provider, password, user id etc..
> Never user MSDE, so queries will be bit more.
> Appreciate all your help to get this resolved.
> Many thanks in advance..
> Regards,
> AJ
>
>
> *** Sent via Developersdex http://www.developersdex.com ***
Have developed Client/Server (VB.NET) application with SQL Server 2000
backend engine. It is working fine. This application can connect to
Database engine if user in our LAN or WAN.
Now, my users need to work on application while they are not in our
network. For instance from Hotel, travel etc.. To achieve this, I
thought to have MSDE installed on user's laptop and get copy of SQL 2k
DB on user machine. But. here I got stuck !. Woudl really appreciate if
you could help me !
MSDE engine, I hope that I can d/load from MS site. Belive that can be
installed easly like other MS application. Upon installation, how can I
get my SQL 2K DB attached or Sychronized ?
What about login id (like "sa") to connect to MSDE engine from my
applciation. I will modify my application user to choose DB engine LOCAL
or LAN. If LAN, I will use my existing connection string. But, LOCAL,
what would be the provider, password, user id etc..
Never user MSDE, so queries will be bit more.
Appreciate all your help to get this resolved.
Many thanks in advance..
Regards,
AJ
*** Sent via Developersdex http://www.developersdex.com ***You have to setup some replication, please refer to the BOL or ressources in
the internet for that, there are tons of examples out there.
HTH, Jens SUessmeyer.
--
http://www.sqlserver2005.de
--
"Ahmed Jewahar" <ahmed.jewahar@.dhl.com> schrieb im Newsbeitrag
news:%23klgAGhWFHA.3280@.TK2MSFTNGP09.phx.gbl...
> Hi All,
> Have developed Client/Server (VB.NET) application with SQL Server 2000
> backend engine. It is working fine. This application can connect to
> Database engine if user in our LAN or WAN.
> Now, my users need to work on application while they are not in our
> network. For instance from Hotel, travel etc.. To achieve this, I
> thought to have MSDE installed on user's laptop and get copy of SQL 2k
> DB on user machine. But. here I got stuck !. Woudl really appreciate if
> you could help me !
> MSDE engine, I hope that I can d/load from MS site. Belive that can be
> installed easly like other MS application. Upon installation, how can I
> get my SQL 2K DB attached or Sychronized ?
> What about login id (like "sa") to connect to MSDE engine from my
> applciation. I will modify my application user to choose DB engine LOCAL
> or LAN. If LAN, I will use my existing connection string. But, LOCAL,
> what would be the provider, password, user id etc..
> Never user MSDE, so queries will be bit more.
> Appreciate all your help to get this resolved.
> Many thanks in advance..
> Regards,
> AJ
>
>
> *** Sent via Developersdex http://www.developersdex.com ***
Saturday, February 25, 2012
MSDE included as part of ASP.NET deployment package?
I need to design an asp.net application w/ and MSDE backend database that will be deployed at 50 different location (unrelated to each other). The application's deployment package needs to be downloaded from a web site on the internet. The end user locations do not have SQL2000 or MSDE...some have access.
I want to know if my deployment package can include the MSDE software? Or, can anyone offer ideas on the EASIEST way for these small offices to get MSDE installed on each of their servers so that my ASP.NET applications will connect to via ado.net.
Thanks for any ideas.I believe you can include it in your deployment package so long as its use at each location is consistent with the MSDE licensing agreement.
Appropriate uses of MSDE
Subscribe to:
Posts (Atom)