mentchconsulting
asked on
Cannot connect to Remote Web Workplace on Windows SBS 2003
I have just set up a Windows SBS 2003 server and have opened the necessary ports on my Linksys WRV200 router. RDP works perfectly, but no other service works-- remote web workplace or smtp. So this means no email is getting through when someone attempts to send it to one of my users.
I have 2 NICs and have verified that they are setup properly from other threads on this site. I can access remote web workplace internally by specifying either the IP and domain, but cannot access it externally. I think if I can resolve this issue then the email problem wil be fixed too.
Anyone see this issue?
Network Connection
IP: 192.168.16.2
Subnet Mask: 255.255.255.0
Gateway: [blank]
Internal NIC
IP: 192.168.1.41
Subnet Mask: 255.255.255.0
Gateway: 192.168.1.1
Router IP: 192.168.1.1
Thanks for any help!
Chris
I have 2 NICs and have verified that they are setup properly from other threads on this site. I can access remote web workplace internally by specifying either the IP and domain, but cannot access it externally. I think if I can resolve this issue then the email problem wil be fixed too.
Anyone see this issue?
Network Connection
IP: 192.168.16.2
Subnet Mask: 255.255.255.0
Gateway: [blank]
Internal NIC
IP: 192.168.1.41
Subnet Mask: 255.255.255.0
Gateway: 192.168.1.1
Router IP: 192.168.1.1
Thanks for any help!
Chris
Check your DNS server settings under properties. Your NICs setup are correct (despite you gave them misleading names).
Have a loook at this link it tells you the 2 NICs setup in more detail.
http://www.smallbizserver.net/Articles/tabid/266/articleType/ArticleView/articleId/76/Two-Nics-a-static-IP-address-ISA-router.aspx
Have a loook at this link it tells you the 2 NICs setup in more detail.
http://www.smallbizserver.net/Articles/tabid/266/articleType/ArticleView/articleId/76/Two-Nics-a-static-IP-address-ISA-router.aspx
ASKER
You're right, I mislabeled them... this what they are...
Internal NIC
----------------------
IP: 192.168.16.2
Subnet Mask: 255.255.255.0
Gateway: [blank]
Preferred DNS: 192.168.16.2
WINS: 192.168.16.2
External NIC
----------------------
IP: 192.168.1.41
Subnet Mask: 255.255.255.0
Gateway: 192.168.1.1
Preferred DNS: 192.168.16.2
WINS: [blank]
Router IP: 192.168.1.1 (has static IP from ISP)
Ports Forwarded: 80, 443, 444, 4125, 3389, 25, 110, 1723
------
Hardeep_Saluja:
My internal NIC is at the top of the network binding list. When I ping the domain externally, I get the router's IP address and not the server's IP. Am I not pinging the RWW properly?
ormerodrutter:
Before I made my original post, I found that site that you listed and validated that all the settings match for both internal and external NICs.
I just find it odd that I can connect to RDP through the router, but cannot get any of the other services to respond. So I know it's listening to something! I also tried placing the server in the DMZ on my router, but still the same problem.
Internal NIC
----------------------
IP: 192.168.16.2
Subnet Mask: 255.255.255.0
Gateway: [blank]
Preferred DNS: 192.168.16.2
WINS: 192.168.16.2
External NIC
----------------------
IP: 192.168.1.41
Subnet Mask: 255.255.255.0
Gateway: 192.168.1.1
Preferred DNS: 192.168.16.2
WINS: [blank]
Router IP: 192.168.1.1 (has static IP from ISP)
Ports Forwarded: 80, 443, 444, 4125, 3389, 25, 110, 1723
------
Hardeep_Saluja:
My internal NIC is at the top of the network binding list. When I ping the domain externally, I get the router's IP address and not the server's IP. Am I not pinging the RWW properly?
ormerodrutter:
Before I made my original post, I found that site that you listed and validated that all the settings match for both internal and external NICs.
I just find it odd that I can connect to RDP through the router, but cannot get any of the other services to respond. So I know it's listening to something! I also tried placing the server in the DMZ on my router, but still the same problem.
ASKER
Just to add on to my last post....
From an external computer, I opened up the command prompt and performed:
telnet [domainname] 3389
This opened to a blank screen, so it shows it is listening on that port.
When I do:
telnet [domainname] 4125
It gives an error saying it cannot connect to that port.
Thanks for your help so far!!
From an external computer, I opened up the command prompt and performed:
telnet [domainname] 3389
This opened to a blank screen, so it shows it is listening on that port.
When I do:
telnet [domainname] 4125
It gives an error saying it cannot connect to that port.
Thanks for your help so far!!
Strange one. Rerun CEIEW and see if it fixes anything?
ASKER
Yes. Very strange. I re-ran CEIEW and it didn't fix anything.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Do u have ISA?
Make sure DNS is listening to Internal IP
Ping <rww website> >> shold return on internal IP
Also, go to network connections>> Advanced menu>Advanced settings and make sure internal network card is on top of network binding list
Please let me know...
Thanks