LGFL 2.0 Local Network Problems

[talksr]

Hi, if anyone could help with this, I would really apreciate it.

We had our LGFL 2.0 internet connection installed last week and have had a list of problems.

At the moment, if I have just one thing left to fix.

 

We have two networks, admin and curriculum.

Our Admin network runs a server 2008 domain and windows 7 clients.

All of the clients are now getting the new lgfl 2.0 internet connection but are not logging in to the domain correctly.

When a user logs in, the pc accepts the password, but then displays an error saying Windows can't access \\server\home$\user\desktop

After clicking cancel, it takes a while to log in. As expected there is no desktop folders and files, and no shares so the login scripts are not working. It is as if the client systems are completely unable to connect to the admin server.

 

I am completely unable to browse to the server \\server\ from stat menu.

But if I open up command prompt, I am able to ping it with no problems.

 

The windows 7 systems have the following static IP address structure:

IP: 10.232.162.*

Sub:255.255.255.0

GW: 10.232.162.1

DNS1 Server IP

DNS2 Blank

 

The server dns forwarders are set as the new lgfl ones which are 172.30.178.53 and 172.30.178.54

 

Any suggestions would be great.

[talksr]

Ah, I have managed to solve. Will post my resolution when I get a chance!

[Mcshammer_dj]

Great news

[spookyspoof]

wow - i'm so happy for you

[Mcshammer_dj]

If you can post the resolution that would be ideal because it sounds just like a problem I have....

[SYNACK]

I'm assuming that this is all related so merged the threads to keep it all together and so everyone knows whats its about.

[talksr]

We were using managed switches on both admin and curriculum. All of the curriculum ones were acting as a stack. I was concerned that maybe the admin one was also acting as part of the stack but it wasn't which was good. Not sure exactly what was wrong on the admin switch, but I factory wiped it by using a serial cable and running putty. Once it was wiped and re-booted, it was fine. Admin network was working, everything was behaving as it should. I gave the admin switch the same admin static ip it had before, no problems. Same with subnet. It didn't need a dns which was what I thought may have been wrong.

 

Hope it helps.