Http://Connect does not work

When I type HTTP://CONNECT, IE fails to connect to the SBS2008 and when I type in "PING CONNECT" in command prompt window, it shows "Pinging connect.DomainName.local [ 192.168.2.3]" followed by 4 failed replies.
Background: I originally had this workstation (WIndows 7) connected to SBS2008. Then I created SBS2011 and connected this Workstation to SBS2011. Ran Migration from 2008 to 2011, but decided not to continue with complete migration. So migration stopped in the middle.
I dis-jointed my workstation from SBS2011. Now I have SBS2008 back up again and wanted to join the network (By the way I know how to joiin the domain), but using HTTP://CONNECT.
Somehow my computer looks for old SBS2011with IP address of 192.168.2.3. IP address of current SBS2008 is 192.168.2.2. Where does my computer keep this information?
sgleeAsked:
Who is Participating?
 
TBK-ConsultingConnect With a Mentor Commented:
it is getting it from DNS ... check your DNS on the server responsible for the domain to ensure that CONNECT points to the proper ip address, and also run an ipconfig /flushdns to get rid of any lingering remains of DNS from the 2011 server ...
0
 
sgleeAuthor Commented:
I turned off SBS2011 (192.168.2.3) completely and currently SBS2008 (192.168.2.2) is turned on.
I just checked SBS2008 TCP/IP property and it has 192.168.2.2 in preferred DNS server area.
I checked the HOST file in Windows 7 workstation, but there is no such an entry "CONNECT 192.168.2.3".
So who is keeping & whre this entry "HTTP://CONNECT ---> IP Address of 192.168.2.3" ?
0
 
TBK-ConsultingCommented:
Check the DNS table on the server, not in the tcp/ip settings .. goto the DNS Manager to check, if nothing is there then you are good on that end and the workstation DNS Cache has the old record still and can be flushed by using the ipconfig /flushdns command from a DOS Prompt in order to get rid of the bad cache entry ... to show you try opening a DOS prompt and do a NSLOOKUP CONNECT command to see what the response is if you are getting 192.168.2.3 instead of .2 then the DNS Cache on the workstation has the old info and is using that and will contiunue to do so until you clear the cache.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
sgleeAuthor Commented:
Also when I type "PING CONNECT" within SBS2008 (192.168.2.2) command prompt, I get the same result as when I  did "PING CONNECT" from my Win7 Workstation. It says "Pinging Connect.domainname.local [192.168.2.3]" which is SBS2011 that no longer exist on the network.
0
 
TBK-ConsultingCommented:
goto a command prompt and type ipconfig /flushdns, then reboot the workstation and go back and see if you are pinging the right address then ...
0
 
sgleeAuthor Commented:
OK. here is what I found out:
SBS2008 (192.168.2.2) Computer Name: MSS01
SBS2011 (192.168.2.3) Computer Name: MSS1

When I typed "nslookup connect", I get the following:

Server:  mss01.mssonline.local
Address:  192.168.2.2
Name:    connect.mssonline.local
Address:  192.168.2.3

Now on the file server SBS2008, I opened DSN Manager  and there are SO MANY references of SBS2011 IP address & NetBIOS computer name in both Forward Lookup Zones and Reverse Lookup Zones - like following:
 
192.168.2.2  mss01.mssonline.local.
192.168.2.3  mss1.mssonline.local.

Should I delete all entries of "192.168.2.3  mss1.mssonline.local"?
I think this entry was created during migration process.


0
 
TBK-ConsultingCommented:
I would delete all the references to the 2011 server, and make sure there is a CONNECT entry in the forward lookup zone as an A record set to the 2008 server.
0
 
sgleeAuthor Commented:
I thought I deleted a ton of entries with 192.168.2.3, but it did not work.

Then I revisited DNS Manager and You were right.
DNS/MSS01/Forward Lookup Zones/Mssonline.local, there was an entry "CONNECT HOST(A) 192.168.2.3 Static" and alsi I see every PC name /Host(A) and IP address on the network.
I changed  "CONNECT HOST(A) 192.168.2.3 Static" to " "CONNECT HOST(A) 192.168.2.2 Static" and http://connect works just fine.

THANK YOU FOR YOUR HELP and I REALLY  APPRECIATE IT!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.