CrossedFingers
asked on
External RWW address on internal network shows Comcast Gateway login page, works fine externally
Hi guys,
I have a client that has a SBS and I just switched their Qwest connection to Comcast yesterday. I updated DNS on GoDaddy to point the updated DNS records to point to the new Comcast Static IP (which is actually the IP of the gateway) and if you try and access https://remote.domain.com externally RWW works just fine. However if you're on the local network and try to use the same address it acts like it's going to work (prompted with invalid certificate/continue screen) but after selecting continue it goes to the interface (192.168.55.1) of the Comcast gateway instead of the server 192.168.55.100.
It's acting like there is some DNS record locally that points remote to the gateway instead of the server, but I'm not seeing anything. Its got to be something easy...I'm just not seeing it
Network setup = Comcast SMC -->16 port switch --->SBS
Thanks guys!
I have a client that has a SBS and I just switched their Qwest connection to Comcast yesterday. I updated DNS on GoDaddy to point the updated DNS records to point to the new Comcast Static IP (which is actually the IP of the gateway) and if you try and access https://remote.domain.com externally RWW works just fine. However if you're on the local network and try to use the same address it acts like it's going to work (prompted with invalid certificate/continue screen) but after selecting continue it goes to the interface (192.168.55.1) of the Comcast gateway instead of the server 192.168.55.100.
It's acting like there is some DNS record locally that points remote to the gateway instead of the server, but I'm not seeing anything. Its got to be something easy...I'm just not seeing it
Network setup = Comcast SMC -->16 port switch --->SBS
Thanks guys!
Aaron Tomosky
Is the comcast smc a router?
ASKER
Yes. It's a SMC 8014.
I would be that the comcast device doesn't support loopback, so when you browse to the external IP it just shows the login of the comcast device (router?).
Is the old router compatible with the comcast service?
Is the old router compatible with the comcast service?
ASKER
The older router was a router/modem combination from Qwest and wouldn't work with the new setup. I've told them for a while now they need a more robust router, but they're on a tight budget. I googled SMC 8014 and loopback and got this thread:
http://superuser.com/questions/107276/how-do-i-forward-ports-on-a-comcast-smc-8014-w-a-static-ip-doesnt-seem-to-wor
http://superuser.com/questions/107276/how-do-i-forward-ports-on-a-comcast-smc-8014-w-a-static-ip-doesnt-seem-to-wor
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Good point DrDave, what was i thinking ...
ASKER
Hi Guys,
So I have two forward zones: _msdcs.domain.local & domain.local. When I added a new zone "remote.domain.com" it defiantly corrected my problem, but when I did an nslookup I could see that the default server had changed from servername.domain.local to remote.domain.com. I went ahead and deleted the remote.domain.com zone and now it's showing correctly. I'm sure this isn't what I want. What should I be doing differently?
So I have two forward zones: _msdcs.domain.local & domain.local. When I added a new zone "remote.domain.com" it defiantly corrected my problem, but when I did an nslookup I could see that the default server had changed from servername.domain.local to remote.domain.com. I went ahead and deleted the remote.domain.com zone and now it's showing correctly. I'm sure this isn't what I want. What should I be doing differently?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Agree with dave, the name of the nslookup server can say anything it likes if your client has the correct static DNS servers in IPconfig or is being give the correct details from the DHCP server then DNS will resolve to the SBS server. What your client thinks is the primary name of that server is irelivent, a server can have 100 names if they are listed it will always resolve to the same IP address, computers communicate via IP address and Netmask not its DNS name in reality, computers talk in numbers not names.
ASKER
Thanks so much guys. Ultra fast responses. I appreciate the help. Sorry for the delay!