• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Windows 2003 Server Question.

R

rschwab

Junior Member
I have a Windows 2003 server at home and I can't connect to it remotely. The only way that I can connect to it is going through my home pc and then going from it to the server. I have 2 nic cards in the server one goes to the router and the other goes to an outside connection. It does have an IP address and I did set the settings to allow it to be controlled by mstsc.exe. Below is the IPCONFIG /all it shows my two ethernet adapters connection. 1st one is the one that goes to my router and the second is the one that goes outside of it. I noticed that it is missing the "Gateway", could that have something to do with it?? Thanks a lot for your help, bye.

Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 3Com 3C920 Integrated Fast Ethernet Controller (3C905C-TX Compatible)
Physical Address. . . . . . . . . : 00-B0-D0-61-CC-7F
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.105
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 64.233.222.2
64.233.222.7
64.233.222.7

Ethernet adapter WowWay:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 3Com EtherLink XL 10/100 PCI TX NIC (3C905B-TX)
Physical Address. . . . . . . . . : 00-10-4B-70-59-B0
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 67.149.145.XXX(I Put the XXX in there)
Subnet Mask . . . . . . . . . . . : 255.255.248.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 64.233.222.2
64.233.222.7
The IP above is the one I can't remotely connect to. I assume it's something I forgot to enable. So please help me out, thanks.
 
Default Gateway is the route for all outbound TCP/IP traffic. You can only have one per TCP/IP stack (not per adapter).
I'm wondering if your traffic is doing a circle, and so failing:
You contact WowWay, the server responds throught the LAN connection/router, attempts to reach you that way.
Handshake fails because...
IP address mismatch (external on the send, vs NATted on the reply)
Replies never make it (LAN connection can't pass traffic back to your client...or port is blocked by router/FW)
?
You could try adding a route (on the server), telling it to send all traffic destined for your (remote) client out the WowWay connection.
 
Is there a technical name for, "You could try adding a route (on the server), telling it to send all traffic destined for your (remote) client out the WowWay connection.

"? I have no idea as to how to do that.
 
I am going to take some screen captures of my settings and show them to you. Is there any thing in per teckular(missspelled i know) that you would like to see? And thanks again for your help.
 
I'm not sure why you have set up the network the way you have. Normally, you'd hook up Windows Server to your router, forward all important ports to the Server, and then let the Server route things to your client computers, connected on the second NIC.

If all you want to do is access your Server remotely, attach the external NIC to the router, assign the NIC a static IP address and have the router forward all incoming port 3389 packets to Server's external NIC IP address. Then enable Remote Desktop Administration on the Server.
 
You have no default gateway on your external interface. Not going anywhere like that.

You can add routes but I would suggest setting it up the opposite of what you have.
Put a GW on the outside interface and remove it from the inside.
 
Tell more about your network setup.


Two interfaces right..

The 192 interface:
Both 2003 and XP box on this network?
Connected by hub? cable/dsl router? ... if so, what is router connected to.

The 67 interface:
Directly to cable/dsl modem?
Any router/hub/switch/firewall inbetween?

I'm trying to get a "napkin diagram" in my head of what you have there.
 
Hey I figured it out thanks you your help everyone. I did some windows updates and it turned the firewall and some other settings back on. So I had to disable the firewall again and change a few other things. Thanks for you help. Rich.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top