Re: Remote Desktop Problem

Here's the new configuration below...and when I try to change the Wan IP to
192.168.2.x a warning appears talking about the default gateway is not on the
same network segment (subnet) that is defined by the IP address and the
subnet mask. Does this mean I can only change the Lan IP to .2.x?

Windows IP Configuration
Host Name . . . . . . . . . . . . : TK-SERVER
Primary Dns Suffix . . . . . . . : trivedikatz.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : trivedikatz.local

Ethernet adapter Internal LAN:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VIA VT6105 Rhine III Compatible Fast
Ethe
rnet Adapter
Physical Address. . . . . . . . . : 00-13-46-78-1B-C7
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.11
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 192.168.1.11
Primary WINS Server . . . . . . . : 192.168.1.11
NetBIOS over Tcpip. . . . . . . . : Disabled

Ethernet adapter WAN:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
Physical Address. . . . . . . . . : 00-13-72-3D-C9-C6
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.10
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.2
DNS Servers . . . . . . . . . . . : 192.168.1.11
NetBIOS over Tcpip. . . . . . . . : Disabled





"HelpinFL" wrote:

And the Firebox...it needs to point to the internal NIC right?

"Frank McCallister SBS MVP" wrote:

Your Internal and External NICs are on the Same subnet and that won't work.
Change the LAN NIC to a different range (The Default is 192.168.16.2) and
the point DNS only to the LAN IP on both NICS. See Diagram at
http://www.smallbizserver.net/tabid/266/articleType/ArticleView/articleId/76/Two-Nics-a-static-IP-address-ISA-router.aspx
(Ignore the ISA parts if using Standard)

--
Frank McCallister SBS MVP
MCP Microsoft Small Business Specialist
COMPUMAC
"HelpinFL" <HelpinFL@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B3A9BAE2-6C00-4931-84BD-A2480E09CC10@xxxxxxxxxxxxxxxx
There has been many questions regarding the same issue, but unfortunately
none of the answers given so far have helped me.
First the logistics...
Static IP of 65.40.x.x, 2 NIC, 1 Wireless Router and 1 Firebox X Edge
IPConfig -all returns the following...
Windows IP Configuration
Host Name . . . . . . . . . . . . : TK-SERVER
Primary Dns Suffix . . . . . . . : trivedikatz.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : trivedikatz.local

Ethernet adapter Internal LAN:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VIA VT6105 Rhine III Compatible Fast
Ethe
rnet Adapter
Physical Address. . . . . . . . . : 00-13-46-78-1B-C7
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.11
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 209.26.88.31
199.2.252.10
Primary WINS Server . . . . . . . : 192.168.1.11
NetBIOS over Tcpip. . . . . . . . : Disabled

Ethernet adapter WAN:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
Physical Address. . . . . . . . . : 00-13-72-3D-C9-C6
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.10
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.2
DNS Servers . . . . . . . . . . . : 209.26.88.31
199.2.252.10
Primary WINS Server . . . . . . . : 192.168.1.10
NetBIOS over Tcpip. . . . . . . . : Disabled

DNS Servers are the ISP IP's.

Map of network...
DSL Modem >> Firebox(192.168.1.2) >> Server(WAN) and 1PC >> Wireless
Router
(1Wireless Laptop) >> Server (Internal LAN)

The question is coming it's just after reading so many threads I noticed
everything that people needed to know in order to get an answer.
Basically what happened was that I was able to connect to the server
through
the firebox and then thru the Remote Desktop one day and the next day
Remote
Desktop is not connecting. I can log into the firebox. Then I open the
pop
up for Remote Desktop which show the computer name as 192.168.1.11 as it
has
done before. After I click connect usually it goes straight thru to the
Desktop on the server asking for a User and Password, but now it says
"Client
could not conncect to remote computer and then gives the possible reasons.
I'm not exactly sure what could have changed from one day to the next.
Before I was able to login from 3 differnt remote computers without and
issue
and now nothing. The Firebox is configured to allow http into
192.168.1.11,
https into 192.168.1.11, IPSec into 192.168.1.2 and ftp into 192.168.1.10
incoming. In addition it allows RDP into port 3389 thru TCP, but it
currently says "No Rule" for the Filter. I added port 4125, but wasn't
sure
if I needed to.

I guess we can start with that. Any and all help would be awesome.



"HelpinFL" wrote:

And the Firebox...it needs to point to the internal NIC right?

"Frank McCallister SBS MVP" wrote:

Your Internal and External NICs are on the Same subnet and that won't work.
Change the LAN NIC to a different range (The Default is 192.168.16.2) and
the point DNS only to the LAN IP on both NICS. See Diagram at
http://www.smallbizserver.net/tabid/266/articleType/ArticleView/articleId/76/Two-Nics-a-static-IP-address-ISA-router.aspx
(Ignore the ISA parts if using Standard)

--
Frank McCallister SBS MVP
MCP Microsoft Small Business Specialist
COMPUMAC
"HelpinFL" <HelpinFL@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B3A9BAE2-6C00-4931-84BD-A2480E09CC10@xxxxxxxxxxxxxxxx
There has been many questions regarding the same issue, but unfortunately
none of the answers given so far have helped me.
First the logistics...
Static IP of 65.40.x.x, 2 NIC, 1 Wireless Router and 1 Firebox X Edge
IPConfig -all returns the following...
Windows IP Configuration
Host Name . . . . . . . . . . . . : TK-SERVER
Primary Dns Suffix . . . . . . . : trivedikatz.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : trivedikatz.local

