File I/O on DMZ

V

Vai2000

Hi All, I have couple of servers in DMZ , I need to do some File I/O on them
from my internal servers...The File I/O are going to be quite large so
obviating WebService option (not sure about Remoting....)
What alternatives do I have which come canned? Don't wanna write a server or
client code....can we use some inbuilt Win2k3 API's???? BTW DMZ's are
strictly provisioned no major policy changes...

My DMZ's servers are Win2k3 (Web Ed)
Internal Servers are Win2k

TIA
 
W

Willy Denoyette [MVP]

| Hi All, I have couple of servers in DMZ , I need to do some File I/O on
them
| from my internal servers...The File I/O are going to be quite large so
| obviating WebService option (not sure about Remoting....)
| What alternatives do I have which come canned? Don't wanna write a server
or
| client code....can we use some inbuilt Win2k3 API's???? BTW DMZ's are
| strictly provisioned no major policy changes...
|
| My DMZ's servers are Win2k3 (Web Ed)
| Internal Servers are Win2k
|
| TIA
|
|

What exactly do you mean with File I/O, if you mean file transfer,use FTP
(port 21). If you mean programmed File I/O, your only option is the use the
standard Windows Client/Server protocol (SMB) for which you need to open TCP
ports 139 and 445, note that you should configure your inner FW to only
allow trafic from your internal network.

Willy.
 
V

Vai2000

Great thanks, I was looking forward for creating files etc...to varied file
folder locations....unfortunately FTP is prohibited on this Box.
 
V

Vai2000

After enabling SMB how to proceed...?


Vai2000 said:
Great thanks, I was looking forward for creating files etc...to varied file
folder locations....unfortunately FTP is prohibited on this Box.
 
W

Willy Denoyette [MVP]

Any network/system admins in the house? You need to ask them to configure
the FW, you need at least to open the TCP ports 139 and 445 and the UDP
ports 137 and 138 and allow the internal network server(s) IP addresses.
When done you need to make sure you can access the perimeter network over
TCP/IP.
Share the directory you want to access from the client(s). Create a shadow
acount, that is an account with the same credentials as on the client and
grant R/W access to the share to this account.
From the client, running as or impersonating the shadow account, you can
access the share for file i/o by using all framework file IO classes.


Willy.

| After enabling SMB how to proceed...?
|
|
| | > Great thanks, I was looking forward for creating files etc...to varied
| file
| > folder locations....unfortunately FTP is prohibited on this Box.
| >
| > | > >
| > > | > > | Hi All, I have couple of servers in DMZ , I need to do some File I/O
| on
| > > them
| > > | from my internal servers...The File I/O are going to be quite large
so
| > > | obviating WebService option (not sure about Remoting....)
| > > | What alternatives do I have which come canned? Don't wanna write a
| > server
| > > or
| > > | client code....can we use some inbuilt Win2k3 API's???? BTW DMZ's
are
| > > | strictly provisioned no major policy changes...
| > > |
| > > | My DMZ's servers are Win2k3 (Web Ed)
| > > | Internal Servers are Win2k
| > > |
| > > | TIA
| > > |
| > > |
| > >
| > > What exactly do you mean with File I/O, if you mean file transfer,use
| FTP
| > > (port 21). If you mean programmed File I/O, your only option is the
use
| > the
| > > standard Windows Client/Server protocol (SMB) for which you need to
open
| > TCP
| > > ports 139 and 445, note that you should configure your inner FW to
only
| > > allow trafic from your internal network.
| > >
| > > Willy.
| > >
| > >
| >
| >
|
|
 
V

Vai2000

Thanks, though like I said the servers are in DMZ so they are not part of
ANY Domains...
 
W

Willy Denoyette [MVP]

| Thanks, though like I said the servers are in DMZ so they are not part of
| ANY Domains...
|
|

So what? You don't need a Domain, that's why I explained to create a shadow
account, right?.

Willy.

