Hi!
I have the issue of having our SBS moved to a server hotel where it only has
a network plug and a certain amount of ports that is opened to it from
outside Internet. I tried to run CEICW and told it that the server was hooked
directly to the Internet, as the firewall doesn't have any IP address.

Having only one NIC (the onboard one) in the SBS, I was prompted to insert
yet another one in order for the server to accept the new Internet
connectivity method. When having done this, I had yet another trouble and
that was that I could not access the file shares that I had created on the
server. I have tried to access the file shares from both Vista Business,
Vista Ultimate as well as Vista Home Premium machines. Some of them were
connected to the domain of which the SBS is the DC.

Now, when I try to connect to the VPN connection through which I use the
server, I succeed. Exchange is working perfectly across this VPN link, as
well as WSUS 3.0. However not the file shares.

CEICW prompted me to insert yet another NIC and so I did, but as there was
no LAN to hook it up to, it is still left unplugged. The network connection
that is to be connecting the server to the presumed LAN is hence
disconnected. Might this be the reason for me not being able to access the
files on the server? If yes, how do I change the settings in the CEICW or in
another spot of the server in order for the file shares to become accessible
again?

A funny thing that I think is extremely peculiar is that when I tried to
connect from a Vista Home Premium machine, and typed \\FQDN\share name, I
actually succeeded in getting a connection to the server shares and I could
see and read them. When I connect from a domain connected computer however,
it only tells me that I cannot access the file share. If I instead type
\\[Server internal IP]\share name I get the same result, so I start to think
that there is something seriously wrong with the config.

Does anyone have any good input?

Re: SBS at server hotel by Leythos

Leythos
Wed May 07 12:33:44 PDT 2008

In article <39999885-564F-4994-A351-002603D4B231@microsoft.com>,
RichardJohanssonParnasso@discussions.microsoft.com says...
> Hi!
> I have the issue of having our SBS moved to a server hotel where it only has
> a network plug and a certain amount of ports that is opened to it from
> outside Internet. I tried to run CEICW and told it that the server was hooked
> directly to the Internet, as the firewall doesn't have any IP address.
>
> Having only one NIC (the onboard one) in the SBS, I was prompted to insert
> yet another one in order for the server to accept the new Internet
> connectivity method. When having done this, I had yet another trouble and
> that was that I could not access the file shares that I had created on the
> server. I have tried to access the file shares from both Vista Business,
> Vista Ultimate as well as Vista Home Premium machines. Some of them were
> connected to the domain of which the SBS is the DC.
>
> Now, when I try to connect to the VPN connection through which I use the
> server, I succeed. Exchange is working perfectly across this VPN link, as
> well as WSUS 3.0. However not the file shares.
>
> CEICW prompted me to insert yet another NIC and so I did, but as there was
> no LAN to hook it up to, it is still left unplugged. The network connection
> that is to be connecting the server to the presumed LAN is hence
> disconnected. Might this be the reason for me not being able to access the
> files on the server? If yes, how do I change the settings in the CEICW or in
> another spot of the server in order for the file shares to become accessible
> again?
>
> A funny thing that I think is extremely peculiar is that when I tried to
> connect from a Vista Home Premium machine, and typed \\FQDN\share name, I
> actually succeeded in getting a connection to the server shares and I could
> see and read them. When I connect from a domain connected computer however,
> it only tells me that I cannot access the file share. If I instead type
> \\[Server internal IP]\share name I get the same result, so I start to think
> that there is something seriously wrong with the config.
>
> Does anyone have any good input?

Yea, you did it all wrong.

Purchase a firewall appliance, one that also acts as a VPN server
endpoint. Remove all but one NIC, install firewall appliance, setup
rules in firewall to allow needed inbound connections, setup firewall
appliance to allow you to VPN into the firewall appliance, setup
firewall rules to allow VPN authenticated firewall users to access ALL
ports on LAN. Set SBS single NIC to be on LAN side of firewall.

Now, you remotely VPN into firewall, then you can run a batch file to
connect to your SBS file shares, like you were sitting in the same room,
and reach everything.

You could also use RWW and just allow mapping of your drive to the
server.

--
- Igitur qui desiderat pacem, praeparet bellum.
- Calling an illegal alien an "undocumented worker" is like calling a
drug dealer an "unlicensed pharmacist"
spam999free@rrohio.com (remove 999 for proper email address)