Ethernet adapter Internal LAN:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VIA VT6105 Rhine III Compatible Fast
Ethe
rnet Adapter
Physical Address. . . . . . . . . : 00-13-46-78-1B-C7
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.11
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 209.26.88.31
199.2.252.10
Primary WINS Server . . . . . . . : 192.168.1.11
NetBIOS over Tcpip. . . . . . . . : Disabled

Ethernet adapter WAN:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
Physical Address. . . . . . . . . : 00-13-72-3D-C9-C6
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.10
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.2
DNS Servers . . . . . . . . . . . : 209.26.88.31
199.2.252.10
Primary WINS Server . . . . . . . : 192.168.1.10
NetBIOS over Tcpip. . . . . . . . : Disabled

DNS Servers are the ISP IP's.

Map of network...
DSL Modem >> Firebox(192.168.1.2) >> Server(WAN) and 1PC >> Wireless
Router
(1Wireless Laptop) >> Server (Internal LAN)

The question is coming it's just after reading so many threads I noticed
everything that people needed to know in order to get an answer.
Basically what happened was that I was able to connect to the server
through
the firebox and then thru the Remote Desktop one day and the next day
Remote
Desktop is not connecting. I can log into the firebox. Then I open the
pop
up for Remote Desktop which show the computer name as 192.168.1.11 as it
has
done before. After I click connect usually it goes straight thru to the
Desktop on the server asking for a User and Password, but now it says
"Client
could not conncect to remote computer and then gives the possible reasons.
I'm not exactly sure what could have changed from one day to the next.
Before I was able to login from 3 differnt remote computers without and
issue
and now nothing. The Firebox is configured to allow http into
192.168.1.11,
https into 192.168.1.11, IPSec into 192.168.1.2 and ftp into 192.168.1.10
incoming. In addition it allows RDP into port 3389 thru TCP, but it
currently says "No Rule" for the Filter. I added port 4125, but wasn't
sure
if I needed to.

I guess we can start with that. Any and all help would be awesome.





"HelpinFL" wrote:

And the Firebox...it needs to point to the internal NIC right?

"Frank McCallister SBS MVP" wrote:

Your Internal and External NICs are on the Same subnet and that won't work.
Change the LAN NIC to a different range (The Default is 192.168.16.2) and
the point DNS only to the LAN IP on both NICS. See Diagram at
http://www.smallbizserver.net/tabid/266/articleType/ArticleView/articleId/76/Two-Nics-a-static-IP-address-ISA-router.aspx
(Ignore the ISA parts if using Standard)

--
Frank McCallister SBS MVP
MCP Microsoft Small Business Specialist
COMPUMAC
"HelpinFL" <HelpinFL@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B3A9BAE2-6C00-4931-84BD-A2480E09CC10@xxxxxxxxxxxxxxxx
There has been many questions regarding the same issue, but unfortunately
none of the answers given so far have helped me.
First the logistics...
Static IP of 65.40.x.x, 2 NIC, 1 Wireless Router and 1 Firebox X Edge
IPConfig -all returns the following...
Windows IP Configuration
Host Name . . . . . . . . . . . . : TK-SERVER
Primary Dns Suffix . . . . . . . : trivedikatz.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : trivedikatz.local

Ethernet adapter Internal LAN:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VIA VT6105 Rhine III Compatible Fast
Ethe
rnet Adapter
Physical Address. . . . . . . . . : 00-13-46-78-1B-C7
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.11
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 209.26.88.31
199.2.252.10
Primary WINS Server . . . . . . . : 192.168.1.11
NetBIOS over Tcpip. . . . . . . . : Disabled

Ethernet adapter WAN:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
Physical Address. . . . . . . . . : 00-13-72-3D-C9-C6
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.10
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.2
DNS Servers . . . . . . . . . . . : 209.26.88.31
199.2.252.10
Primary WINS Server . . . . . . . : 192.168.1.10
NetBIOS over Tcpip. . . . . . . . : Disabled

DNS Servers are the ISP IP's.

Map of network...
DSL Modem >> Firebox(192.168.1.2) >> Server(WAN) and 1PC >> Wireless
Router
(1Wireless Laptop) >> Server (Internal LAN)

The question is coming it's just after reading so many threads I noticed
everything that people needed to know in order to get an answer.
Basically what happened was that I was able to connect to the server
through
the firebox and then thru the Remote Desktop one day and the next day
Remote
Desktop is not connecting. I can log into the firebox. Then I open the
pop
up for Remote Desktop which show the computer name as 192.168.1.11 as it
has
done before. After I click connect usually it goes straight thru to the
Desktop on the server asking for a User and Password, but now it says
"Client
could not conncect to remote computer and then gives the possible reasons.
I'm not exactly sure what could have changed from one day to the next.
Before I was able to login from 3 differnt remote computers without and
issue
and now nothing. The Firebox is configured to allow http into
192.168.1.11,
https into 192.168.1.11, IPSec into 192.168.1.2 and ftp into 192.168.1.10
incoming. In addition it allows RDP into port 3389 thru TCP, but it
currently says "No Rule" for the Filter. I added port 4125, but wasn't
sure
if I needed to.

I guess we can start with that. Any and all help would be awesome.



.