| | > Any network/system admins in the house? You need to ask them to
configure
| > the FW, you need at least to open the TCP ports 139 and 445 and the UDP
| > ports 137 and 138 and allow the internal network server(s) IP addresses.
| > When done you need to make sure you can access the perimeter network
over
| > TCP/IP.
| > Share the directory you want to access from the client(s). Create a
shadow
| > acount, that is an account with the same credentials as on the client
and
| > grant R/W access to the share to this account.
| > From the client, running as or impersonating the shadow account, you can
| > access the share for file i/o by using all framework file IO classes.
| >
| >
| > Willy.
| >
| > | > | After enabling SMB how to proceed...?
| > |
| > |
| > | | > | > Great thanks, I was looking forward for creating files etc...to
varied
| > | file
| > | > folder locations....unfortunately FTP is prohibited on this Box.
| > | >
message
| > | > | > | > >
| > | > > | > | > > | Hi All, I have couple of servers in DMZ , I need to do some File
| I/O
| > | on
| > | > > them
| > | > > | from my internal servers...The File I/O are going to be quite
| large
| > so
| > | > > | obviating WebService option (not sure about Remoting....)
| > | > > | What alternatives do I have which come canned? Don't wanna write
a
| > | > server
| > | > > or
| > | > > | client code....can we use some inbuilt Win2k3 API's???? BTW
DMZ's
| > are
| > | > > | strictly provisioned no major policy changes...
| > | > > |
| > | > > | My DMZ's servers are Win2k3 (Web Ed)
| > | > > | Internal Servers are Win2k
| > | > > |
| > | > > | TIA
| > | > > |
| > | > > |
| > | > >
| > | > > What exactly do you mean with File I/O, if you mean file
| transfer,use
| > | FTP
| > | > > (port 21). If you mean programmed File I/O, your only option is
the
| > use
| > | > the
| > | > > standard Windows Client/Server protocol (SMB) for which you need
to
| > open
| > | > TCP
| > | > > ports 139 and 445, note that you should configure your inner FW to
| > only
| > | > > allow trafic from your internal network.
| > | > >
| > | > > Willy.
| > | > >
| > | > >
| > | >
| > | >
| > |
| > |
| >
| >
|
|
 
V

Vai2000

Thanks a bunch my friend

Willy Denoyette said:
| Thanks, though like I said the servers are in DMZ so they are not part of
| ANY Domains...
|
|

So what? You don't need a Domain, that's why I explained to create a shadow
account, right?.

Willy.

| | > Any network/system admins in the house? You need to ask them to
configure
| > the FW, you need at least to open the TCP ports 139 and 445 and the UDP
| > ports 137 and 138 and allow the internal network server(s) IP addresses.
| > When done you need to make sure you can access the perimeter network
over
| > TCP/IP.
| > Share the directory you want to access from the client(s). Create a
shadow
| > acount, that is an account with the same credentials as on the client
and
| > grant R/W access to the share to this account.
| > From the client, running as or impersonating the shadow account, you can
| > access the share for file i/o by using all framework file IO classes.
| >
| >
| > Willy.
| >
| > | > | After enabling SMB how to proceed...?
| > |
| > |
| > | | > | > Great thanks, I was looking forward for creating files etc...to
varied
| > | file
| > | > folder locations....unfortunately FTP is prohibited on this Box.
| > | >
message
| > | > | > | > >
| > | > > | > | > > | Hi All, I have couple of servers in DMZ , I need to do some File
| I/O
| > | on
| > | > > them
| > | > > | from my internal servers...The File I/O are going to be quite
| large
| > so
| > | > > | obviating WebService option (not sure about Remoting....)
| > | > > | What alternatives do I have which come canned? Don't wanna write
a
| > | > server
| > | > > or
| > | > > | client code....can we use some inbuilt Win2k3 API's???? BTW
DMZ's
| > are
| > | > > | strictly provisioned no major policy changes...
| > | > > |
| > | > > | My DMZ's servers are Win2k3 (Web Ed)
| > | > > | Internal Servers are Win2k
| > | > > |
| > | > > | TIA
| > | > > |
| > | > > |
| > | > >
| > | > > What exactly do you mean with File I/O, if you mean file
| transfer,use
| > | FTP
| > | > > (port 21). If you mean programmed File I/O, your only option is
the
| > use
| > | > the
| > | > > standard Windows Client/Server protocol (SMB) for which you need
to
| > open
| > | > TCP
| > | > > ports 139 and 445, note that you should configure your inner FW to
| > only
| > | > > allow trafic from your internal network.
| > | > >
| > | > > Willy.
| > | > >
| > | > >
| > | >
| > | >
| > |
| > |
| >
| >
|
|
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top