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!
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]
>

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]
>

MSDE installed succesfully but there is no instancename folder

Hello
I finally managed to install MSDE after more than 20 attempts. The strange
thing is, there was no error during the installation, but there is no
instance name folder.
I used this command to install: setup.exe instancename="name" blanksapwd=1
securitymode=sql /L*v C:\MSDE_setup.log targetdir="c:\msde\"
There is even no C:\msde folder, the instancename isn't mentioned in the
registry, but my log file says that the installation operation was completed
successfully. This means also that my dropdown lists in the sql server
service manger are empty, because it can't find back the services that are
needed.
What did I do wrong? I hope that anyone can help me
"pluno" <pluno@.discussions.microsoft.com> ha scritto nel messaggio
news:63434B7B-ED9D-4F6E-BC63-7E1535BEBF2C@.microsoft.com
> Hello
> I finally managed to install MSDE after more than 20 attempts. The
> strange thing is, there was no error during the installation, but
> there is no instance name folder.
> I used this command to install: setup.exe instancename="name"
> blanksapwd=1 securitymode=sql /L*v C:\MSDE_setup.log
> targetdir="c:\msde\"
> There is even no C:\msde folder, the instancename isn't mentioned in
> the registry, but my log file says that the installation operation
> was completed successfully. This means also that my dropdown lists in
> the sql server service manger are empty, because it can't find back
> the services that are needed.
> What did I do wrong? I hope that anyone can help me
have a look at \program files\Microsoft SQL Server\MSSQL$name
as /L*v parameter expects it's value enclosed in "...", perhaps TARGETDIR
has not been honored..
just a guess...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply